Xtreme Auto Detailing

Xtreme Auto Detailing does ceramic coating, paint correction and full details out of a shop in Blue Springs, and most of that work is hard to explain in a sentence. I hand-built a 28-page site that shows it instead: before-and-after sliders, a gallery of Aaron's own photos, and an interactive page that shows what a ceramic coating does when it rains. Under Google's throttled mobile test the homepage scores 91, against a median of 55 for Kansas City small-business sites.

The challenge

Detailing gets sold on trust and on photos. From a price list, most people can't tell a wash from a paint correction, and ceramic coating is the hardest of all to sell because you don't see what it does until the next storm. Aaron needed a site that made those differences obvious, let a customer book or pay without playing phone tag, and showed up when someone near the shop searched for a detailer.

What I built

A static site generated from a custom Python build: a page for every service, a page for each of the five towns around the shop, a membership page, and a filterable gallery of real cars, boats and trucks Aaron has worked on. Every photo goes through an image pipeline that writes AVIF and WebP at several widths, so a phone only downloads the size it needs. The page I'm proudest of is How Ceramic Works, an animated explainer that walks one drop of water across bare paint and then coated paint, and ends on a half-coated hood you can tap to make it rain on. Booking goes straight into the Square calendar Aaron already used, customers can pay an invoice from the site, the quote form lands in his inbox, and his real Google reviews sit on the homepage.

The results

Under Google's throttled mobile test on 2026-10-11, the homepage scored 91 for performance, 100 for accessibility, 100 for SEO and 100 for best practices, with a 3.4-second Largest Contentful Paint, against a median mobile performance of 55 across the 105 Kansas City small-business sites I surveyed. Every page carries structured data, the site runs behind a strict content security policy, and a regression gate checks the build before every deploy. Each check in that gate has been proven able to fail, by planting the exact mistake it looks for and making sure it catches it.

Measured under Google's throttled mobile (Lighthouse) test on 2026-10-11. *Medians from my survey of 105 KC small-business websites. No CrUX real-user field data is available for this site, so every figure here is a lab measurement.

The stack, for the curious

A custom Python and Jinja static-site generator with an AVIF and WebP image pipeline and self-hosted fonts. No framework; the one animation library (GSAP) loads only on the ceramic explainer. Deployed on Cloudflare Pages with an edge function that keeps preview builds out of search, sends www to the main domain, and logs which AI crawlers read the site. A strict content-security-policy and full security headers, llms.txt plus a markdown copy of every page, and a small JSON layer so AI assistants can read the services and how to book. Analytics are cookieless, through LiveDash.

Visit xadkc.com ↗