speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time.

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

bayton.org

https://bayton.org/

31 84 96 85 CWV 114AXE

Data from Aug 20, 2026, 3:47 PM UTC — 27h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 27h

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.

Eleventy 2.0.1 Built with Eleventy 2.0.1
Netlify Hosted by Netlify

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.

LCP 2.51 s needs-improvement
INP 171 ms good
CLS 0 good

Scores

31
Performance
no change
84
Accessibility
no change
96
Best Practices
no change
85
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 36.05 s 36.05 s 36.05 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 1.25 s 1.25 s 1.25 s
FCP First Contentful Paint 12.68 s 12.68 s 12.68 s
Speed Index 12.68 s 12.68 s 12.68 s
TTFB Time to First Byte 621 ms 621 ms 621 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.

element render delay 2.32 s
time to first byte 26 ms

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 2.51 s needs-improvement 74.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 171 ms good 79.2% good
CLS CWV 0 good 97.4% good
FCP 2.06 s needs-improvement 68.3% good
TTFB 1.00 s needs-improvement 61.1% good

Lab vs field

Lab LCP 36.05 s · field p75 2.51 s · real users are 0.07× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 2.56 s 161 ms 0 2.06 s 1.01 s
2026-08-08 2.47 s 162 ms 0 2.02 s 979 ms
2026-08-01 2.47 s 154 ms 0 2.02 s 972 ms
2026-07-25 2.59 s 162 ms 0 2.13 s 998 ms
2026-07-18 2.60 s 175 ms 0 2.12 s 984 ms
2026-07-11 2.83 s 174 ms 0 2.31 s 1.03 s
2026-07-04 3.09 s 166 ms 0 2.41 s 1.07 s
2026-06-27 3.08 s 146 ms 0 2.37 s 1.03 s
2026-06-20 3.19 s 200 ms 0 2.44 s 1.03 s
2026-06-13 3.20 s 197 ms 0 2.40 s 1.03 s
2026-06-06 3.13 s 190 ms 0 2.35 s 1.01 s
2026-05-30 2.96 s 189 ms 0 2.37 s 1.15 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 10.59 MB 10.59 MB 10.59 MB
Requests 150 150 150
Third-party Weight 921.3 kB 921.3 kB 921.3 kB
Third-party CPU 816 ms 816 ms 816 ms
Unused JS 384.8 kB 384.8 kB 384.8 kB
Unused CSS 33.0 kB 33.0 kB 33.0 kB

By resource type

image 4.59 MB · 41 req
font 3.33 MB · 10 req
script 2.11 MB · 47 req
document 447.6 kB · 8 req
stylesheet 109.0 kB · 21 req
other 2.7 kB · 21 req
third party 2.87 MB · 109 req

Third parties 9 entities

921.3 kB transferred, 816 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Google Tag Manager 491.6 kB · 88 ms CPU
posthog.com 193.9 kB · 213 ms CPU
Google Fonts 82.3 kB · 0 ms CPU
Sentry 75.4 kB · 483 ms CPU
FontAwesome CDN 33.0 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 9.43 s 9.43 s 9.43 s
Long Tasks 17 17 17
DOM Elements 662 662 662
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 114 114 114
A11y Failures 5 5 5
A11y Failing Nodes 34 34 34

Main thread work

script evaluation 4.69 s
other 2.30 s
paint composite render 1.10 s
style layout 864 ms
script parse compile 331 ms
parse HTML 127 ms
garbage collection 23 ms

Axe violations axe-core 4.13.0, full rule set

114 violating nodes across 7 rules, 1889 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.

  • moderate region — All page content should be contained by landmarks 64 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 20 nodes
  • critical aria-allowed-attr — Elements must only use supported ARIA attributes 7 nodes
  • serious aria-prohibited-attr — Elements must only use permitted ARIA attributes 7 nodes
  • critical button-name — Buttons must have discernible text 7 nodes
  • serious link-name — Links must have discernible text 5 nodes
  • critical image-alt — Images must have alternative text 4 nodes

Accessibility failures 5 of 29 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 23 nodes
  • link-name — Links do not have a discernible name 5 nodes
  • image-alt — Image elements do not have `[alt]` attributes 4 nodes
  • aria-prohibited-attr — Elements use prohibited ARIA attributes 1 node
  • landmark-one-main — Document does not have a main landmark. 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

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 PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 20, 2026, 3:47 PM UTC 31 36.05 s 0 1.25 s 10.59 MB 3/3 ±1 2,273 61.1s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show bayton.org'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://bayton.org/"></speedlify-score>