speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time. Follow us on Mastodon or Bluesky.

Charts Compare Measurement runs Embed a score Open to Work

alprado.com/icons

https://alprado.com/icons

98PERF 93A11Y 96BEST 50SEO ✗AXE –CWV

Ranks Overall #1,486 11ty Emeritus

Data from Sep 29, 2026, 5:53 PM UTC old Measured once a week · 36 runs since Aug 20, 2026

Elsewhere: PageSpeed Insights · Calibre · Treo · CrUX Vis · Tame the Bots · Scoring Calculator · Wayback Machine

The most recent attempt failed (4 in a row). ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404)

Numbers below are from the last successful run, old.

Retries are backing off, so this site is being attempted less often than the rest.

Lab data is measured using Lighthouse, Mobile mode unless otherwise specified. Field data is reported from Chrome UX Report (using p75 measurements).

Stack

WordPress 7.1.2 Built with WordPress 7.1.2
Li Hosted by Self-hosted

Lighthouse Scores LAB Simulated

98
Performance
no change
93
Accessibility
no change
96
Best Practices
no change
50
SEO
no change

Metrics LAB

No field data: the Chrome UX Report is not being collected for this project, so every figure below is from the Lighthouse run.

Metric Lab Simulated
Value Change / range Trend
LCP CWV (estimate) Largest Contentful Paint 1.10 s good — 1.10 s – 1.10 s
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a —
CLS CWV (estimate) Cumulative Layout Shift 0.092 good — 0.092 – 0.092
TBT Total Blocking Time 0 ms good — 0 ms – 0 ms
FCP First Contentful Paint 952 ms good — 952 ms – 952 ms
Speed Index 1.22 s good — 1.22 s – 1.22 s
TTFB Time to First Byte 1.00 s needs work — 1.00 s – 1.00 s

LCP Subparts LAB Unthrottled

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

time to first byte 208 ms
element render delay 40 ms

Page weight

Metric Value Change / range Trend
Page Weight 119 kB — 119 kB – 119 kB
Requests 8 — 8 – 8
Third-party Weight 0 B — 0 B – 0 B
Third-party CPU 0 ms — 0 ms – 0 ms
Unused JS 0 B — 0 B – 0 B
Unused CSS 0 B — 0 B – 0 B

By resource type

Type Transfer Share Size Requests
font 61.9% 73.3 kB 1
document 22% 26.1 kB 2
script 13.8% 16.4 kB 2
image 1.4% 1.7 kB 1
other 0.8% 991 B 2
Total 119 kB 8

Page health

Metric Value Change / range Trend
Main Thread Work 4.55 s — 4.55 s – 4.55 s
Long Tasks 0 — 0 – 0
DOM Elements 27 — 27 – 27
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 12 — 12 – 12
A11y Failures 2 — 2 – 2
A11y Failing Nodes 5 — 5 – 5

Main thread work

Task Time Share Duration Simulated
script evaluation 86% 3.90 s
other 7% 314 ms
garbage collection 5% 207 ms
style layout 2% 82 ms
parse HTML 1% 29 ms
paint composite render 0% 16 ms
script parse compile 0% 3 ms
Total 4.55 s

Axe violations axe-core 4.13.0, full rule set

12 violating nodes across 8 rules, 208 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.

  • serious link-name — Links must have discernible text 4 nodes
    Offending elements
    1. .wp-container-core-column-is-layout-099d2093.wp-block-column.is-layout-flow:nth-child(2) > .wp-block-paragraph:nth-child(4) > a:nth-child(1)
      <a href="https://www.youtube.com/@SoyAlbertoPrado"></a>
    2. .wp-container-core-column-is-layout-099d2093.wp-block-column.is-layout-flow:nth-child(2) > .wp-block-paragraph:nth-child(6) > a:nth-child(1)
      <a href="https://www.youtube.com/@SoyAlbertoPrado"></a>
    3. a[rel="noreferrer noopener"]
      <a href="https://profiles.wordpress.org/alprado/" target="_blank" rel="noreferrer noopener"></a>
    4. .wp-container-core-column-is-layout-099d2093.wp-block-column.is-layout-flow:nth-child(2) > .wp-block-paragraph:nth-child(7) > a:nth-child(1)
      <a href="https://www.youtube.com/@SoyAlbertoPrado"></a>
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 2 nodes
    Offending elements
    1. .wp-site-blocks > header
      <header class="wp-block-template-part">
    2. .wp-site-blocks > footer
      <footer class="wp-block-template-part">
  • moderate landmark-banner-is-top-level — Banner landmark should not be contained in another landmark 1 node
    Offending element
    1. .has-base-background-color
      <header class="wp-block-group has-c..." style="border-top-style:non...">
  • moderate landmark-contentinfo-is-top-level — Contentinfo landmark should not be contained in another landmark 1 node
    Offending element
    1. .wp-elements-2
      <footer class="wp-block-group has-c..." style="margin-top:0;margin-...">
  • moderate landmark-no-duplicate-banner — Document should not have more than one banner landmark 1 node
    Offending element
    1. .wp-site-blocks > header
      <header class="wp-block-template-part">
  • moderate landmark-no-duplicate-contentinfo — Document should not have more than one contentinfo landmark 1 node
    Offending element
    1. .wp-site-blocks > footer
      <footer class="wp-block-template-part">
  • moderate landmark-one-main — Document should have one main landmark 1 node
    Offending element
    1. html
      <html lang="es">
  • moderate region — All page content should be contained by landmarks 1 node
    Offending element
    1. .wp-site-blocks > .has-global-padding.is-layout-constrained.wp-block-group-is-layout-constrained
      <div class="wp-block-group has-global-padding is-layout-constrained wp-block-group-is-layout-constrained">

Accessibility failures 2 of 19 audits

  • link-name — Links do not have a discernible name 4 nodes
  • landmark-one-main — Document does not have a main landmark. 1 node

Best Practices failures 1 of 20 audits

  • errors-in-console — Browser errors were logged to the console 1 item

SEO failures 3 of 9 audits

  • is-crawlable — Page is blocked from indexing 1 item
  • meta-description — Document does not have a meta description
  • http-status-code — Page has unsuccessful HTTP status code

Hygiene

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 1 console error

Measurement log

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchTook Archive
Oct 8, 2026, 2:39 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 13.2s
Oct 7, 2026, 5:27 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 12.8s
Oct 7, 2026, 10:05 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 13.4s
Oct 6, 2026, 6:47 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 15.9s
Sep 29, 2026, 5:53 PM UTC 98 1.10 s 0.092 0 ms 119 kB 1/3 — 2,449 -2% 18.8s Wayback
Sep 26, 2026, 2:10 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 14.7s
Sep 25, 2026, 6:02 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 19.4s
Sep 24, 2026, 1:08 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 13.6s
Sep 23, 2026, 12:11 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 13.9s
Sep 21, 2026, 11:30 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 18.6s
Sep 19, 2026, 8:38 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 14.1s
Sep 18, 2026, 3:27 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 14.2s
Sep 17, 2026, 12:11 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 18.3s
Sep 15, 2026, 11:30 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 14.1s
Sep 14, 2026, 9:40 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 20.1s
Sep 12, 2026, 11:28 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 16.3s
Sep 11, 2026, 3:14 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 13.8s
Sep 10, 2026, 1:00 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 18.8s
Sep 8, 2026, 11:55 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 13.4s
Sep 7, 2026, 10:37 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 13.8s
Sep 6, 2026, 4:48 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 13.1s
Sep 5, 2026, 12:26 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 13.4s
Sep 4, 2026, 10:46 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 19.6s
Sep 3, 2026, 1:04 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 14.5s
Sep 1, 2026, 10:45 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 14.1s
Aug 31, 2026, 9:04 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 14.6s
Aug 27, 2026, 4:08 PM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 13.7s
Aug 26, 2026, 7:45 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 13.8s
Aug 25, 2026, 7:43 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 15.1s
Aug 24, 2026, 6:56 AM UTC ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) 19.5s