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 ·

expong.org

https://www.expong.org/

84 100 100 100 –CWV 0AXE

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

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

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

84
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 3.88 s — — 3.88 s 3.88 s
CLS Cumulative Layout Shift 0.101 — — 0.101 0.101
TBT Total Blocking Time 141 ms — — 141 ms 141 ms
FCP First Contentful Paint 856 ms — — 856 ms 856 ms
Speed Index 1.43 s — — 1.43 s 1.43 s
TTFB Time to First Byte 685 ms — — 685 ms 685 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 288 ms
time to first byte 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.26 MB — — 1.26 MB 1.26 MB
Requests 21 — — 21 21
Third-party Weight 386.2 kB — — 386.2 kB 386.2 kB
Third-party CPU 114 ms — — 114 ms 114 ms
Unused JS 143.9 kB — — 143.9 kB 143.9 kB
Unused CSS 21.3 kB — — 21.3 kB 21.3 kB

By resource type

image 720.5 kB · 7 req
script 385.7 kB · 5 req
font 148.0 kB · 3 req
stylesheet 5.0 kB · 2 req
document 2.6 kB · 1 req
other 86 B · 2 req
third party 386.2 kB · 8 req

Third parties 4 entities

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

Google Tag Manager 306.7 kB · 75 ms CPU
Netlify 55.4 kB · 25 ms CPU
Google Analytics 21.0 kB · 13 ms CPU
Fathom Analytics 3.2 kB · 1 ms CPU

Page health

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

Main thread work

script evaluation 416 ms
other 178 ms
script parse compile 107 ms
style layout 45 ms
paint composite render 15 ms
parse HTML 11 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 106 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.

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:34 PM UTC 84 3.88 s 0.101 141 ms 1.26 MB 1/3 — 2,367 131.5s

Embed this score

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