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 ·

1896gallery.com

https://www.1896gallery.com/

75 98 100 100 CWV 21AXE

Data from Aug 21, 2026, 9:37 AM UTC — 9h old.

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

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 0.11.0 Built with Eleventy 0.11.0
Netlify Hosted by Netlify

Scores

75
Performance
no change
98
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 1.85 s 1.85 s 1.85 s
CLS Cumulative Layout Shift 1.002 1.002 1.002
TBT Total Blocking Time 28 ms 28 ms 28 ms
FCP First Contentful Paint 955 ms 955 ms 955 ms
Speed Index 955 ms 955 ms 955 ms
TTFB Time to First Byte 655 ms 655 ms 655 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 duration 87 ms
time to first byte 31 ms
element render delay 25 ms
resource load delay 11 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 3.19 MB 3.19 MB 3.19 MB
Requests 54 54 54
Third-party Weight 81.7 kB 81.7 kB 81.7 kB
Third-party CPU 4 ms 4 ms 4 ms
Unused JS 48.8 kB 48.8 kB 48.8 kB
Unused CSS 0 B 0 B 0 B

By resource type

image 2.98 MB · 34 req
script 90.4 kB · 6 req
font 88.5 kB · 6 req
stylesheet 14.9 kB · 4 req
document 10.2 kB · 1 req
other 3.1 kB · 3 req
third party 81.7 kB · 8 req

Third parties 3 entities

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

openstreetmap.org 77.0 kB · 0 ms CPU
zgo.at 4.4 kB · 4 ms CPU
goatcounter.com 381 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.20 s 1.20 s 1.20 s
Long Tasks 1 1 1
DOM Elements 426 426 426
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 21 21 21
A11y Failures 2 2 2
A11y Failing Nodes 2 2 2

Main thread work

style layout 429 ms
other 421 ms
script evaluation 179 ms
paint composite render 92 ms
parse HTML 43 ms
script parse compile 38 ms

Axe violations axe-core 4.13.0, full rule set

21 violating nodes across 4 rules, 733 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 15 nodes
  • serious role-img-alt — [role="img"] and [role="image"] elements must have alternative text 4 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • minor presentation-role-conflict — Elements marked as presentational should be consistently ignored 1 node

Accessibility failures 2 of 28 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.

  • landmark-one-main — Document does not have a main landmark. 1 node
  • presentation-role-conflict — Elements with `role="none"` or `role="presentation"` have conflicts 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 21, 2026, 9:37 AM UTC 75 1.85 s 1.002 28 ms 3.19 MB 3/3 ±17 2,498 26.1s

Embed this score

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