A roofing website rebuilt around one goal: the booked estimate.

The baseline models the roofing site we audit most often: a purchased theme carrying about 4MB of scripts and sliders, a 7.2-second load on mobile data, the phone number hidden in a footer, one generic "services" page for every kind of work, and no pages for the cities the company actually serves. It looks busy and performs like a brochure left in a drawer.

We rebuilt it as we would for a paying client. A tap-to-call header and an estimate request on the first screen. Separate pages for repair, replacement, and storm work, plus a service-area structure Google can read. Insurance and financing questions answered in plain English, and a project gallery that loads fast instead of impressing slowly.

Under the hood: hand-coded pages, structured data describing the business honestly, and a performance budget enforced in code — the mobile load dropped from 7.2 seconds to 0.8.

This is the exact playbook we apply to real roofing sites: conversion path first, local-search structure second, speed as the multiplier on both. The numbers below are measured on this build — and they're the same numbers we'd measure on yours, before and after.