speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time.

Charts Measurement runs Embed a score

radioclassique.fr

https://www.radioclassique.fr/

68 75 77 100 ✗AXE ✓CWV

Ranks Overall #10 Important #8

Data from Sep 4, 2026, 11:18 AM UTC old Measured once a day · 1 run since Sep 4, 2026

Test elsewhere: PageSpeed Insights · Calibre · Treo · CrUX Vis

Stack

WP Built with WP Rocket 3.23
Su Hosted by Sucuri

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-08-06 → 2026-09-02).

LCP 2.45 s good
INP 124 ms good
CLS 0.050 good

Lighthouse Scores

68
Performance
no change
75
Accessibility
no change
77
Best Practices
no change
100
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

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

Scripts disabled
As rendered

61.6% of pixels differ — the page changes substantially. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 10.09 s — — 10.09 s 10.09 s
CLS Cumulative Layout Shift 0.004 — — 0.004 0.004
TBT Total Blocking Time 252 ms — — 252 ms 252 ms
FCP First Contentful Paint 2.05 s — — 2.05 s 2.05 s
Speed Index 3.30 s — — 3.30 s 3.30 s
TTFB Time to First Byte 626 ms — — 626 ms 626 ms

LCP Subparts lab observed, unthrottled

The subparts attribute LCP to your server, resource discovery, download, or rendering. Note that the Lab metrics LCP metric shown above is throttled.

element render delay 481 ms
time to first byte 21 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-08-06 → 2026-09-02).

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 2.45 s good 75.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 124 ms good 88.4% good
CLS CWV 0.050 good 99.2% good
FCP 1.45 s good 81.6% good
TTFB 450 ms good 87.2% good

Lab LCP vs Field LCP

Lab 10.09 s
Field p75 2.45 s

The lab LCP is 4.12× the field p75 — real users likely have above-average hardware or network connectivity.

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.36 MB — — 1.36 MB 1.36 MB
Requests 78 — — 78 78
Third-party Weight 872 kB — — 872 kB 872 kB
Third-party CPU 134 ms — — 134 ms 134 ms
Unused JS 320 kB — — 320 kB 320 kB
Unused CSS 14.4 kB — — 14.4 kB 14.4 kB

By resource type

  • script 75.1% 1.02 MB · 42 req
  • image 10.8% 147 kB · 4 req
  • font 6.7% 90.6 kB · 5 req
  • other 3.3% 44.7 kB · 7 req
  • document 2.3% 31.6 kB · 1 req
  • stylesheet 1.8% 24.7 kB · 8 req

Third parties 8 entities

872 kB transferred, 134 ms on the main thread.

Google/Doubleclick Ads script 278 kB · 51 ms CPU
Dailymotion script 232 kB · 2 ms CPU
Didomi script 207 kB · 52 ms CPU
Google Tag Manager script 127 kB · 25 ms CPU
XiTi 23.6 kB · 3 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 2.16 s — — 2.16 s 2.16 s
Long Tasks 8 — — 8 8
DOM Elements 1,129 — — 1,129 1,129
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 93 — — 93 93
A11y Failures 8 — — 8 8
A11y Failing Nodes 11 — — 11 11

Main thread work

script evaluation 813 ms
other 524 ms
script parse compile 294 ms
style layout 258 ms
paint composite render 215 ms
parse HTML 34 ms
garbage collection 24 ms

Axe violations axe-core 4.13.0, full rule set

93 violating nodes across 10 rules, 1061 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.

  • moderate region — All page content should be contained by landmarks 81 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 4 nodes
  • critical aria-allowed-attr — Elements must only use supported ARIA attributes 1 node
  • serious aria-input-field-name — ARIA input fields must have an accessible name 1 node
  • critical aria-required-children — Certain ARIA roles must contain particular children 1 node
  • critical aria-valid-attr-value — ARIA attributes must conform to valid values 1 node
  • critical meta-refresh — Delayed refresh under 20 hours must not be used 1 node
  • moderate meta-viewport — Zooming and scaling must not be disabled 1 node
  • serious nested-interactive — Interactive controls must not be nested 1 node
  • minor presentation-role-conflict — Elements marked as presentational should be consistently ignored 1 node

Accessibility failures 8 of 37 audits

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 4 nodes
  • aria-allowed-attr — `[aria-*]` attributes do not match their roles 1 node
  • aria-input-field-name — ARIA input fields do not have accessible names 1 node
  • aria-required-children — Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children. 1 node
  • aria-valid-attr-value — `[aria-*]` attributes do not have valid values 1 node
  • meta-refresh — The document uses `<meta http-equiv="refresh">` 1 node
  • meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 1 node
  • presentation-role-conflict — Elements with `role="none"` or `role="presentation"` have conflicts 1 node

Hygiene

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchTook
Sep 4, 2026, 11:18 AM UTC 68 10.09 s 0.004 252 ms 1.36 MB 3/3 ±2 1,858 0% 36.7s