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 ·

firekeepers.info

https://firekeepers.info/

98 98 100 100 –CWV 11AXE

Data from Aug 20, 2026, 10:33 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.

Eleventy 3.1.6 Built with Eleventy 3.1.6
Netlify Hosted by Netlify

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP — no data
INP — no data
CLS — no data

Scores

98
Performance
no change
98
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.93 s — — 1.93 s 1.93 s
CLS Cumulative Layout Shift 0.022 — — 0.022 0.022
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.85 s — — 1.85 s 1.85 s
Speed Index 1.85 s — — 1.85 s 1.85 s
TTFB Time to First Byte 481 ms — — 481 ms 481 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 62 ms
time to first byte 31 ms

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 — — — — —
2026-08-08 935 ms — 0 899 ms 745 ms
2026-08-01 971 ms 68 ms 0 934 ms 799 ms
2026-07-25 907 ms 71 ms 0 878 ms 692 ms
2026-07-18 853 ms — 0 839 ms 654 ms
2026-07-11 955 ms — 0 897 ms 692 ms
2026-07-04 906 ms 70 ms 0 897 ms 663 ms
2026-06-27 919 ms — 0 920 ms 702 ms
2026-06-20 981 ms — 0 970 ms —
2026-06-13 1.04 s — 0 988 ms 860 ms
2026-06-06 1.05 s — 0 1.04 s 894 ms
2026-05-30 1.19 s — 0 1.18 s 989 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 666.3 kB — — 666.3 kB 666.3 kB
Requests 19 — — 19 19
Third-party Weight 272.0 kB — — 272.0 kB 272.0 kB
Third-party CPU 3 ms — — 3 ms 3 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 51.8 kB — — 51.8 kB 51.8 kB

By resource type

image 324.2 kB · 7 req
font 243.3 kB · 4 req
document 45.4 kB · 1 req
script 35.7 kB · 3 req
stylesheet 17.3 kB · 1 req
other 447 B · 2 req
third party 272.0 kB · 6 req

Third parties 3 entities

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

Cloudflare CDN 252.6 kB · 0 ms CPU
Cloudflare 11.5 kB · 3 ms CPU
Google Fonts 7.9 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 404 ms — — 404 ms 404 ms
Long Tasks 0 — — 0 0
DOM Elements 495 — — 495 495
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 11 — — 11 11
A11y Failures 1 — — 1 1
A11y Failing Nodes 1 — — 1 1

Main thread work

style layout 149 ms
other 131 ms
parse HTML 48 ms
script evaluation 41 ms
paint composite render 28 ms
script parse compile 7 ms

Axe violations axe-core 4.13.0, full rule set

11 violating nodes across 3 rules, 808 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 9 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 1 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.

  • 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 h3

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, 10:33 PM UTC 98 1.93 s 0.022 0 ms 666.3 kB 3/3 ±1 3,397 25.6s

Embed this score

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