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 and Bluesky.
Last updated ago. 1,763 measurements in the last week.

Charts Compare Measurement runs Embed a score Open to Work

womenofjamstack.com

https://womenofjamstack.com/

61PERF 90A11Y 96BEST 100SEO ✗AXE –CWV

Ranks Overall #1,508 11ty Emeritus

Data from Nov 19, 2026, 10:16 PM UTC old Measured once a month · 7 runs since Aug 21, 2026

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

The measuring machine was faster than most in this project.

Lighthouse benchmark index was 4,076, 64% faster than this project's median of 2,493. CPU-bound metrics — TBT, TTI, main thread work — are affected by this and may have moved without the site changing at all.

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.5 Built with WordPress 7.1.5
Self-hosted · Apache Hosted by Self-hosted
Rendered On request, then cached Page cache hit

Lighthouse Scores LAB Simulated

61
Performance
↑ +5 (+8.9%)
90
Accessibility
no change
96
Best Practices
no change
100
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 4.12 s poor ↓ -240 ms (-5.5%) 4.12 s – 5.67 s
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a —
CLS CWV (estimate) Cumulative Layout Shift 1.597 poor → no change 0 – 1.622
TBT Total Blocking Time 0 ms good ↓ -11 ms (-100%) 0 ms – 59 ms
FCP First Contentful Paint 1.70 s good ↓ -959 ms (-36.1%) significant 1.70 s – 2.87 s
Speed Index 1.74 s good ↓ -916 ms (-34.5%) 1.74 s – 5.20 s
TTFB Time to First Byte 633 ms good ↓ -51 ms (-7.5%) 632 ms – 731 ms
RTT Round-trip time to the server — field only, and ungraded: Google publishes no threshold for it n/a —

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.

resource load delay 205 ms
element render delay 43 ms
resource load duration 37 ms
time to first byte 27 ms

Page weight

Metric Value Change / range Trend
Page Weight 846 kB ↓ -9 B 845 kB – 846 kB
Requests 50 → no change 50 – 50
Third-party Weight 33.5 kB ↓ -2 B 33.5 kB – 33.8 kB
Third-party CPU 0 ms → no change 0 ms – 0 ms
Unused JS 0 B → no change 0 B – 0 B
Unused CSS 15.1 kB ↓ -69 B (-0.5%) 15.1 kB – 15.2 kB

By resource type

Type Transfer Share Size Requests
image 73.6% 622 kB 7
script 10.2% 86.0 kB 16
font 7.1% 60.1 kB 4
document 4.1% 34.4 kB 1
stylesheet 3.8% 32.5 kB 20
other 1.3% 10.8 kB 2
Total 846 kB 50

Third parties 2 entities

Entity Transfer Size Main thread Simulated
archive.org image 17.0 kB 0 ms
Google Fonts font 16.4 kB 0 ms
Total 33.5 kB 0 ms

Page health

Metric Value Change / range Trend
Main Thread Work 654 ms ↓ -381 ms (-36.8%) significant 654 ms – 1.15 s
Long Tasks 0 ↓ -3 (-100%) significant 0 – 5
DOM Elements 676 → no change 671 – 677
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 14 → no change 14 – 14
A11y Failures 3 → no change 3 – 3
A11y Failing Nodes 14 → no change 14 – 14

Main thread work

Task Time Share Duration Simulated
style layout 32% 210 ms
other 27% 174 ms
script evaluation 26% 173 ms
parse HTML 7% 44 ms
paint composite render 4% 29 ms
script parse compile 3% 19 ms
garbage collection 1% 5 ms
Total 654 ms

Axe violations axe-core 4.14.0, full rule set

14 violating nodes across 3 rules, 1105 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 9 nodes
    Offending elements (5 of 9)
    1. .sowb-button > span
      <span> Contact Us </span>
    2. p[data-start="470"] > a
      <a href="https://womenofjamstack.com/women-of-influence/">And in many families, that quiet strength often comes from older women.</a>
    3. p[data-start="2423"] > a
      <a href="https://goo.gl/maps/YzVofdKf151LV4BSA">garage door repair</a>
    4. p[data-start="6484"] > a
      <a href="https://goo.gl/maps/YzVofdKf151LV4BSA">garage door repair Wellesley MA</a>
    5. p:nth-child(9) > a
      <a href="https://womenofjamstack.com/empowered-and-handy-skilled-women-take-on-home-improvement-projects-with-confidence/">demonstrating their skills and pushing the boundaries of creativity</a>
  • moderate heading-order — Heading levels should only increase by one 3 nodes
    Offending elements
    1. .sow-features-feature.sow-icon-container-position-top:nth-child(1) > .textwidget > h5
      <h5 class="sow-features-feature-title"> Graphic Design </h5>
    2. .slick-current > .sow-carousel-item-title
      <h3 class="sow-carousel-item-title">
    3. .panel-widget-style-for-11-5-0-0 > .so-widget-sow-editor.so-widget-sow-editor-base > .siteorigin-widget-tinymce.textwidget > h3
      <h3><img fetchpriority="high" decoding="async" src="https://web.archive.org/web/20220703033344im_/https://womenofjamstack.com/img/j1AzQcXnYx-300.webp" alt="Salma Alam-Naylor" width="900" height="900"…
  • serious frame-title — Frames must have an accessible name 2 nodes
    Offending elements
    1. p[data-start="2599"][data-end="2679"]:nth-child(23) > iframe
      <iframe loading="lazy" style="border: 0;" src="https://www.google.c..." width="600" height="450" allowfullscreen="allowfullscreen">
    2. center > iframe
      <iframe loading="lazy" style="border: 0;" src="https://www.google.c..." width="600" height="450" allowfullscreen="allowfullscreen">

Accessibility failures 3 of 24 audits

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 9 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 3 nodes
  • frame-title — `<frame>` or `<iframe>` elements do not have a title 2 nodes

Best Practices failures 1 of 20 audits

  • inspector-issues — Issues were logged in the `Issues` panel in Chrome Devtools 1 item

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 RunsSpreadBenchLighthouseTook Archive
Nov 19, 2026, 10:16 PM UTC 61 4.12 s 1.597 0 ms 846 kB 3/3 ±2 4,076 +63% 13.6.0 41.5s Wayback
Oct 20, 2026, 10:08 PM UTC 56 4.36 s 1.597 11 ms 846 kB 3/3 ±3 2,433 -2% 13.4.1 44.2s Wayback
Sep 20, 2026, 8:52 PM UTC 55 4.44 s 1.622 16 ms 845 kB 3/3 ±25 2,487 0% 13.4.1 48.2s Wayback
Sep 13, 2026, 8:33 PM UTC 56 4.39 s 0.854 42 ms 846 kB 3/3 ±2 2,532 +2% 13.4.1 36.3s Wayback
Sep 6, 2026, 7:01 PM UTC 71 5.67 s 0 59 ms 845 kB 3/3 ±20 2,504 0% 13.4.1 40.9s Wayback
Aug 30, 2026, 6:06 PM UTC 56 4.38 s 1.622 17 ms 845 kB 3/3 ±15 2,462 -1% 13.4.1 41.7s Wayback
Aug 21, 2026, 10:39 AM UTC 58 4.60 s 1.596 19 ms 845 kB 3/3 ±22 2,320 -7% 13.4.1 59.6s Wayback