---
title: "Discussion on \"Partial page loads and CrUX: what field data quietly drops\" | Hashnode"
description: "Discussion on \"Partial page loads and CrUX: what field data quietly drops\". Chrome UX Report percentiles are not a slower Lighthouse run. Incomplete visits, background starts, and navigation types quietly reshape what agencies can claim after a green lab score."
url: "https://hashnode.com/posts/partial-page-loads-crux-what-field-data-quietly-drops/6af81f5389b3ba1d6b73e8a1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Partial page loads and CrUX: what field data quietly drops](https://devlog.apogeewatcher.com/partial-page-loads-crux-what-field-data-quietly-drops?utm_source=hashnode&utm_medium=feed)

Chrome UX Report percentiles are not a slower Lighthouse run. Incomplete visits, background starts, and navigation types quietly reshape what agencies can claim after a green lab score.

7h ago · 7 min read · devlog.apogeewatcher.com  
Read the article

-   [#core-web-vitals](https://hashnode.com/tag/core-web-vitals)
-   [#webperf](https://hashnode.com/tag/webperf)
-   [#pagespeed](https://hashnode.com/tag/pagespeed)
-   [#seo](https://hashnode.com/tag/seo)
-   [#webdevelopment](https://hashnode.com/tag/webdevelopment)

## Written by

[Apogee Watcher](https://hashnode.com/@apogeewatcher)

@apogeewatcher · Greece

  
[View profile](https://hashnode.com/@apogeewatcher)

Solving web performance monitoring for agencies and solopreneurs

Apogee Information Systems operates at the intersection of digital transformation for international organisations, innovative e-learning, public service automation, and specialised commercial solutions. Currently building Apogee Watcher, a web performance tool for agencies and solopreneurs.

## Responses 2

Markdown supported · ⌘↵ to post

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[54m ago](https://hashnode.com/posts/partial-page-loads-crux-what-field-data-quietly-drops/6af81f5389b3ba1d6b73e8a1/comment/6af87943495c1d1ea843b5c7)

The table comparing the Lighthouse clock with the CrUX field clock is the part I will keep. It makes the mismatch concrete: one controlled full navigation against an aggregate of eligible real experiences, with background tabs, early abandons, and bfcache restores quietly dropped from the comparison. The line about stopping the claim that field disagrees with Lighthouse also landed well. Lab measured a controlled run and field measured a population, so the honest move is to label which clock each number came from before selling a fix.

[Apogee Watcher](https://hashnode.com/@apogeewatcher)

[52m ago](https://hashnode.com/posts/partial-page-loads-crux-what-field-data-quietly-drops/6af81f5389b3ba1d6b73e8a1/comment/6af87943495c1d1ea843b5c7#reply-6af879b9a59ec55fc1769494)

Thanks for reading closely. One small refinement on bfcache restores: they aren't dropped outright, since CrUX still measures LCP on a restore because it feels like a new visit to the user, while TTFB only comes from full page loads. That's why we'd compare navigation types before blaming hosting when TTFB and LCP tell different field stories on the same origin. Labelling which clock each number came from is the habit we'd most like agencies to keep, ideally as a caption on the slide itself.