Topic · 6 items
INP
This page gathers what Preload has covered on INP (Interaction to Next Paint), the Core Web Vitals metric for the delay between an interaction and the next frame that shows its result. I follow CrUX data, the tools that help you pin down the slow interaction, and the scripts, ads included, that block the main thread. It's for developers and teams who need a site that feels responsive to its real visitors.
Follow this topic By RSS, in your feed reader
Chrome measures the weight of ads, with two blind spots
Ads often slow down the pages that show them, without anyone knowing exactly which ones. Chrome can now recognize them (using EasyList, a public ad filter list, and the script that loads them), and DevTools, the browser's built-in diagnostic tool, shows them in an Ads tab: processing time and download size per ad, and a list of ad scripts. Google also publishes four metrics measured on real visitors (screen space taken, count, processing, size) for sites that declare their ad sellers in their ads.txt file.
Next step
On a page with ads, open DevTools (F12 key), Application panel, Ads tab: you'll see which ads and scripts weigh the most. Then cross-check with the Performance panel to find which ones make the page slow to respond to clicks.
Two blind spots in our tests: an ad script running directly in the page isn't counted, only ad frames are, and a Chrome driven by a testing tool shows everything at 0. The script list is therefore more reliable than the total for knowing which ad network slows the site down.
opendesk, an open source helpdesk you can host yourself
To keep your support data in house, Mindroot has released opendesk, an open source helpdesk (Apache 2.0): shared support inbox, embeddable chat widget, public help center, AI (Anthropic, OpenAI-compatible models or a local model), API, webhooks and an MCP server. Written in Go and Elixir on Postgres, it self-hosts with a single command (Docker, Caddy) and runs the same code as the cloud offering. The project is new, and neither the widget's weight nor how it loads is documented.
Next step
If you embed the widget, load it on click behind a facade (a lightweight button that only loads the real script on interaction) and reserve its space to avoid CLS. An iframe doesn't isolate INP or CLS: measure it like the rest of the page.
Self-hosting settles the data sovereignty question, not the widget's cost to your site, which you should measure before rolling it out.
CrUX finally measures soft navigations in single-page apps
Starting with the September dataset, released on October 13, CrUX adds three experimental variants of LCP, INP and CLS that count each route change in a single-page app as a navigation. They are available in BigQuery, the API, the History API and CrUX Vis, with FCP coming in November. Google aims to take them out of experimental status in May 2027, at which point Search Console would switch to this data. Across all origins, the share of good LCP goes from 68.3% to 72.1%.
Next step
On a single-page app, track both series side by side and note which dashboards and alerts only read the stable one. On a multi-page site, such as WordPress or PrestaShop without a decoupled front end, nothing changes.
A gap between the two series mostly reflects a change in what is measured, not a faster site: follow-up views reuse code that is already loaded. The JavaScript that runs on every route change still weighs on INP.
WebPerf Snippets: from console copy-paste to a complete toolkit
Joan León's diagnostic scripts, which you used to paste one by one into the console, became a toolkit with structured results in a single week (versions 2.0 and 2.0.1, October 13 to 15). A beta DevTools extension gathers them in a panel, even when the CSP blocks pasting, and CLI 1.0 also audits logged-in pages and compares them against CrUX data. In CI, a GitHub Action fails the build when a page goes over the performance budget you set. The same scripts are also packaged for AI agents, so they can run these diagnostics themselves.
Next step
Install the extension for live diagnosis and the GitHub Action to catch regressions, but always start from field data (CrUX, RUM) to decide what to fix.
An effective but clunky tool becomes easy to use, which means measuring more often.
BEACON: field data from 10,000 large sites, open in BigQuery
Since late September, Cloudflare has published BEACON: anonymized field measurements from 10,000 of the largest sites on its network, updated daily in BigQuery using the RUM Archive format. Unlike CrUX, it covers WebKit on iOS, provides full distributions and breaks down LCP and INP into their subparts. For slow LCPs, render delay and load delay weigh far more than the image download itself.
Next step
Query the cf-open-web-performance.rumarchive project with the queries documented by the RUM Archive, and always filter on the date: tables are partitioned and BigQuery bills you for the bytes scanned.
A gold mine for spotting trends, not for judging a single site. The sample is limited to large sites behind Cloudflare and says nothing about your own domain.
web-vitals 6.2.3 fixes LCP attribution
The October 5 release of Google's library fixes a negative resourceLoadDuration value in LCP attribution, as well as a memory leak related to INP.
Next step
If your own monitoring reads LCP attribution, upgrade to 6.2.3 and discard any negative values you have already collected.