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 ·

nicolas-birckel.fr

https://www.nicolas-birckel.fr/

99 96 100 91 –CWV 7AXE

Data from Aug 21, 2026, 6:36 PM UTC — 36m old.

Built Awesome · 2 measurements · since Aug 21, 2026 · last attempt 36m

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

Scores

99
Performance
no change
96
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.03 s — — 2.03 s 2.03 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 60 ms — — 60 ms 60 ms
FCP First Contentful Paint 903 ms — — 903 ms 903 ms
Speed Index 955 ms — — 955 ms 955 ms
TTFB Time to First Byte 718 ms — — 718 ms 718 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.

time to first byte 363 ms
element render delay 49 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 95.7 kB — — 95.7 kB 95.7 kB
Requests 5 — — 5 5
Third-party Weight 55.2 kB — — 55.2 kB 55.2 kB
Third-party CPU 26 ms — — 26 ms 26 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 21.3 kB — — 21.3 kB 21.3 kB

By resource type

script 56.3 kB · 2 req
font 30.7 kB · 1 req
document 6.1 kB · 1 req
other 2.6 kB · 1 req
third party 55.2 kB · 1 req

Third parties 1 entities

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

Netlify 55.2 kB · 26 ms CPU

Page health

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

Main thread work

other 98 ms
script evaluation 90 ms
style layout 64 ms
script parse compile 31 ms
parse HTML 15 ms
paint composite render 6 ms

Axe violations axe-core 4.13.0, full rule set

7 violating nodes across 1 rule, 219 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 color-contrast — Elements must meet minimum color contrast ratio thresholds 7 nodes

Accessibility failures 1 of 23 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. 6 nodes

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 21, 2026, 6:36 PM UTC 99 2.03 s 0 60 ms 95.7 kB 3/3 ±1 2,380 21.3s
Aug 21, 2026, 11:32 AM UTC TRACING_ALREADY_STARTED: An internal Chrome error occurred. Please restart Chrome and try re-running Lighthouse. 19.5s

Embed this score

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