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 ·

jules.poulain.dev

https://jules.poulain.dev/

79 89 100 100 –CWV 10AXE

Data from Aug 21, 2026, 3:02 AM UTC — 16h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 16h

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
Bu Hosted by Bunny CDN

Scores

79
Performance
no change
89
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 4.67 s — — 4.67 s 4.67 s
CLS Cumulative Layout Shift 0.064 — — 0.064 0.064
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 2.45 s — — 2.45 s 2.45 s
Speed Index 2.45 s — — 2.45 s 2.45 s
TTFB Time to First Byte 622 ms — — 622 ms 622 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 94 ms
time to first byte 22 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 598.5 kB — — 598.5 kB 598.5 kB
Requests 16 — — 16 16
Third-party Weight 36.3 kB — — 36.3 kB 36.3 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 555.4 kB · 12 req
font 35.5 kB · 1 req
document 4.0 kB · 1 req
stylesheet 3.6 kB · 2 req
third party 36.3 kB · 2 req

Third parties 1 entities

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

Google Fonts 36.3 kB · 0 ms CPU

Page health

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

Main thread work

other 470 ms
style layout 75 ms
paint composite render 20 ms
script evaluation 12 ms
parse HTML 9 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

10 violating nodes across 3 rules, 334 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 8 nodes
  • serious html-has-lang — <html> element must have a lang attribute 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 2 of 13 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.

  • html-has-lang — `<html>` element does not have a `[lang]` attribute 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 21, 2026, 3:02 AM UTC 79 4.67 s 0.064 0 ms 598.5 kB 3/3 ±5 2,321 23.8s

Embed this score

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