Company website

What I took on

In September the front end of the company website became mine. It is a Next.js site. The service behind its forms, which carries a lead into NetSuite, belongs to the company’s architect, and it is not part of my work.

How a change ships

Every change is its own branch and a pull request to the development site. It has to pass type checks, lint, tests and a clean production build, the architect reviews it, and marketing signs it off on a preview link before it is promoted. Nobody has to read a diff to approve a page.

Pages

Service pages went out in waves, following an outside SEO agency’s plan: heating and cooling, plumbing, insulation, commercial, and blog posts. Each wave carried its metadata, schema and internal links, and a pass to take out claims that were not true, such as warranty wording and old prices.

Landing pages

A page for a utility’s income qualified programme, with its own lead source so an order shows where it came from, and Google Ads pages for heating repair and heating replacement. The ad pages follow one plan: the trust line and both calls to action above the fold, then reviews, how it works, guarantees and financing. The calls to action open the scheduler on the page instead of sending people away.

Speed

Images on the key pages are under 200 KB with their own mobile versions, and the tag manager loads after the page has finished, with ad conversions checked afterwards. The homepage video plays on the page and downloads nothing until someone presses play.

What it includes

1. Service pages in waves: heating, cooling, plumbing, insulation, commercial
2. Landing pages for a utility programme and for Google Ads
3. Schema, internal links and metadata fixed site wide
4. Images under 200 KB, tag manager loaded after the page
5. Reviews card, on page video and check-in widget on the homepage