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 ·

ecsspert.com

https://ecsspert.com/

100 97 100 100 –CWV 1AXE

Data from Aug 20, 2026, 9:30 PM UTC — 21h old.

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

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

100
Performance
no change
97
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 788 ms — — 788 ms 788 ms
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 788 ms — — 788 ms 788 ms
Speed Index 788 ms — — 788 ms 788 ms
TTFB Time to First Byte 618 ms — — 618 ms 618 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 35 ms
time to first byte 13 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 5.6 kB — — 5.6 kB 5.6 kB
Requests 4 — — 4 4
Third-party Weight 103 B — — 103 B 103 B
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

script 3.2 kB · 1 req
document 2.1 kB · 1 req
other 270 B · 2 req
third party 103 B · 1 req

Third parties 1 entities

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

Google Analytics 103 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 110 ms — — 110 ms 110 ms
Long Tasks 0 — — 0 0
DOM Elements 22 — — 22 22
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 62 ms
script evaluation 23 ms
style layout 16 ms
parse HTML 4 ms
paint composite render 3 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 56 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 heading-order — Heading levels should only increase by one 1 node

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

  • heading-order — Heading elements are not in a sequentially-descending order 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, 9:30 PM UTC 100 788 ms 0 0 ms 5.6 kB 3/3 ±0 2,361 20.3s

Embed this score

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