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 ·

wix.com

https://www.wix.com/

51 93 73 92 !AXE ✗CWV

Data from Aug 25, 2026, 2:00 PM UTC 6h old

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

Wix Built with Wix
Pe Hosted by Pepyaka

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.48 s needs-improvement
INP 460 ms needs-improvement
CLS 0 good

Scores

51
Performance
no change
93
Accessibility
no change
73
Best Practices
no change
92
SEO
no change

Filmstrip Lighthouse, mobile

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

  1. 740 ms
  2. 1.48 s
  3. 2.22 s
  4. 2.96 s
  5. 3.70 s
  6. 4.44 s
  7. 5.18 s
  8. 5.92 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.98 s — — 3.98 s 3.98 s
CLS Cumulative Layout Shift 0.068 — — 0.068 0.068
TBT Total Blocking Time 1.90 s — — 1.90 s 1.90 s
FCP First Contentful Paint 3.68 s — — 3.68 s 3.68 s
Speed Index 3.68 s — — 3.68 s 3.68 s
TTFB Time to First Byte 675 ms — — 675 ms 675 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 3.98 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 146 ms
time to first byte 23 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.48 s needs-improvement 60.2% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 460 ms needs-improvement 45.2% good
CLS CWV 0 good 94.9% good
FCP 2.38 s needs-improvement 64.6% good
TTFB 959 ms needs-improvement 69.6% good

Lab vs field

Lab LCP 3.98 s · field p75 3.48 s · real users are 0.87× 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.49 s 458 ms 0 2.38 s 956 ms
2026-08-15 3.60 s 443 ms 0 2.40 s 948 ms
2026-08-08 3.57 s 425 ms 0 2.38 s 948 ms
2026-08-01 3.48 s 392 ms 0 2.38 s 986 ms
2026-07-25 3.31 s 353 ms 0 2.35 s 1.04 s
2026-07-18 3.10 s 317 ms 0 2.26 s 1.06 s
2026-07-11 3.00 s 289 ms 0 2.25 s 1.09 s
2026-07-04 2.92 s 279 ms 0 2.20 s 1.06 s
2026-06-27 2.85 s 274 ms 0 2.17 s 1.04 s
2026-06-20 2.77 s 265 ms 0 2.12 s 1.02 s
2026-06-13 2.69 s 267 ms 0 2.05 s 988 ms
2026-06-06 2.65 s 262 ms 0 2.02 s 971 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 3.61 MB — — 3.61 MB 3.61 MB
Requests 388 — — 388 388
Third-party Weight 1.36 MB — — 1.36 MB 1.36 MB
Third-party CPU 723 ms — — 723 ms 723 ms
Unused JS 597 kB — — 597 kB 597 kB
Unused CSS 31.2 kB — — 31.2 kB 31.2 kB

By resource type

script 2.09 MB · 126 req
other 870 kB · 156 req
document 311 kB · 7 req
image 203 kB · 90 req
font 119 kB · 4 req
stylesheet 6.8 kB · 3 req
third party 3.61 MB · 386 req

Third parties 15 entities

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

Google Tag Manager 799 kB · 415 ms CPU
Facebook 259 kB · 206 ms CPU
Other Google APIs/SDKs 99.5 kB · 11 ms CPU
LinkedIn Ads 42.8 kB · 21 ms CPU
Sentry 42.4 kB · 10 ms CPU

Page health

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

Main thread work

script evaluation 5.60 s
other 4.04 s
style layout 1.03 s
script parse compile 686 ms
parse HTML 324 ms
garbage collection 275 ms
paint composite render 249 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 1 rule, 5452 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 3 nodes

Accessibility failures 3 of 35 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. 2 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 2 nodes
  • presentation-role-conflict — Elements with `role="none"` or `role="presentation"` have conflicts 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 2 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, 2:00 PM UTC 51 3.98 s 0.068 1.90 s 3.61 MB 3/3 ±28 2,825 91.7s

Embed this score

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