Loupe LookoutSaltbrush & Sage
How fast pages load for real visitors (field data) and in the lab, and how quickly the server answers.
On phones, 75th percentile over 2026-10-22 to 2026-11-18: LCP 2.6 s (needs improvement), INP 168 ms (good), CLS 0.04 (good). Desktop: LCP 1.7 s, INP 71 ms, CLS 0.02.
This is what Google measures on real visitors' phones over the last 28 days, and it feeds ranking. It is the headline speed number because lab scores swing from run to run.
What to do: Images sized for the screen, fewer apps injecting scripts, a lighter theme section above the fold. Each poor metric has its own fix on the facet page.
Ask RDA to handle thisLab mobile performance 58 (average of 3 pages): home 61 mobile / 92 desktop; top collection 55 / 88; top product 58 / 90. Biggest opportunity: Improve image delivery (Estimated savings of 1.2 s).
A lab run on a throttled phone connection. It swings run to run, so it is weighted below the field data, but it points at the specific resources slowing the page.
What to do: The three biggest opportunities from the run are listed on the facet page in plain words.
Ask RDA to handle thisLighthouse accessibility 94 on the home (lowest of 3 pages).
Contrast, labels and alt text: what makes the site usable with a screen reader or in bright sun, and part of what Google checks.
What to do: Fix the failed audits listed on the facet page; most are alt text and contrast.
Median 317 ms from New York over 288 pings today, 351 ms from New Jersey just now.
How long the server takes to start answering, before any page content loads. Measured from two vantage points so one slow route is not mistaken for a slow site.
What to do: On Shopify this is Shopify's edge; on WordPress it is hosting and caching. A slow first byte usually means a cache miss or an overloaded server.
Mobile performance, average across the pages tested; lab figures swing run to run. Columns are the mobile run.
| Page | Mobile | Desktop | LCP | TBT | CLS | Weight |
|---|---|---|---|---|---|---|
| home | 61 | 92 | 3.9 s | 310 ms | 0.03 | 2.6 MB, 96 req |
| top collection | 55 | 88 | 4.3 s | 380 ms | 0.02 | 3.1 MB, 112 req |
| top product | 58 | 90 | 4.0 s | 420 ms | 0.04 | 2.8 MB, 104 req |
Biggest opportunities: Improve image delivery (Estimated savings of 1.2 s); Reduce unused JavaScript (0.9 s); Render-blocking requests (Estimated savings of 450 ms).
Real Chrome visitors, 75th percentile, to . This is what Google measures.
| Metric | Phone p75 | Rating | Good | Desktop p75 | Rating |
|---|---|---|---|---|---|
| LCP | 2.6 s | needs improvement | 68% | 1.7 s | good |
| INP | 168 ms | good | 84% | 71 ms | good |
| CLS | 0.04 | good | 81% | 0.02 | good |
Ask about any figure, check or change on this page. Every answer names its source and date.
Loupe answers from the figures on this page. For anything else, your RDA team is at support@rubydigitalagency.com.