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 ·

neocities.org

https://neocities.org/

86 89 58 100 ✓CWV 15AXE

Data from Aug 21, 2026, 5:38 AM UTC — 13h old.

Web Hosts · 1 measurement · since Aug 21, 2026 · last attempt 13h

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.

ne Hosted by neocities

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.

LCP 2.10 s good
INP 194 ms good
CLS 0 good

Scores

86
Performance
no change
89
Accessibility
no change
58
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.07 s — — 4.07 s 4.07 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 78 ms — — 78 ms 78 ms
FCP First Contentful Paint 1.82 s — — 1.82 s 1.82 s
Speed Index 1.82 s — — 1.82 s 1.82 s
TTFB Time to First Byte 620 ms — — 620 ms 620 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.

resource load delay 82 ms
resource load duration 55 ms
time to first byte 45 ms
element render delay 43 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 2.10 s good 82.6% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 194 ms good 74.9% good
CLS CWV 0 good 95.7% good
FCP 1.89 s needs-improvement 72.3% good
TTFB 1.35 s needs-improvement 56.9% good

Lab vs field

Lab LCP 4.07 s · field p75 2.10 s · real users are 0.52× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 2.10 s 198 ms 0 1.87 s 1.34 s
2026-08-08 2.09 s 194 ms 0 1.86 s 1.33 s
2026-08-01 2.08 s 194 ms 0 1.85 s 1.33 s
2026-07-25 2.06 s 197 ms 0 1.82 s 1.32 s
2026-07-18 2.03 s 188 ms 0 1.79 s 1.29 s
2026-07-11 2.02 s 195 ms 0 1.78 s 1.29 s
2026-07-04 2.04 s 197 ms 0 1.78 s 1.28 s
2026-06-27 2.04 s 183 ms 0 1.78 s 1.30 s
2026-06-20 2.06 s 196 ms 0 1.80 s 1.30 s
2026-06-13 2.08 s 198 ms 0 1.84 s 1.33 s
2026-06-06 2.13 s 199 ms 0 1.90 s 1.38 s
2026-05-30 2.18 s 206 ms 0 1.94 s 1.41 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.66 MB — — 2.66 MB 2.66 MB
Requests 52 — — 52 52
Third-party Weight 102.0 kB — — 102.0 kB 102.0 kB
Third-party CPU 66 ms — — 66 ms 66 ms
Unused JS 52.8 kB — — 52.8 kB 52.8 kB
Unused CSS 75.9 kB — — 75.9 kB 75.9 kB

By resource type

image 1.56 MB · 24 req
script 594.4 kB · 6 req
font 196.2 kB · 4 req
document 193.9 kB · 3 req
stylesheet 93.6 kB · 7 req
other 17.2 kB · 4 req
third party 746.2 kB · 7 req

Third parties 1 entities

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

hcaptcha.com 102.0 kB · 66 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 906 ms — — 906 ms 906 ms
Long Tasks 3 — — 3 3
DOM Elements 263 — — 263 263
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 15 — — 15 15
A11y Failures 3 — — 3 3
A11y Failing Nodes 13 — — 13 13

Main thread work

script evaluation 284 ms
other 271 ms
style layout 176 ms
script parse compile 68 ms
paint composite render 56 ms
parse HTML 51 ms

Axe violations axe-core 4.13.0, full rule set

15 violating nodes across 5 rules, 640 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.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 9 nodes
  • critical label — Form elements must have labels 2 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 2 nodes
  • moderate landmark-contentinfo-is-top-level — Contentinfo landmark should not be contained in another landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 3 of 31 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 9 nodes
  • label — Form elements do not have associated labels 2 nodes
  • link-in-text-block — Links rely on color to be distinguishable. 2 nodes

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, 5:38 AM UTC 86 4.07 s 0 78 ms 2.66 MB 3/3 ±25 2,487 30s

Embed this score

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