Test Registry
The 2415 executable tests behind Insights analysis, ranking, and New Internet scoring. Each test has a stable ID, suite, weight, severity, output schema, trace span name, and remediation guidance. No mock scoring is published as real data, and accessibility checks now include the W3C WAI standards/guidelines matrix (including ACT, WCAG 2.2/2.1/2.0, EPUB Accessibility 1.1, ARIA, ATAG, UAAG, and related guidance).
Report and UI Readout Mapping
These are the product report sections used by result pages, exports, MCP resources, and agent-readable summaries.
Measured speed, responsiveness, visual stability, resource weight, and runtime performance evidence.
Automated accessibility signals, WCAG-linked findings, keyboard support, semantics, labels, and inclusive UX evidence.
Search, answer-engine, generative-engine, canonical, indexing, sitemap, and route discovery signals.
Transport security, response headers, public/protected boundaries, privacy disclosures, and policy hygiene.
AI-readable files, OpenAPI, MCP, agent policy, machine-readable docs, and read-only automation access.
JSON-LD, Open Graph, Twitter/X cards, RSS, sitemap, llms, humans, and machine-readable public artifacts.
Modern web standards, route integrity, reproducibility, deterministic grading, and operational resilience.
WCAG compliance, screen reader support, and inclusive design
LLM discoverability, structured data, and machine readability
Modern web standards and code quality
Core Web Vitals, loading speed, and resource optimization
HTTPS, headers, and vulnerability prevention
Search engine optimization and discoverability
JSON-LD, XML feeds, and machine-readable content
Sample of named tests
Open JSON registryMeasures loading performance. LCP should occur within 2.5 seconds of page load.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records critical severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: core-web-vitals, loading, ux.
Measures interactivity. FID should be less than 100 milliseconds.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records critical severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: core-web-vitals, interactivity, ux.
Measures visual stability. CLS should be less than 0.1.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records critical severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: core-web-vitals, visual-stability, ux.
Measures when the first content is painted. Should be under 1.8 seconds.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records serious severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: loading, ux, perceived-performance.
Measures server response time. Should be under 800ms.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records serious severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: server, network, infrastructure.
Measures when the page becomes fully interactive. Should be under 3.8 seconds.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records serious severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: interactivity, ux, javascript.
Sum of blocking time for long tasks. Should be under 200ms.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records serious severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: blocking, javascript, main-thread.
Measures how quickly content is visually displayed. Should be under 3.4 seconds.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records moderate severity and medium impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: visual, perceived-performance.
Identifies resources that block first paint.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records moderate severity and medium impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: css, javascript, critical-path.
Identifies CSS rules that are not used.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records moderate severity and medium impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: css, optimization, bundle-size.
Identifies JavaScript that is not used.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records moderate severity and medium impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: javascript, optimization, bundle-size.
Checks if images are properly optimized.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records moderate severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: images, optimization, format.
Checks for WebP/AVIF usage.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records moderate severity and medium impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: images, format, compression.
Checks if offscreen images use lazy loading.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records moderate severity and medium impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: images, lazy-loading, ux.
Checks if text resources are compressed (gzip/brotli).. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records moderate severity and medium impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: compression, server, network.
Checks if HTTP/2 or HTTP/3 is being used.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records moderate severity and medium impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: protocol, server, network.
Checks if static assets have proper cache headers.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records moderate severity and medium impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: caching, server, optimization.
Checks if preconnect is used for critical third-party origins.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records minor severity and low impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: preload, network, optimization.
Checks if fonts use font-display: swap or optional.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records minor severity and medium impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: fonts, ux, loading.
Checks total JavaScript bundle size.. This automated or measured website-analysis check is reported under Performance and Core Web Vitals, records serious severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: javascript, bundle-size, optimization.
Text must have sufficient contrast ratio (4.5:1 for normal text, 3:1 for large text).. This automated or measured website-analysis check is reported under Accessibility and Inclusion, records critical severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: visual, color, readability.
All images must have alt attributes.. This automated or measured website-analysis check is reported under Accessibility and Inclusion, records critical severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: images, screen-reader, text-alternative.
All buttons must have discernible text.. This automated or measured website-analysis check is reported under Accessibility and Inclusion, records critical severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: buttons, screen-reader, interactive.
All links must have discernible text.. This automated or measured website-analysis check is reported under Accessibility and Inclusion, records critical severity and high impact evidence, and must return a truthful product status with public-safe evidence instead of placeholder pass/fail data; tags: links, screen-reader, navigation.