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 ·

wrapmate.com

https://wrapmate.com/

61 93 58 100 ✗CWV 19AXE

Data from Aug 21, 2026, 9:36 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.

Amazon S3 Hosted by Amazon S3

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 1.02 s good
INP 244 ms needs-improvement
CLS 0.010 good

Scores

61
Performance
no change
93
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 2.80 s — — 2.80 s 2.80 s
CLS Cumulative Layout Shift 0.027 — — 0.027 0.027
TBT Total Blocking Time 3.59 s — — 3.59 s 3.59 s
FCP First Contentful Paint 2.80 s — — 2.80 s 2.80 s
Speed Index 3.22 s — — 3.22 s 3.22 s
TTFB Time to First Byte 638 ms — — 638 ms 638 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 145 ms
time to first byte 36 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 1.02 s good 95.5% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 244 ms needs-improvement 64.5% good
CLS CWV 0.010 good 100% good
FCP 1.00 s good 91.3% good
TTFB 601 ms good 86.2% good

Lab vs field

Lab LCP 2.80 s · field p75 1.02 s · real users are 0.36× 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 1.02 s 238 ms 0.010 1.01 s 599 ms
2026-08-08 1.03 s 244 ms 0.010 1.01 s 593 ms
2026-08-01 1.01 s 245 ms 0.010 986 ms 579 ms
2026-07-25 989 ms 239 ms 0.010 977 ms 565 ms
2026-07-18 995 ms 244 ms 0.010 980 ms 568 ms
2026-07-11 1.01 s 240 ms 0.010 990 ms 583 ms
2026-07-04 1.03 s 231 ms 0.010 1.00 s 604 ms
2026-06-27 1.04 s 238 ms 0.010 1.02 s 601 ms
2026-06-20 1.09 s 236 ms 0.010 1.07 s 605 ms
2026-06-13 1.07 s 221 ms 0.010 1.03 s 605 ms
2026-06-06 1.09 s 230 ms 0.010 1.07 s 603 ms
2026-05-30 1.12 s 221 ms 0.010 1.12 s 645 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 6.68 MB — — 6.68 MB 6.68 MB
Requests 170 — — 170 170
Third-party Weight 2.20 MB — — 2.20 MB 2.20 MB
Third-party CPU 1.55 s — — 1.55 s 1.55 s
Unused JS 675.9 kB — — 675.9 kB 675.9 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 2.23 MB · 60 req
media 2.20 MB · 1 req
script 2.12 MB · 45 req
font 48.5 kB · 1 req
document 35.9 kB · 5 req
other 35.9 kB · 54 req
stylesheet 1.0 kB · 1 req
third party 2.20 MB · 114 req

Third parties 26 entities

2.20 MB transferred, 1.55 s of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Google Tag Manager 1.06 MB · 580 ms CPU
Facebook 278.9 kB · 246 ms CPU
TikTok 173.3 kB · 67 ms CPU
Mixpanel 138.2 kB · 45 ms CPU
Hubspot 133.3 kB · 86 ms CPU

Page health

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

Main thread work

script evaluation 6.95 s
other 1.77 s
script parse compile 744 ms
style layout 397 ms
paint composite render 244 ms
garbage collection 188 ms
parse HTML 106 ms

Axe violations axe-core 4.13.0, full rule set

19 violating nodes across 3 rules, 1530 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
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 2 nodes
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 2 of 26 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
  • target-size — Touch targets do not have sufficient size or spacing. 3 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, 9:36 AM UTC 61 2.80 s 0.027 3.59 s 6.68 MB 3/3 ±20 2,508 65.8s

Embed this score

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