Griffin Renovation website case study

The project

This is a client project Vient built twice. The brief was a small business site that had to load fast, read well on a phone, and carry clean structured data so it could rank in local search. The first version shipped on the LandingSite AI builder for a quick launch. A few months later it got rebuilt from scratch in code, mostly to take back control of the SEO and drop a monthly hosting fee. The interesting part of this project is that migration, not the storefront it points to.

The build

The rebuild is plain HTML, Tailwind CSS v4, and vanilla JavaScript. No framework, no build step, no npm. Three pages, two JS files, one CSS file.

Key technical decisions:

• Tailwind v4 Browser CDN for styling without a build pipeline
• JavaScript component injection for a shared header and footer across pages without a static site generator, plus a <noscript> nav fallback so crawlers still see the links
• EmailJS for contact form submissions without a backend, with a phone-number fallback if a send fails
• Cloudflare Image Delivery for automatic image optimization and WebP conversion
• JSON-LD structured data with the HomeAndConstructionBusiness schema type, area served, service catalog, and ratings, so local search has a machine-readable version of the business
• Netlify for free static hosting with security headers and aggressive caching

Results

The migration dropped a monthly hosting fee and gave the site the SEO controls the AI builder didn’t expose. The structured data, canonical and Open Graph tags, and a hand-built sitemap give Google what it needs, and the whole thing runs on a free static deploy. The build itself was the interesting problem here.