speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

nordcraft.com

https://nordcraft.com/

52 100 96 100 ✗AXE ✗CWV

Data from Aug 25, 2026, 1:49 PM UTC 6h old

Overall #1,438 Website Builders #3 · 1 measurement · since Aug 25, 2026

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.

Cloudflare Hosted by Cloudflare

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-27 → 2026-08-23). This is what Google measures you on.

LCP 3.49 s needs-improvement
INP — no data
CLS 0 good

Scores

52
Performance
no change
100
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 10.12 s.

  1. 1.26 s
  2. 2.53 s
  3. 3.79 s
  4. 5.06 s
  5. 6.33 s
  6. 7.59 s
  7. 8.86 s
  8. 10.12 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 11.54 s — — 11.54 s 11.54 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 523 ms — — 523 ms 523 ms
FCP First Contentful Paint 3.22 s — — 3.22 s 3.22 s
Speed Index 5.00 s — — 5.00 s 5.00 s
TTFB Time to First Byte 1.03 s — — 1.03 s 1.03 s

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 11.54 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 6.58 s
time to first byte 1.03 s
resource load duration 378 ms
resource load delay 84 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-27 → 2026-08-23). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 3.49 s needs-improvement 52.2% good
CLS CWV 0 good 91.9% good
FCP 2.90 s needs-improvement 46.9% good
TTFB 2.17 s poor 39.5% good

Lab vs field

Lab LCP 11.54 s · field p75 3.49 s · real users are 0.3× 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-22 3.68 s — 0 2.90 s 2.26 s
2026-08-15 3.48 s 237 ms 0 2.72 s 2.09 s
2026-08-08 3.50 s — 0 2.72 s 1.97 s
2026-08-01 3.37 s 223 ms 0 2.50 s 1.84 s
2026-07-25 3.60 s 249 ms 0 2.43 s 1.84 s
2026-07-18 3.77 s 278 ms 0 2.81 s 2.03 s
2026-07-11 3.67 s 274 ms 0 2.78 s 2.01 s
2026-07-04 3.60 s 253 ms 0 2.61 s 2.01 s
2026-06-27 3.32 s 222 ms 0 2.55 s 1.94 s
2026-06-20 3.61 s 197 ms 0 2.47 s 1.81 s
2026-06-13 3.32 s 176 ms 0 2.18 s 1.51 s
2026-06-06 3.33 s 210 ms 0.020 2.08 s 1.48 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 6.37 MB — — 6.37 MB 6.37 MB
Requests 150 — — 150 150
Third-party Weight 1.16 MB — — 1.16 MB 1.16 MB
Third-party CPU 1 ms — — 1 ms 1 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 47.7 kB — — 47.7 kB 47.7 kB

By resource type

media 2.76 MB · 4 req
image 1.86 MB · 80 req
font 1.18 MB · 10 req
script 395 kB · 8 req
document 121 kB · 1 req
stylesheet 47.2 kB · 4 req
other 11.7 kB · 43 req
third party 1.16 MB · 12 req

Third parties 3 entities

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

toddle.site 1.15 MB · 1 ms CPU
JSDelivr CDN 5.1 kB · 0 ms CPU
toddle.dev 3.6 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 5.72 s — — 5.72 s 5.72 s
Long Tasks 15 — — 15 15
DOM Elements 3,667 — — 3,667 3,667
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 179 — — 179 179
A11y Failures 1 — — 1 1
A11y Failing Nodes 1 — — 1 1

Main thread work

other 2.42 s
style layout 1.43 s
script evaluation 1.07 s
paint composite render 426 ms
parse HTML 249 ms
garbage collection 106 ms
script parse compile 20 ms

Axe violations axe-core 4.13.0, full rule set

179 violating nodes across 3 rules, 2743 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 177 nodes
  • minor image-redundant-alt — Alternative text of images should not be repeated as text 1 node
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 1 node

Accessibility failures 1 of 27 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.

  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 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 25, 2026, 1:49 PM UTC 52 11.54 s 0 523 ms 6.37 MB 3/3 ±2 3,029 52.9s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show nordcraft.com's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://nordcraft.com/"></speedlify2-score>