Urgent.News

What's breaking now, across thousands of outlets.

Tech

Why does CrUX say no data for my client site?

PageSpeed Insights finishes the Lighthouse half of the report and then leaves the “real users” block empty. The client Slack thread fills with “is CrUX broken?” and someone refreshes the same URL three times. Lab scores are there, but field percentiles are not. That pattern is usually eligibility, not a failed API call. What follows is the engineer’s short path: which kind of “no data” you are…

The Chrome UX Report (CrUX) displays no data for your client site because the necessary eligible Chrome sessions are not available for that origin or URL. Lighthouse scores are present, but field percentiles are missing. This pattern usually indicates eligibility issues, not a failed API call. To resolve this, ensure the URL and host match exactly as CrUX expects.

CrUX only publishes anonymized field distributions when enough eligible Chrome sessions clear privacy and quality rules for the site. The absence of field data does not indicate a slow site; lab diagnostics can guide performance improvements while eligible traffic builds.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

HLS vs progressive MP4: what a video downloader actually hands you

When I started building the downloader on ramrom.io, I assumed every video on the internet was an MP4. A URL points at a file, you fetch the bytes, you hand them to the visitor. Simple.

  • Progressive MP4s are single files with clear sizes and headers
  • HLS streams are playlists of segments with no single file size
  • HLS requires either stitching (resource-intensive) or delegation (browser/app handling)

PHP2Shell, What Was That About?

Recently, about two weeks ago on 21 October 2026, there were two vulnerabilities announcement which shook most of the internet, caused permanent EoS (End of Services) at web based games like World…

  • Two critical PHP vulnerabilities emerged on 21 October 2026
  • Attackers could access web shell via remote code execution
  • Servers urged to upgrade PHP to 8.5.12 or apply patches

More from Tuesday 3 November →