geolytix.com
Data from Aug 20, 2026, 10:31 PM UTC — 20h old.
Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 20h
Stack
Detected on the same page load as the accessibility pass — the generator
from <meta name="generator"> or the shape of the page,
the host from response headers.
Core Web Vitals field data, origin-level
Real Chrome users, 28-day window (2026-07-22 → 2026-08-18). This is what Google measures you on.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 2.95 s | — | — | 2.95 s | 2.95 s | |
| CLS Cumulative Layout Shift | 0.310 | — | — | 0.310 | 0.310 | |
| TBT Total Blocking Time | 285 ms | — | — | 285 ms | 285 ms | |
| FCP First Contentful Paint | 1.25 s | — | — | 1.25 s | 1.25 s | |
| Speed Index | 1.26 s | — | — | 1.26 s | 1.26 s | |
| TTFB Time to First Byte | 611 ms | — | — | 611 ms | 611 ms |
What LCP is made of
A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.
Field data Chrome UX Report, origin-level
Real Chrome users, 28-day trailing window (2026-07-22 → 2026-08-18). This is what Google measures you on.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 1.32 s | good | 93.9% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 72 ms | good | 95.4% good |
| CLS CWV | 0 | good | 98.9% good |
| FCP | 1.18 s | good | 87.4% good |
| TTFB | 634 ms | good | 83% good |
Lab vs field
Lab LCP 2.95 s · field p75 1.32 s · real users are 0.45× faster than the lab.
Field history 25 weeks
Weekly p75 from the CrUX History API, backfilled in a single request.
| Week ending | LCP | INP | CLS | FCP | TTFB |
|---|---|---|---|---|---|
| 2026-08-15 | 1.34 s | 77 ms | 0 | 1.19 s | 644 ms |
| 2026-08-08 | 1.32 s | 78 ms | 0 | 1.20 s | 649 ms |
| 2026-08-01 | 994 ms | — | 0 | 948 ms | 379 ms |
| 2026-07-25 | 950 ms | — | 0 | 832 ms | 378 ms |
| 2026-07-18 | — | — | — | — | — |
| 2026-07-11 | — | — | — | — | — |
| 2026-07-04 | — | — | — | — | — |
| 2026-06-27 | 843 ms | — | 0 | 681 ms | 267 ms |
| 2026-06-20 | 826 ms | — | 0 | 673 ms | 268 ms |
| 2026-06-13 | 764 ms | — | 0 | 613 ms | 221 ms |
| 2026-06-06 | 770 ms | — | 0 | 628 ms | 225 ms |
| 2026-05-30 | — | — | — | — | — |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 22.81 MB | — | — | 22.81 MB | 22.81 MB | |
| Requests | 138 | — | — | 138 | 138 | |
| Third-party Weight | 19.81 MB | — | — | 19.81 MB | 19.81 MB | |
| Third-party CPU | 175 ms | — | — | 175 ms | 175 ms | |
| Unused JS | 380.0 kB | — | — | 380.0 kB | 380.0 kB | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 6 entities
19.81 MB transferred, 175 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 2.70 s | — | — | 2.70 s | 2.70 s | |
| Long Tasks | 12 | — | — | 12 | 12 | |
| DOM Elements | 1,094 | — | — | 1,094 | 1,094 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 54 | — | — | 54 | 54 | |
| A11y Failures | 6 | — | — | 6 | 6 | |
| A11y Failing Nodes | 45 | — | — | 45 | 45 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
54 violating nodes across 7 rules, 1411 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.
-
serious
aria-hidden-focus— ARIA hidden element must not be focusable or contain focusable elements 45 nodes -
serious
link-name— Links must have discernible text 4 nodes -
critical
aria-valid-attr-value— ARIA attributes must conform to valid values 1 node -
serious
color-contrast— Elements must meet minimum color contrast ratio thresholds 1 node -
moderate
heading-order— Heading levels should only increase by one 1 node -
serious
html-has-lang— <html> element must have a lang attribute 1 node -
moderate
landmark-unique— Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
Accessibility failures 6 of 27 audits
Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.
-
aria-hidden-focus— `[aria-hidden="true"]` elements contain focusable descendents 37 nodes -
link-name— Links do not have a discernible name 4 nodes -
aria-valid-attr-value— `[aria-*]` attributes do not have valid values 1 node -
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 1 node -
heading-order— Heading elements are not in a sequentially-descending order 1 node -
html-has-lang— `<html>` element does not have a `[lang]` attribute 1 node
Hygiene
Changes rarely — which is exactly why a change is worth noticing.
Measurement log
Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.
| When | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took |
|---|---|---|---|---|---|---|---|---|---|
| Aug 20, 2026, 10:31 PM UTC | 73 | 2.95 s | 0.310 | 285 ms | 22.81 MB | 3/3 | ±20 | 2,327 | 54.9s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
geolytix.com's scores, updated whenever this instance
re-measures — more about the component. Don’t forget to bundle the speedlify-score.js component code into your site!
<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://geolytix.com/"></speedlify-score>