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 ·

printsgram.com

https://printsgram.com/

81 96 100 100 –CWV 16AXE

Data from Aug 21, 2026, 2:38 PM UTC — 4h old.

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

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.2 Built with Eleventy 3.1.2
Cloudflare Hosted by Cloudflare

Scores

81
Performance
no change
96
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.50 s — — 3.50 s 3.50 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 214 ms — — 214 ms 214 ms
FCP First Contentful Paint 3.21 s — — 3.21 s 3.21 s
Speed Index 3.21 s — — 3.21 s 3.21 s
TTFB Time to First Byte 458 ms — — 458 ms 458 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.

time to first byte 208 ms
element render delay 120 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 424.6 kB — — 424.6 kB 424.6 kB
Requests 15 — — 15 15
Third-party Weight 392.4 kB — — 392.4 kB 392.4 kB
Third-party CPU 94 ms — — 94 ms 94 ms
Unused JS 137.1 kB — — 137.1 kB 137.1 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 312.2 kB · 5 req
font 83.2 kB · 2 req
stylesheet 17.4 kB · 4 req
document 7.5 kB · 1 req
other 4.3 kB · 3 req
third party 392.4 kB · 8 req

Third parties 3 entities

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

Google Tag Manager 296.0 kB · 91 ms CPU
Google Fonts 85.0 kB · 0 ms CPU
Cloudflare 11.5 kB · 3 ms CPU

Page health

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

Main thread work

script evaluation 334 ms
other 115 ms
style layout 95 ms
script parse compile 70 ms
parse HTML 24 ms
paint composite render 13 ms

Axe violations axe-core 4.13.0, full rule set

16 violating nodes across 1 rule, 367 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 16 nodes

Accessibility failures 1 of 22 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. 16 nodes

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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, 2:38 PM UTC 81 3.50 s 0 214 ms 424.6 kB 3/3 ±2 2,499 24.5s

Embed this score

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