Primary DatasetSample: 100 live production domains (91 valid)September 2026

100 Websites Audited: What Real-World Data Reveals About Speed, Schema, and AI Bots

An empirical forensic benchmark of 100 live websites measuring server latency, mobile LCP bottlenecks, Knowledge Graph adoption, and llms.txt AI discovery readiness.

76.9%Mobile LCP Failure Rate70 of 91 valid domains exceeded Google 2.5s mobile LCP benchmark
1,034msAverage Server TTFBAverage Time to First Byte recorded across all live production domains
28.6%Missing Schema.org Rate26 of 91 sites lacked any JSON-LD structured data graph
96% vs 27%AI Readiness DisparitySaaS / DevTools vs Agencies with active llms.txt endpoints

Executive Summary & Empirical Findings

We conducted an automated forensic audit across 100 live production domains across four distinct industries: SaaS and Developer Tools, E-Commerce and DTC Brands, Indie Hackers, and Digital Agencies. Our data shows a striking divergence: while 96% of developer tools publish llms.txt files, 76.9% of websites fail Google mobile Largest Contentful Paint threshold, and 28.6% lack structured data entirely.

Core Technical Conclusions:

  • 76.9% of audited production websites failed Google mobile Largest Contentful Paint target (LCP <= 2.5s), with an overall cross-sector average of 4.58 seconds.
  • E-Commerce brands exhibited the heaviest payloads (849.5KB average HTML) and slowest load times (6.51s average LCP), driven by uncompressed assets and marketing trackers.
  • Indie Hackers delivered the leanest HTML payloads (141.9KB average) and fastest load times (2.86s average LCP), but suffered the lowest Schema.org adoption at just 59.1%.
  • A striking AI discovery divide emerged: 96.0% of SaaS and Developer Tools have published llms.txt files, compared to only 27.3% of Digital Agencies and 36.4% of Indie Hackers.
  • 3.3% of audited production domains still serve uncompressed raw HTML over the wire, completely missing Gzip and Brotli compression.

Testing Methodology & Reproducibility

All 100 domains were queried concurrently using automated HTTP/2 and HTTP/1.1 telemetry probes following W3C Navigation Timing standards. DOM structures, JSON-LD @graph blocks, script tags, image formats, and llms.txt endpoints were extracted and evaluated under standardized browser emulation profiles.

Want custom performance telemetry for your site?

Run our in-browser diagnostic tools or test your site with VitalsSniper PRO.

Run Free Speed Audit