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 ·

11straps.com

https://11straps.com/

93 95 96 100 –CWV 1AXE

Data from Aug 20, 2026, 7:03 PM UTC — 24h old.

Build Awesome Starters · 1 measurement · since Aug 20, 2026 · last attempt 24h

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.

Netlify Hosted by Netlify

Scores

93
Performance
no change
95
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.60 s — — 2.60 s 2.60 s
CLS Cumulative Layout Shift 0.004 — — 0.004 0.004
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 2.60 s — — 2.60 s 2.60 s
Speed Index 2.60 s — — 2.60 s 2.60 s
TTFB Time to First Byte 603 ms — — 603 ms 603 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 94 ms
time to first byte 5 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 89.8 kB — — 89.8 kB 89.8 kB
Requests 14 — — 14 14
Third-party Weight 49.8 kB — — 49.8 kB 49.8 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 48.5 kB · 1 req
script 22.4 kB · 2 req
image 11.3 kB · 6 req
stylesheet 4.0 kB · 2 req
document 2.1 kB · 1 req
other 1.4 kB · 1 req
third party 49.8 kB · 3 req

Third parties 2 entities

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

Google Fonts 49.3 kB · 0 ms CPU
splitbee.io 534 B · 0 ms CPU

Page health

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

Main thread work

other 117 ms
style layout 74 ms
script evaluation 17 ms
paint composite render 14 ms
script parse compile 10 ms
parse HTML 8 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 147 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 1 node

Accessibility failures 1 of 17 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. 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 1 console error

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 20, 2026, 7:03 PM UTC 93 2.60 s 0.004 0 ms 89.8 kB 3/3 ±6 2,515 25s

Embed this score

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