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

foxdog.io

https://www.foxdog.io/

72 80 96 73 AXE CWV

Ranks Overall #1,443 Built Awesome #1,084

Data from Sep 14, 2026, 9:36 PM UTC old Measured once a week · 12 runs since Aug 21, 2026

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

This URL redirects to https://www.foxdog.io/lander.

The site’s front door pointing at the page it serves there — a locale or CMS landing path, not a move. The origin is still the address of the site, so history stays under it rather than forking to a path that depends on where the measurement ran. Lighthouse follows the redirect, so the numbers below describe the page actually served; the only cost is an extra hop on each run.

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

Stack

Uses ReactReact

Lighthouse Scores LAB Simulated

72
Performance
↑ +1 (+1.4%)
80
Accessibility
no change
96
Best Practices
no change
73
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 3.65 s needs work ↓ -44 ms (-1.2%) 3.65 s – 3.69 s
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a
CLS CWV (estimate) Cumulative Layout Shift 0.282 poor → no change 0.282 – 0.282
TBT Total Blocking Time 200 ms good ↓ -8 ms (-3.8%) 190 ms – 208 ms
FCP First Contentful Paint 1.69 s good ↓ -37 ms (-2.1%) 1.69 s – 1.73 s
Speed Index 1.69 s good ↓ -37 ms (-2.1%) 1.69 s – 1.73 s
TTFB Time to First Byte 612 ms good ↓ -7 ms (-1.1%) 612 ms – 622 ms

Page weight

Metric Value Change / range Trend
Page Weight 228 kB ↓ -72 B 228 kB – 228 kB
Requests 17 → no change 17 – 17
Third-party Weight 0 B → no change 0 B – 0 B
Third-party CPU 0 ms → no change 0 ms – 0 ms
Unused JS 120 kB → no change 120 kB – 120 kB
Unused CSS 0 B → no change 0 B – 0 B

By resource type

Type Transfer Share Size Requests
script 92.1% 210 kB 2
other 5.1% 11.7 kB 12
stylesheet 2% 4.6 kB 1
document 0.7% 1.7 kB 2
Total 228 kB 17

Page health

Metric Value Change / range Trend
Main Thread Work 804 ms ↑ +48 ms (+6.3%) 756 ms – 837 ms
Long Tasks 3 → no change 3 – 4
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 13 → no change 13 – 13
A11y Failures 3 → no change 3 – 3
A11y Failing Nodes 3 → no change 3 – 3

Main thread work

Task Time Share Duration Simulated
script evaluation 53% 428 ms
other 28% 227 ms
script parse compile 10% 79 ms
garbage collection 5% 42 ms
style layout 2% 18 ms
paint composite render 1% 6 ms
parse HTML 1% 5 ms
Total 804 ms

Axe violations axe-core 4.13.0, full rule set

13 violating nodes across 5 rules, 207 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 9 nodes
  • serious document-title — Documents must have <title> element to aid in navigation 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate meta-viewport — Zooming and scaling must not be disabled 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 3 of 16 audits

  • document-title — Document doesn't have a `<title>` element 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
  • 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 2 items

SEO failures 3 of 8 audits

  • document-title — Document doesn't have a `<title>` element 1 item
  • meta-description — Document does not have a meta description
  • robots-txt — robots.txt is not valid 2 items

Hygiene

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache http/1.1 2 console errors

Measurement log

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchTook Archive
Sep 14, 2026, 9:36 PM UTC 72 3.65 s 0.282 200 ms 228 kB 3/3 ±4 2,324 -6% 281.7s Wayback
Sep 7, 2026, 7:04 PM UTC 71 3.69 s 0.282 208 ms 228 kB 3/3 ±3 2,491 0% 282.1s Wayback
Aug 31, 2026, 6:07 PM UTC 72 3.69 s 0.282 190 ms 228 kB 3/3 ±3 2,486 0% 281.8s Wayback
Aug 26, 2026, 10:35 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 137.8s
Aug 25, 2026, 9:43 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.1s
Aug 24, 2026, 9:06 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.6s
Aug 23, 2026, 8:37 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.6s
Aug 22, 2026, 4:23 PM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.1s
Aug 22, 2026, 7:33 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.3s
Aug 22, 2026, 1:12 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.6s
Aug 21, 2026, 6:35 PM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.2s
Aug 21, 2026, 11:44 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.2s

Embed this score

Use this web component to show foxdog.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://www.foxdog.io/"></speedlify2-score>