In short
Codeinate says that it measures before and after. So here is the before: Codeinate's own site, with the numbers that are fine and the ones that are not. The site is being rebuilt against a strict budget, and the after will be published on this page when it ships.
Who: Codeinate's own marketing site: four product pages, docs, guides and legal pages (54 routes).
Where it started
- The home page is static HTML served from Amazon S3 through the CloudFront content delivery network over HTTP/2, which is the right shape: no server to patch and fast to deliver.
- Compression is on: the home page is 310,646 bytes uncompressed, 51,985 bytes with gzip and 44,180 bytes with Brotli. A phone receives the Brotli version.
- On a mid-range phone profile with a slow 4G connection and a 4x slower CPU, the main content of the home page painted at 1.71 s in Codeinate's own measurement, inside Google's 2.5 s threshold but above Codeinate's own 2.0 s target on the heaviest pages.
- Lighthouse's simulated mobile run scores the same page lower: it estimated 8.47 s to the largest paint and a performance score of 51 out of 100, because the page ships about 160 KB of compressed JavaScript, 194 KB of third-party scripts and 13 images totalling about 836 KB. The two methods disagree, and the baseline document explains why both are reported.
- Accessibility, best practices and SEO scored 100 in that run. Zero console errors, one H1 per page, canonical links and JSON-LD on every page.
What was done
- Set a page budget for the rebuild: HTML at most 60 KB compressed, JavaScript at most 90 KB, CSS at most 40 KB, first screen at most 300 KB, main content painted within 2.0 s at phone width on slow 4G.
- Rebuilt from one content source per page so that the HTML, the structured data, the plain-text twin for AI assistants and the sitemap cannot disagree.
- Replaced the component library and three font families with one self-hosted font and hand-written styles, and drew the illustrations with code instead of shipping large images.
- Kept every existing URL, the trailing slashes, the structured data types and the analytics events, so search rankings are not put at risk by the rebuild.
What changed
- Not yet. The after numbers go here when the rebuild ships, measured the same way. If a number is worse, it will be here too.
The numbers
| What | Value | How it was measured |
|---|---|---|
| Home page HTML, uncompressed | 310,646 bytes | curl, 2026-11-05 |
| Home page HTML, gzip | 51,985 bytes | curl with Accept-Encoding: gzip, 2026-11-05 |
| Home page HTML, Brotli | 44,180 bytes | curl with Accept-Encoding: br, 2026-11-05 |
| Delivery | S3 + CloudFront, HTTP/2 | response headers, 2026-11-05 |
| Largest Contentful Paint, slow 4G, 4x CPU | 1.71 s | own measurement at 390 px, docs/redesign/00-baseline.md |
| Largest Contentful Paint, Lighthouse simulated mobile | 8.47 s | Lighthouse 13.5 mobile preset, one run |
| Lighthouse performance / accessibility / best practices / SEO | 51 / 100 / 100 / 100 | Lighthouse 13.5 mobile preset, one run |
Source: docs/redesign/00-baseline.md (home row, 2026-11-04) and a curl measurement on 2026-11-05 14:48 UTC



