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

jcmendez.io

https://jcmendez.io/

75PERF 94A11Y 77BEST 100SEO ✗AXE –CWV

Ranks Overall #1,563 Built Awesome #1,035

Data from Oct 4, 2026, 4:29 AM UTC old Measured once a week · 7 runs since Aug 21, 2026

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

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

Stack

Uses Font AwesomeFont Awesome
Netlify Hosted by Netlify

Lighthouse Scores LAB Simulated

75
Performance
↑ +4 (+5.6%)
94
Accessibility
no change
77
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 5.46 s poor ↓ -518 ms (-8.7%) significant 5.37 s – 5.98 s
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a —
CLS CWV (estimate) Cumulative Layout Shift 0.002 good ↑ +0.002 0 – 0.002
TBT Total Blocking Time 72 ms good ↓ -5 ms (-6.5%) 36 ms – 77 ms
FCP First Contentful Paint 2.78 s needs work ↓ -424 ms (-13.2%) significant 2.75 s – 3.21 s
Speed Index 2.78 s good ↓ -424 ms (-13.2%) significant 2.75 s – 3.21 s
TTFB Time to First Byte 481 ms good ↑ +13 ms (+2.8%) 466 ms – 487 ms

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.

element render delay 156 ms
time to first byte 36 ms

Page weight

Metric Value Change / range Trend
Page Weight 1.72 MB ↑ +23.9 kB (+1.4%) 1.70 MB – 1.72 MB
Requests 36 ↑ +1 (+2.9%) 35 – 36
Third-party Weight 386 kB ↑ +23.8 kB (+6.7%) significant 362 kB – 386 kB
Third-party CPU 89 ms ↑ +10 ms (+12.5%) 65 ms – 89 ms
Unused JS 141 kB ↑ +760 B (+0.5%) 136 kB – 141 kB
Unused CSS 51.2 kB ↓ -50 B (-0.1%) 51.2 kB – 51.3 kB

By resource type

Type Transfer Share Size Requests
image 63.2% 1.09 MB 17
script 21.3% 367 kB 8
font 10% 172 kB 2
stylesheet 3.3% 56.9 kB 3
document 2.2% 38.2 kB 1
other <0.1% 775 B 2
Total 1.72 MB 36

Third parties 6 entities

Entity Transfer Size Main thread Simulated
Google Tag Manager script 295 kB 76 ms
Google Fonts 37.6 kB 0 ms
iconfinder.com 21.8 kB 0 ms
Google Analytics 21.3 kB 9 ms
Cloudflare 10.2 kB 4 ms
All 6 386 kB 89 ms

Page health

Metric Value Change / range Trend
Main Thread Work 1.42 s ↑ +58 ms (+4.2%) 1.14 s – 1.42 s
Long Tasks 4 → no change 4 – 5
DOM Elements 998 → no change 998 – 998
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 14 → no change 14 – 18
A11y Failures 2 → no change 2 – 2
A11y Failing Nodes 13 → no change 13 – 13

Main thread work

Task Time Share Duration Simulated
script evaluation 30% 427 ms
style layout 29% 407 ms
other 25% 353 ms
script parse compile 7% 99 ms
paint composite render 5% 69 ms
parse HTML 5% 69 ms
Total 1.42 s

Axe violations axe-core 4.13.0, full rule set

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

  • moderate heading-order — Heading levels should only increase by one 10 nodes
    Offending elements (5 of 10)
    1. a[href$="experience#mipariente"] > h5
      <h5 class="text-primary font-sans-serif">MiPariente</h5>
    2. .show.active[data-tor-slider-item-id="0"] > .portfolio-item.card.card-has-bg > .card-img-overlay.flex-column.d-flex > .card-footer > .media > .media-body > h6
      <h6 class="my-0 text-white d-block">jcmendez</h6>
    3. .tor-slider-item[data-tor-slider-item-id="1"] > .portfolio-item.card.card-has-bg > .card-img-overlay.flex-column.d-flex > .card-footer > .media > .media-body > h6
      <h6 class="my-0 text-white d-block">jcmendez</h6>
    4. .tor-slider-item[data-tor-slider-item-id="2"] > .portfolio-item.card.card-has-bg > .card-img-overlay.flex-column.d-flex > .card-footer > .media > .media-body > h6
      <h6 class="my-0 text-white d-block">jcmendez</h6>
    5. div[data-tor-slider-item-id="3"] > .portfolio-item.card.card-has-bg > .card-img-overlay.flex-column.d-flex > .card-footer > .media > .media-body > h6
      <h6 class="my-0 text-white d-block">jcmendez</h6>
  • serious link-name — Links must have discernible text 3 nodes
    Offending elements
    1. .me-3.d-inline-block[target="_blank"]:nth-child(1)
      <a href="https://twitter.com/jcmendez_us" target="_blank" class="d-inline-block me-3"> <i class="bi bi-twitter text-primary"></i> </a>
    2. .me-3.d-inline-block[target="_blank"]:nth-child(2)
      <a href="https://linkedin.com/in/jcmendez/" target="_blank" class="d-inline-block me-3"> <i class="bi bi-linkedin text-primary"></i> </a>
    3. .me-3.d-inline-block[target="_blank"]:nth-child(3)
      <a href="sms:+1-954-205-6824?body=Hi JC, I'm contacting you about " target="_blank" class="d-inline-block me-3"> <i class="bi bi-chat-dots-fill text-primary"></i> </a>
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
    Offending element
    1. .navbar
      <nav class="navbar navbar-expand-lg fixed-top bg-white">

Accessibility failures 2 of 23 audits

  • heading-order — Heading elements are not in a sequentially-descending order 10 nodes
  • link-name — Links do not have a discernible name 3 nodes

Best Practices failures 2 of 19 audits

  • third-party-cookies — Uses third-party cookies 7 items
  • 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 h3

Measurement log

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchTook Archive
Oct 4, 2026, 4:29 AM UTC 75 5.46 s 0.002 72 ms 1.72 MB 3/3 ±15 2,502 +1% 36s Wayback
Sep 26, 2026, 10:00 PM UTC 71 5.98 s 0 77 ms 1.70 MB 3/3 ±11 2,482 0% 30s Wayback
Sep 19, 2026, 7:20 PM UTC 75 5.47 s 0.002 66 ms 1.72 MB 3/3 ±12 2,471 -1% 30.8s Wayback
Sep 12, 2026, 6:17 PM UTC 75 5.45 s 0.002 59 ms 1.72 MB 3/3 ±13 2,195 -12% 29.8s Wayback
Sep 5, 2026, 5:57 PM UTC 75 5.47 s 0.002 62 ms 1.72 MB 3/3 ±6 2,379 -4% 30.9s Wayback
Aug 29, 2026, 5:00 PM UTC 76 5.37 s 0.002 36 ms 1.71 MB 3/3 ±14 3,016 +21% 29.7s Wayback
Aug 21, 2026, 1:17 AM UTC 75 5.43 s 0.002 58 ms 1.71 MB 3/3 ±16 2,477 0% 36.3s Wayback

Embed this score

Use this web component to show jcmendez.io's scores on any website, updated whenever this instance re-measures. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://jcmendez.io/"></speedlify2-score>