GaboAuditmyweb — Marketing Site and the Audit Engine Behind It

GaboAuditmyweb — Marketing Site and the Audit Engine Behind It An architecture diagram generated by Archify. Google APIs · PageSpeed + CrUX · audit-engine — the tooling that produces what the site sells Google APIs PageSpeed + CrUX Recorded Payloads · network cut at fetch · audit-engine — the tooling that produces what the site sells Recorded Payloads network cut at fetch audit-engine CLI · audit · seo · batch · audit-engine — the tooling that produces what the site sells audit-engine CLI audit · seo · batch Speed Collectors · lab + field · audit-engine — the tooling that produces what the site sells Speed Collectors lab + field Schema Validation · before anything renders · audit-engine — the tooling that produces what the site sells Schema Validation before anything renders Report Generator · template from tipo · audit-engine — the tooling that produces what the site sells Report Generator template from tipo Client Report · one HTML file · audit-engine — the tooling that produces what the site sells Client Report one HTML file SEO Crawl · 22 checks, no API key · audit-engine — the tooling that produces what the site sells SEO Crawl 22 checks, no API key Three Pages · no framework · marketing site — no framework, zero external requests Three Pages no framework build.js · minify, zero deps · marketing site — no framework, zero external requests build.js minify, zero deps build --check · same text, same ids · marketing site — no framework, zero external requests build --check same text, same ids Vercel · dist/ · hashed fonts · marketing site — no framework, zero external requests Vercel dist/ · hashed fonts lab + field metrics tests, real code paths audit.js seo.js raw payload 22 verdicts tipo picks the template rendered source is what you edit minified dist/ refuses if text moved audit-engine — the tooling that produces what the site sells marketing site — no framework, zero external requests Legend Frontend Backend Cloud Security External

A silent minifier bug looks like a working site

  • • build --check compares source against dist/ before the deploy is allowed
  • • Text, per-gap whitespace, data-i18n keys, data-* hooks, ids and hrefs
  • • Any one of them moves and the build refuses — that is the Vercel build command

Two tracks, sold separately

  • • Speed guarantees PageSpeed 85+; SEO guarantees every failed check green
  • • Running both inside one month would force cutting one short
  • • Then neither guarantee is defensible, so there is no bundle

No dependencies on either side

  • • 129 tests on node:test with nothing to install
  • • The network is intercepted at fetch, so collectors run real code paths on recorded payloads
  • • The site's pitch is page speed, so shipping a bundle would undercut the product