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 ·

innesi.fr

https://www.innesi.fr/

99 100 100 100 –CWV 1AXE

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

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 32m

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
Cloudflare Hosted by Cloudflare

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.96 s — — 1.96 s 1.96 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.53 s — — 1.53 s 1.53 s
Speed Index 1.53 s — — 1.53 s 1.53 s
TTFB Time to First Byte 614 ms — — 614 ms 614 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 122 ms
resource load duration 39 ms
element render delay 25 ms
resource load delay 9 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 150.7 kB — — 150.7 kB 150.7 kB
Requests 8 — — 8 8
Third-party Weight 11.5 kB — — 11.5 kB 11.5 kB
Third-party CPU 4 ms — — 4 ms 4 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 91.6 kB · 2 req
font 32.7 kB · 1 req
script 11.5 kB · 1 req
stylesheet 11.0 kB · 1 req
document 2.8 kB · 1 req
other 1.2 kB · 2 req
third party 11.5 kB · 1 req

Third parties 1 entities

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

Cloudflare 11.5 kB · 4 ms CPU

Page health

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

Main thread work

other 101 ms
style layout 47 ms
script evaluation 45 ms
paint composite render 9 ms
parse HTML 8 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 151 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 landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

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.

  • 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 21, 2026, 6:40 PM UTC 99 1.96 s 0 0 ms 150.7 kB 3/3 ±2 2,333 22.7s

Embed this score

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