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 ·

germanfrelo.dev

https://germanfrelo.dev/

82 100 100 100 –CWV 0AXE

Data from Aug 20, 2026, 11:26 PM UTC — 19h old.

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

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.2 Built with Eleventy 3.1.2
Netlify Hosted by Netlify

Scores

82
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 2.58 s — — 2.58 s 2.58 s
CLS Cumulative Layout Shift 0.219 — — 0.219 0.219
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 2.58 s — — 2.58 s 2.58 s
Speed Index 2.58 s — — 2.58 s 2.58 s
TTFB Time to First Byte 605 ms — — 605 ms 605 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 58 ms
time to first byte 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 79.5 kB — — 79.5 kB 79.5 kB
Requests 8 — — 8 8
Third-party Weight 70.8 kB — — 70.8 kB 70.8 kB
Third-party CPU 5 ms — — 5 ms 5 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 61.2 kB · 2 req
stylesheet 9.9 kB · 3 req
script 4.9 kB · 1 req
document 3.4 kB · 1 req
image 95 B · 1 req
third party 70.8 kB · 6 req

Third parties 3 entities

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

Google Fonts 62.0 kB · 0 ms CPU
simpleanalyticscdn.com 5.0 kB · 5 ms CPU
GitHub 3.7 kB · 0 ms CPU

Page health

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

Main thread work

style layout 94 ms
other 79 ms
script evaluation 30 ms
paint composite render 10 ms
parse HTML 9 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 302 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.

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

  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 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, 11:26 PM UTC 82 2.58 s 0.219 0 ms 79.5 kB 3/3 ±13 2,465 22.5s

Embed this score

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