Topic · 8 items
Field data
This page gathers what Preload has published on field data: what your visitors actually experience, beyond lab tests. I follow CrUX data, real user monitoring (RUM) tools, new browser APIs and the blind spots that skew the numbers. It's for anyone who steers a site's performance based on its real users.
Follow this topic By RSS, in your feed reader
A field monitoring script hijacked to drain Polymarket accounts
A performance monitoring script can do a lot more than measure: on October 29, according to Hudson Rock's analysis, the DebugBear real user monitoring (RUM) file loaded by the betting platform Polymarket contained code that looked for the open session in the page, sold or transferred positions to an attacker's address, then reported back to a DebugBear server. Polymarket's Content Security Policy (CSP) allowed the script's host, and therefore anything it served. DebugBear asked customers to remove its embed code; Polymarket, which points to a compromised third-party provider, paused trading and promised refunds. How the script was compromised and which other customers were hit is still unknown.
Next step
Search your sites' code for cdn.debugbear.com and remove it. More broadly, load no third-party script, monitoring agents included, on account, checkout and admin pages. Subresource Integrity (SRI) only protects a frozen file: a vendor script updated in place breaks its hash.
Allowing a host in your CSP means trusting every byte it will ever serve. A monitoring tool has no business on a page where people pay or administer a site.
Basicrum, open source field monitoring on a single server
To measure Core Web Vitals from real visitors without a subscription, Basicrum has released an installer that deploys everything on one server with a single command: six Docker containers (Traefik, a Rust ingestion service, ClickHouse, Postgres, a Node API and a Next.js dashboard), fed by the open source Boomerang collection script. It needs at least 2 CPUs and 4 GB of memory for Docker, and handles TLS through Cloudflare Origin CA, Let's Encrypt or your own certificate.
Next step
Try it on a non-shared server (a VPS, a cloud instance or a dedicated server), in letsencrypt or cloudflare mode depending on your DNS. If you run Docker Engine 29 yourself, keep Traefik at 3.6 or later: older versions can no longer talk to it.
It's a credible alternative to paid tools once several sites share the collection. For a single site, a few lines of
web-vitalsand a small collector are enough; the brand-new repository doesn't show a license yet.
Safari 27 blocks services that track visitors by their email address
Your attribution and audience numbers may shift without you shipping anything: in iOS, iPadOS, macOS and visionOS 27, Safari cuts network access to third-party “identity resolution” infrastructure, WebKit announced on October 19. These services grab the email address typed at sign-in or sign-up and turn it into an opaque tracking identifier, so they can follow the person across sites and devices. The block works at the domain level, so reshaping the request won't get around it, and WebKit doesn't name any service.
Next step
If attribution, audience matching or third-party requests drop, compare Safari with other browsers first, before blaming the site or its performance. In a third-party audit, count what Safari blocks separately.
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.
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.
deliveryType finally tells you when a resource came from cache
Firefox 158, out on October 13, supports PerformanceResourceTiming.deliveryType, which returns "cache" when a resource was served from the cache. Chrome and Edge have exposed it since version 117 and Safari since 26.4, so all four engines will have it, but its Baseline status has not been updated yet.
Not Baseline yet: Chrome 117, Safari 26.4, Firefox 158
Next step
In your field data, split cached resources from the rest before reading their timings, otherwise your averages mix two very different populations.
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.