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 ·

frontendnorth.com

https://frontendnorth.com/

99 100 100 100 –CWV 1AXE

Data from Aug 20, 2026, 10:52 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.0.0 Built with Eleventy 3.0.0

Scores

99
Performance
no change
100
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.55 s — — 1.55 s 1.55 s
CLS Cumulative Layout Shift 0.001 — — 0.001 0.001
TBT Total Blocking Time 2 ms — — 2 ms 2 ms
FCP First Contentful Paint 1.55 s — — 1.55 s 1.55 s
Speed Index 1.55 s — — 1.55 s 1.55 s
TTFB Time to First Byte 610 ms — — 610 ms 610 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 93 ms
time to first byte 12 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 538.0 kB — — 538.0 kB 538.0 kB
Requests 24 — — 24 24
Third-party Weight 506.4 kB — — 506.4 kB 506.4 kB
Third-party CPU 17 ms — — 17 ms 17 ms
Unused JS 96.6 kB — — 96.6 kB 96.6 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 311.5 kB · 12 req
script 146.9 kB · 3 req
font 57.2 kB · 2 req
document 9.2 kB · 1 req
stylesheet 8.8 kB · 2 req
other 4.5 kB · 4 req
third party 506.4 kB · 14 req

Third parties 4 entities

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

Sirv 301.6 kB · 0 ms CPU
Amazon Web Services 143.7 kB · 14 ms CPU
Google Fonts 58.1 kB · 0 ms CPU
Plausible 3.0 kB · 3 ms CPU

Page health

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

Main thread work

other 195 ms
style layout 145 ms
script evaluation 68 ms
parse HTML 34 ms
paint composite render 33 ms
script parse compile 13 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 428 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 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, 10:52 PM UTC 99 1.55 s 0.001 2 ms 538.0 kB 3/3 ±24 2,656 26.5s

Embed this score

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