speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

neocities.org

https://neocities.org/

89 89 58 100 15AXE CWV

Data from Aug 23, 2026, 6:38 AM UTC 15h old

Web Hosts #4 · 3 measurements · since Aug 21, 2026

The measuring machine was faster than usual.

Lighthouse benchmark index was 3091 against a baseline of 2484.5 (24.4%). CPU-bound metrics — TBT, TTI, main thread work — are affected by this and may have moved without the site changing at all.

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-25 → 2026-08-21). This is what Google measures you on.

LCP 2.10 s good
INP 192 ms good
CLS 0 good

Scores

89
Performance
↑ +4 (+4.7%)
89
Accessibility
no change
58
Best Practices
no change
100
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.76 s 4.20 s ↓ -443 ms (-10.5%) significant 3.76 s 4.20 s
CLS Cumulative Layout Shift 0 0 → no change 0 0
TBT Total Blocking Time 22 ms 34 ms ↓ -12 ms (-35.3%) 22 ms 78 ms
FCP First Contentful Paint 1.51 s 1.80 s ↓ -293 ms (-16.2%) significant 1.51 s 1.82 s
Speed Index 1.51 s 1.80 s ↓ -293 ms (-16.2%) significant 1.51 s 1.82 s
TTFB Time to First Byte 611 ms 604 ms ↑ +7 ms (+1.2%) 604 ms 620 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 3.76 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

time to first byte 83 ms
resource load delay 62 ms
resource load duration 39 ms
element render delay 39 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 2.10 s good 82.8% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 192 ms good 75.6% good
CLS CWV 0 good 95.8% good
FCP 1.88 s needs-improvement 72.7% good
TTFB 1.36 s needs-improvement 56.8% good

Lab vs field

Lab LCP 3.76 s · field p75 2.10 s · real users are 0.56× 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.73 MB 2.55 MB ↑ +181.7 kB (+7.3%) 2.55 MB 2.73 MB
Requests 52 52 → no change 52 52
Third-party Weight 102 kB 102 kB ↓ -158 B (-0.2%) 102 kB 102 kB
Third-party CPU 44 ms 67 ms ↓ -23 ms (-33.7%) significant 44 ms 67 ms
Unused JS 52.7 kB 52.7 kB ↑ +14 B 52.7 kB 52.8 kB
Unused CSS 75.9 kB 75.9 kB → no change 75.9 kB 75.9 kB

By resource type

image 1.64 MB · 24 req
script 591 kB · 6 req
font 196 kB · 4 req
document 194 kB · 3 req
stylesheet 93.6 kB · 7 req
other 17.0 kB · 4 req
third party 742 kB · 7 req

Third parties 1 entities

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

hcaptcha.com 102 kB · 44 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 730 ms 907 ms ↓ -177 ms (-19.5%) significant 730 ms 907 ms
Long Tasks 3 2 ↑ +1 (+50%) 2 3
DOM Elements 263 263 → no change 263 263
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 15 15 → no change 15 15
A11y Failures 3 3 → no change 3 3
A11y Failing Nodes 13 13 → no change 13 13

Main thread work

other 225 ms
script evaluation 204 ms
style layout 146 ms
paint composite render 62 ms
script parse compile 48 ms
parse HTML 46 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 23, 2026, 6:38 AM UTC 89 3.76 s 0 22 ms 2.73 MB 3/3 ±31 3,091 32.1s
Aug 22, 2026, 6:38 AM UTC 85 4.20 s 0 34 ms 2.55 MB 3/3 ±32 2,483 31.7s
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 speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://neocities.org/"></speedlify2-score>