41 pages made crawlable, readable, and three times lighter
A content-heavy site where most pages could not be found, half the images were 4 MB camera uploads, and contrast failures made the service pages hard to read. The same fixes lifted search visibility, accessibility and speed together.
Page weight
4.8 MB1.2 MB
−75%
Accessibility issues
680
−68
Pages in the sitemap
1241
+29
Lighthouse SEO
42100
+58 pts
Before and after
What was slowing it down → what changed
Before
29 service pages were unreachable from the navigation and missing from the sitemap, so search engines indexed a fraction of the site.
After
Generated a complete sitemap from the route list, linked every service page from an index page, and fixed the crawl-blocking robots rule.
Before
Every page had the same title tag and no canonical URL, so pages competed with each other in search results.
After
Per-page titles, descriptions and canonicals, generated from the same content that renders the page.
Before
Photography was uploaded straight from a camera: 4 MB each, no width or height, no responsive sizes.
After
Compressed to AVIF/WebP at three widths with explicit dimensions. Images fell from 4.1 MB to 780 KB and layout shift disappeared.
Before
68 accessibility failures across the site: low-contrast body text, unlabelled form fields, skipped heading levels.
After
Raised contrast to WCAG AA, labelled every input, and corrected the heading order. Automated checks now return zero issues.
Before
Contact and location information was plain text, invisible to search engines as structured data.
After
Added LocalBusiness and Breadcrumb structured data validated against Google's requirements.
The numbers
Lighthouse, same local production build, median of five runs
Performance
5496
Accessibility
61100
Best practices
79100
SEO
42100
| Metric | Before | After | Good threshold |
|---|---|---|---|
| LCPCWV | 4.60 s | 2.10 s | ≤ 2.5 s |
| CLSCWV | 0.24 | 0.02 | ≤ 0.10 |
| INP (lab: TBT)CWV | 620 ms | 140 ms | ≤ 200 ms |
| Page size | 4.80 MB | 1.20 MB | ≤ 2 MB |
| Images | 4.10 MB | 780 KB | ≤ 1 MB |
| Requests | 96 | 38 | ≤ 80 |
| Accessibility issues | 68 | 0 | 0 |
| Indexable pages | 12 | 41 | All |
Lab data, not a promise: field results depend on your visitors' devices and networks. The thresholds above are the 75th-percentile targets Google uses.
The playbook
The same order of work applies to most sites
Start with what search engines can see
A sitemap that lists a page is not the same as a page that is linked. Crawl your own site like a visitor: if you cannot click to it, neither can Google.
One page, one title, one canonical
Duplicate titles split relevance. Generate metadata from the content the page already has instead of maintaining a second list.
Treat images as content that has a budget
Three widths cover phones, tablets and desktop. Explicit dimensions prevent layout shift; compression is not an optional polish step.
Accessibility fixes are SEO fixes
Labels, heading order and readable contrast help screen readers, keyboard users and crawlers that parse the same markup.
Add structured data last
Schema describes content that already exists. Build the content and metadata first, then describe it with validated JSON-LD.
What it changed
- The sitemap grew from 12 to 41 indexable pages, all reachable by link.
- Automated accessibility checks went from 68 issues to zero.
- Page weight fell 75%, and the slowest heading image is now under one second on mobile.
Check it yourself
The tools and definitions behind every number above
- PageSpeed InsightsRun a test on any public URL
- Core Web Vitals: what each metric meansLCP, INP and CLS explained, with the thresholds used on this page.
- Largest Contentful Paint (LCP)Why the hero image decides when the page feels loaded.
- Interaction to Next Paint (INP)Responsiveness, and the metric that replaced FID in 2024.
- Cumulative Layout Shift (CLS)Visual stability, and how to stop content jumping.
- Chrome UX Report (CrUX)Real-user field data, collected over a rolling 28-day window.