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 ·

ineliagestion.com

https://www.ineliagestion.com/

98 100 100 100 –CWV 11AXE

Data from Aug 21, 2026, 12:46 PM UTC — 6h old.

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

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.

Netlify Hosted by Netlify

Scores

98
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.16 s — — 2.16 s 2.16 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.68 s — — 1.68 s 1.68 s
Speed Index 1.68 s — — 1.68 s 1.68 s
TTFB Time to First Byte 624 ms — — 624 ms 624 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 48 ms
resource load duration 32 ms
resource load delay 29 ms
time to first byte 25 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 148.3 kB — — 148.3 kB 148.3 kB
Requests 13 — — 13 13
Third-party Weight 3.6 kB — — 3.6 kB 3.6 kB
Third-party CPU 3 ms — — 3 ms 3 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 16.9 kB — — 16.9 kB 16.9 kB

By resource type

font 47.5 kB · 3 req
image 39.2 kB · 3 req
script 30.4 kB · 3 req
document 29.1 kB · 1 req
other 2.1 kB · 2 req
third party 3.6 kB · 3 req

Third parties 2 entities

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

Plausible 2.4 kB · 3 ms CPU
instant.page 1.2 kB · 0 ms CPU

Page health

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

Main thread work

other 113 ms
script evaluation 83 ms
style layout 42 ms
parse HTML 20 ms
script parse compile 16 ms
paint composite render 9 ms

Axe violations axe-core 4.13.0, full rule set

11 violating nodes across 2 rules, 260 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 10 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 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, 12:46 PM UTC 98 2.16 s 0 0 ms 148.3 kB 3/3 ±2 2,481 23.2s

Embed this score

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