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 ·

tilda.cc

https://tilda.cc/

62 81 100 92 AXE CWV

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

Overall #1,450 Website Builders #4 · 1 measurement · since Aug 25, 2026

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.28 s needs-improvement
INP 245 ms needs-improvement
CLS 0.390 poor

Scores

62
Performance
no change
81
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Filmstrip Lighthouse, mobile

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

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.15 s 5.15 s 5.15 s
CLS Cumulative Layout Shift 0.308 0.308 0.308
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 2.38 s 2.38 s 2.38 s
Speed Index 2.38 s 2.38 s 2.38 s
TTFB Time to First Byte 673 ms 673 ms 673 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 5.15 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 652 ms
resource load delay 467 ms
time to first byte 75 ms
resource load duration 7 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.28 s needs-improvement 59.6% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 245 ms needs-improvement 67.4% good
CLS CWV 0.390 poor 47.3% good
FCP 1.95 s needs-improvement 70.9% good
TTFB 1.24 s needs-improvement 55.9% good

Lab vs field

Lab LCP 5.15 s · field p75 3.28 s · real users are 0.64× 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.28 s 244 ms 0.390 1.97 s 1.25 s
2026-08-15 3.30 s 255 ms 0.390 2.02 s 1.28 s
2026-08-08 3.33 s 261 ms 0.390 2.06 s 1.29 s
2026-08-01 3.39 s 273 ms 0.390 2.12 s 1.32 s
2026-07-25 3.36 s 271 ms 0.390 2.12 s 1.31 s
2026-07-18 3.40 s 278 ms 0.390 2.14 s 1.32 s
2026-07-11 3.37 s 285 ms 0.370 2.11 s 1.31 s
2026-07-04 3.32 s 281 ms 0.370 2.04 s 1.28 s
2026-06-27 3.30 s 281 ms 0.370 2.00 s 1.24 s
2026-06-20 3.21 s 267 ms 0.350 1.93 s 1.21 s
2026-06-13 3.10 s 249 ms 0.320 1.85 s 1.15 s
2026-06-06 2.98 s 225 ms 0.250 1.79 s 1.11 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 695 kB 695 kB 695 kB
Requests 99 99 99
Third-party Weight 582 kB 582 kB 582 kB
Third-party CPU 50 ms 50 ms 50 ms
Unused JS 24.0 kB 24.0 kB 24.0 kB
Unused CSS 0 B 0 B 0 B

By resource type

image 374 kB · 60 req
document 113 kB · 1 req
script 106 kB · 25 req
font 85.6 kB · 1 req
stylesheet 15.6 kB · 8 req
other 1.2 kB · 2 req
third party 582 kB · 96 req

Third parties 2 entities

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

tildacdn.net 495 kB · 49 ms CPU
Tilda 86.9 kB · 1 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 5.47 s 5.47 s 5.47 s
Long Tasks 9 9 9
DOM Elements 1,704 1,704 1,704
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 103 103 103
A11y Failures 6 6 6
A11y Failing Nodes 65 65 65

Main thread work

paint composite render 1.89 s
other 1.62 s
style layout 1.46 s
script evaluation 324 ms
parse HTML 95 ms
script parse compile 84 ms

Axe violations axe-core 4.13.0, full rule set

103 violating nodes across 8 rules, 2255 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 62 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 25 nodes
  • minor aria-allowed-role — ARIA role should be appropriate for the element 9 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 3 nodes
  • critical button-name — Buttons must have discernible text 1 node
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • serious summary-name — Summary elements must have discernible text 1 node

Accessibility failures 6 of 29 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. 37 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 22 nodes
  • link-in-text-block — Links rely on color to be distinguishable. 3 nodes
  • button-name — Buttons do not have an accessible name 1 node
  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • landmark-one-main — Document does not have a main landmark. 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

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:50 PM UTC 62 5.15 s 0.308 0 ms 695 kB 3/3 ±4 2,353 40.4s

Embed this score

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