According to DEV Community, the November 2026 State of Web Vitals analysed 236,675 crawled sites. It found that 79.1% run third-party scripts, meaning code from outside vendors such as chat widgets, tracking pixels and heatmaps. It also found that 64.7% still ship render-blocking synchronous scripts, which stop the browser building the page until they finish loading. The worst sites load more than 1.5 MB of unused JavaScript before a visitor sees anything.
The article links this to measurable results. Sites with render-blocking scripts pass Largest Contentful Paint, the measure of how fast the main content appears, at 79%, with a 1.7-second median. On React and Next.js sites, pages with synchronous blocking scripts pass at 66%, against 86% for pages using defer, a loading attribute that lets the page continue while a script downloads. WordPress is named as the worst of the major platforms: 89.1% of its sites load render-blocking synchronous scripts.
The author also points to Interaction to Next Paint, which grades a site's worst interaction rather than its first. A chat widget, a heatmap recorder or a tag manager can each cause a freeze of around 400 ms on a single tap, even when a Lighthouse score looks green.
The suggested audit takes about ten minutes. List every script the page loads using the DevTools console. Run Chrome DevTools Coverage to see how much of each script actually executes. Then read the PageSpeed Insights diagnostics on unused JavaScript and third-party code. The author recommends deleting first, then deferring or delaying scripts, then moving the rest off the main thread with tools such as Partytown or Cloudflare Zaraz. Loading a chat widget only when someone clicks it is called a facade. The author calls it the highest-leverage change for most sites. GitHub and Shopify are cited as teams that cut work before optimising what remained.
Why it matters
Many of these scripts were added quickly and never reviewed. Each one can delay how soon visitors see content and how responsive the page feels, and that can affect the experience of people trying to buy or sign up. A good lab score may hide the problem.
The article's wider point is about ownership. Scripts pile up because nobody is responsible for them. Giving each script an owner, a stated job and a review date, and re-checking every quarter, helps stop the clutter returning. Note that the figures come from one analysis as reported by DEV Community, so treat them as a guide to the scale of the issue rather than a prediction for your own site.
Source: DEV Community. This brief summarises their reporting; read the original for the full detail.