The typical page runs 26 scripts weighing 552 KB

LCP INP CLS

At a glance the headline numbers for Scripts per page

How many scripts the page runs and their over-the-wire weight.

script count

on the typical page

552 KB

script weight

on the typical page

1,007 KB

1 in 4 pages exceed this

script weight

180,899

sites measured

phone field data

The typical page runs 26 scripts weighing 552 KB.

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv

Distribution & median INP site count and median INP at each level of scripts per page — n

0ms 63ms 125ms 188ms 250ms

200ms

0 9927 19854

5–9 10–14 15–19 20–24 25–29 30–34 35–39 40–44 45–49 50–54 55–59 60–64 65–69 70–74 75–79 80+

Good (≤200ms) Needs improvement Poor (>500ms) Site count

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv

Passing INP by scripts per page — n which level passes the INP most often

Scripts per page — nSitesPassing INPINP

5–9 14,865 82% 103ms

10–14 19,854 92% 91ms

15–19 17,447 94% 94ms

20–24 15,796 93% 95ms

25–29 13,865 94% 95ms

30–34 11,862 95% 96ms

35–39 10,243 93% 100ms

40–44 8,512 95% 101ms

45–49 7,105 94% 103ms

50–54 5,958 94% 104ms

55–59 5,141 94% 103ms

60–64 4,201 93% 105ms

65–69 3,530 94% 105ms

70–74 3,664 93% 103ms

75–79 3,602 93% 102ms

80+ 17,893 90% 116ms

Good Needs Improvement Poor Faded rows: under 100 sites

Scripts per page — n 26. p75 49. p99 156. At the low end (5–9): INP 103ms. At the high end (80+): INP 116ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv

Distribution & median INP site count and median INP at each level of scripts per page — size

0ms 63ms 125ms 188ms 250ms

200ms

0 17209 34418

0–199 200–399 400–599 600–799 800–999 1000–1199 1200–1399 1400–1599 1600–1799 1800+

Good (≤200ms) Needs improvement Poor (>500ms) Site count

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv

Passing INP by scripts per page — size which level passes the INP most often

Scripts per page — sizeSitesPassing INPINP

0–199 34,418 93% 87ms

200–399 33,297 96% 91ms

400–599 26,236 95% 95ms

600–799 21,252 94% 97ms

800–999 16,562 94% 102ms

1000–1199 12,061 92% 108ms

1200–1399 8,648 89% 113ms

1400–1599 6,041 90% 115ms

1600–1799 4,464 88% 118ms

1800+ 13,322 82% 129ms

Good Needs Improvement Poor Faded rows: under 100 sites

Scripts per page — size 552 KB. p75 1,007 KB. p99 3.7 MB. At the low end (0–199 KB): INP 87ms. At the high end (1800+ KB): INP 129ms. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv

Why this matters for the Core Web Vitals, and where to start fixing it

Script weight is the most expensive weight. A kilobyte of JavaScript costs more than a kilobyte of image, because after the download it is parsed, compiled and executed on the main thread. That is the same thread that must answer every click and keystroke, which is why script totals track INP.

The count matters next to the bytes: every script is a potential long task and another spot for the main thread to stall. Most pages would lose nothing by deferring most of their scripts. The ones that truly must run early are rare.

How do scripts affect the Core Web Vitals?

Scripts per page correlates with the INP. Script weight separates passing sites from failing sites more than script count does. Where the script weight is low, 93% of sites pass the INP. Where it is high, 82% do. The decline is gradual. There is no point where sites suddenly start failing. Script bytes keep costing after the download: the main thread still has to parse and execute them.

Go fix it 14 methods to defer JavaScript → Reduce unused JavaScript → JavaScript priority levels →

Related signals DOM size → Page weight & requests → Image source mix → Stylesheet loading mix → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured