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 ·

obspogon.neocities.org

https://obspogon.neocities.org/

89 57 92 75 CWV 61AXE

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

Built Awesome · 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.

Eleventy 3.1.5 Built with Eleventy 3.1.5
ne Hosted by neocities

Scores

89
Performance
no change
57
Accessibility
no change
92
Best Practices
no change
75
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.20 s 3.20 s 3.20 s
CLS Cumulative Layout Shift 0.064 0.064 0.064
TBT Total Blocking Time 17 ms 17 ms 17 ms
FCP First Contentful Paint 2.37 s 2.37 s 2.37 s
Speed Index 2.66 s 2.66 s 2.66 s
TTFB Time to First Byte 602 ms 602 ms 602 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 402 ms
time to first byte 54 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.73 MB 1.73 MB 1.73 MB
Requests 190 190 190
Third-party Weight 1.30 MB 1.30 MB 1.30 MB
Third-party CPU 63 ms 63 ms 63 ms
Unused JS 0 B 0 B 0 B
Unused CSS 14.8 kB 14.8 kB 14.8 kB

By resource type

image 790.4 kB · 75 req
font 434.1 kB · 8 req
script 341.6 kB · 40 req
document 89.3 kB · 12 req
other 55.3 kB · 39 req
stylesheet 18.7 kB · 13 req
third party 1.64 MB · 142 req

Third parties 21 entities

1.30 MB transferred, 63 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

FontAwesome CDN 889.7 kB · 45 ms CPU
cresentri.com 163.7 kB · 2 ms CPU
sertimus.xyz 60.2 kB · 3 ms CPU
jeith.com 48.0 kB · 0 ms CPU
gossipsweb.net 41.8 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 3.01 s 3.01 s 3.01 s
Long Tasks 6 6 6
DOM Elements 281 281 281
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 61 61 61
A11y Failures 7 7 7
A11y Failing Nodes 29 29 29

Main thread work

other 1.38 s
script evaluation 521 ms
style layout 478 ms
paint composite render 430 ms
parse HTML 109 ms
script parse compile 87 ms

Axe violations axe-core 4.13.0, full rule set

61 violating nodes across 11 rules, 912 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 23 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 15 nodes
  • serious link-name — Links must have discernible text 6 nodes
  • serious frame-title — Frames must have an accessible name 5 nodes
  • critical image-alt — Images must have alternative text 4 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 3 nodes
  • serious aria-input-field-name — ARIA input fields must have an accessible name 1 node
  • critical button-name — Buttons must have discernible text 1 node
  • moderate meta-viewport — Zooming and scaling must not be disabled 1 node
  • serious object-alt — <object> elements must have alternative text 1 node

Accessibility failures 7 of 19 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. 13 nodes
  • frame-title — `<frame>` or `<iframe>` elements do not have a title 4 nodes
  • image-alt — Image elements do not have `[alt]` attributes 4 nodes
  • link-name — Links do not have a discernible name 3 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 3 nodes
  • meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 1 node
  • object-alt — `<object>` elements do not have alternate text 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 3 console errors

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:33 AM UTC 89 3.20 s 0.064 17 ms 1.73 MB 3/3 ±3 2,485 125.9s

Embed this score

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