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 ·

duda.co

https://www.duda.co/

32 93 54 100 !AXE CWV

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

Overall #1,460 Website Builders #7 · 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.

Self-hosted · nginx Hosted by Self-hosted

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 2.63 s needs-improvement
INP 254 ms needs-improvement
CLS 0.020 good

Scores

32
Performance
no change
93
Accessibility
no change
54
Best Practices
no change
100
SEO
no change

Filmstrip Lighthouse, mobile

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

  1. 553 ms
  2. 1.11 s
  3. 1.66 s
  4. 2.21 s
  5. 2.77 s
  6. 3.32 s
  7. 3.87 s
  8. 4.43 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 37.67 s 37.67 s 37.67 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 1.14 s 1.14 s 1.14 s
FCP First Contentful Paint 15.90 s 15.90 s 15.90 s
Speed Index 15.90 s 15.90 s 15.90 s
TTFB Time to First Byte 605 ms 605 ms 605 ms

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 37.67 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 2.17 s
time to first byte 6 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 2.63 s needs-improvement 72.7% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 254 ms needs-improvement 69.5% good
CLS CWV 0.020 good 88.5% good
FCP 2.31 s needs-improvement 61.6% good
TTFB 1.07 s needs-improvement 62.1% good

Lab vs field

Lab LCP 37.67 s · field p75 2.63 s · real users are 0.07× 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 2.63 s 251 ms 0.020 2.33 s 1.08 s
2026-08-15 2.63 s 257 ms 0.020 2.33 s 1.10 s
2026-08-08 2.45 s 245 ms 0.020 2.24 s 1.07 s
2026-08-01 2.30 s 261 ms 0.020 2.06 s 1.01 s
2026-07-25 2.06 s 278 ms 0.020 1.91 s 955 ms
2026-07-18 2.06 s 294 ms 0.020 1.92 s 956 ms
2026-07-11 2.06 s 306 ms 0.020 1.96 s 984 ms
2026-07-04 2.14 s 300 ms 0.010 2.03 s 1.02 s
2026-06-27 2.25 s 296 ms 0 2.08 s 1.06 s
2026-06-20 2.09 s 282 ms 0 2.00 s 1.01 s
2026-06-13 2.07 s 263 ms 0 1.93 s 993 ms
2026-06-06 2.03 s 269 ms 0 1.88 s 977 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 15.04 MB 15.04 MB 15.04 MB
Requests 287 287 287
Third-party Weight 20.43 MB 20.43 MB 20.43 MB
Third-party CPU 1.95 s 1.95 s 1.95 s
Unused JS 960 kB 960 kB 960 kB
Unused CSS 0 B 0 B 0 B

By resource type

media 9.07 MB · 14 req
script 2.77 MB · 86 req
image 2.59 MB · 105 req
font 315 kB · 12 req
stylesheet 105 kB · 14 req
other 96.3 kB · 50 req
document 84.2 kB · 2 req
third party 14.83 MB · 278 req

Third parties 34 entities

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

cdn-website.com 17.87 MB · 96 ms CPU
Google Tag Manager 677 kB · 273 ms CPU
audioeye.com 296 kB · 1.05 s CPU
multiscreensite.com 247 kB · 0 ms CPU
Facebook 230 kB · 90 ms CPU

Page health

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

Main thread work

script evaluation 8.58 s
other 4.34 s
style layout 1.60 s
script parse compile 654 ms
paint composite render 613 ms
garbage collection 359 ms
parse HTML 164 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 3 rules, 10 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 2 nodes
  • serious html-has-lang — <html> element must have a lang attribute 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 3 of 31 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. 2 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 1 node
  • link-name — Links do not have a discernible name 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 3 console errors

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:52 PM UTC 32 37.67 s 0 1.14 s 15.04 MB 3/3 ±4 3,244 204.7s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show duda.co'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://www.duda.co/"></speedlify2-score>