03The Limitations
Where the current site holds SecureHeat back
Grouped by theme and tagged by severity. Every point below is drawn from the live site as reviewed on 10 July 2026, with the supporting evidence noted on each card.
Design, Brand & First Impressions
High A dated, monotone visual language
- The same translucent-yellow box is reused for the hero, the plan callouts and the feature cards — the page has one idea repeated, not a visual hierarchy.
- Pale yellow on white with light-grey text reads as low-energy and cheap; it fights the "trusted, professional, in-your-home" message.
- Buttons appear in grey, black, yellow and blue with no consistent primary-action colour, so nothing feels like the thing to click.
Evidence: Homepage + cover page; Hello-Elementor theme with default styling, Elementor 3.23.
High Generic stock photography
- Every image is stock — a family on a sofa, a parent and child at a tap. None of it is SecureHeat.
- For a local trade, authenticity is the marketing: real engineers, branded vans, real Berkshire homes and completed jobs build far more trust than stock.
- Competitors using real team photography instantly feel more legitimate by comparison.
Evidence: All homepage/cover imagery is generic library photography.
Mobile Experience
Critical The first mobile screen is nearly all chrome
- On load, the cookie banner sits on top of and hides the logo — the first thing a visitor should see is missing.
- After consent, the header (logo + two full-width stacked buttons + nav bar) eats roughly 60% of the first screen.
- The hero headline and the primary "View Plans" button are pushed below the fold — the main message isn't visible without scrolling.
- A floating shopping-basket icon overlaps the hero text, which is confusing for a service business.
Why it matters: The majority of "emergency boiler" and "plumber near me" searches happen on mobile — this is the screen most first-time visitors see.
Conversion & Lead Generation
High Too many competing calls to action
- The homepage alone offers "Call an Engineer", "Book a Boiler Service", "View Plans", "Get a Quote", "Speak to SecureHeat" and "Get Started" — six different asks.
- With no visual priority, the visitor has to decide instead of being led. Choice overload lowers conversion.
- Recommendation: one dominant primary action (Get Cover / Get a Quote) plus a persistent click-to-call for emergencies.
Evidence: Homepage header + body CTAs, cover page CTAs.
Medium The best asset is buried & slightly muddled
- The four-tier table is good, but you scroll through two text blocks and a landlord box before reaching it.
- Tier naming is inconsistent — "Boiler Plan, Bronze, Silver, Gold" mixes metaphors; the entry tier breaks the metal ladder.
- "Prices may vary based on house size and boiler type" undercuts the headline "from" prices — a postcode/property quote step would resolve this cleanly.
- Cards sit on a busy splashing-water photo that reduces legibility.
Evidence: /cover/ — Boiler Plan £9.50 · Bronze £14 · Silver £22 (Popular) · Gold £39 per month.
SEO & Local Search
Critical No local-business structured data
- The homepage ships only generic WebSite / WebPage / Article schema — there's no LocalBusiness / HVACBusiness / Plumber markup.
- That's the single most important signal for ranking in the local "map pack" and rich results for a trade business.
- No Service, FAQPage or Review schema either — all quick wins that the current setup leaves on the table.
Evidence: Single JSON-LD block; only ImageObject/WebSite/WebPage/Person/Article types present.
High The blog died in 2022
- Just seven blog posts exist, and the post sitemap's last-modified date is 14 December 2022 — nothing published in ~3.5 years.
- Fresh, helpful content ("boiler making noise?", "landlord gas safety certificate", "should I get a heat pump?") is how local trades capture search demand.
- A dormant blog also signals staleness to both users and Google.
Evidence: post-sitemap.xml lastmod 2022-12-14; 7 posts total.
High No service-area page system
- Only a couple of thin local pages exist (Wokingham, Woodley). There's no structured set of location pages for the towns SecureHeat covers.
- Dedicated, genuinely useful pages for Reading, Bracknell, Twyford, Crowthorne, Winnersh, etc. are the proven way to rank for "boiler repair [town]".
Evidence: page-sitemap.xml — only /boiler-repair-wokingham/, /gas-engineer-wokingham/, /woodley-berkshire/.
Medium Orphan & duplicate pages clutter the site
- The sitemap exposes test/leftover pages: home-2, home-3, seo-template, landing-page, cover-landing, comingsoon, comingsoongold, book-2, cal.
- These create thin/duplicate content, dilute crawl focus and look unprofessional if found.
- The rebuild is the moment to prune, consolidate and 301-redirect everything to a clean structure.
Evidence: page-sitemap.xml (39 URLs, several clearly orphaned).
Performance & Technical Health
~1.3s
Server time-to-first-byte (should be under ~0.5s)
66+
CSS/JS files on the homepage (34 scripts, 32 stylesheets)
off
Full-page caching disabled (Cache-Control: no-store)
20
Separate Elementor CSS files loading per page
High Caching is switched off & the server is slow
- Response headers send Cache-Control: no-store, no-cache with X-Cache: MISS — pages are rebuilt from scratch on every visit.
- Measured TTFB ranged 1.0–1.6s across repeat requests; that's dead time before anything renders.
- Fixing this (full-page cache + a CDN like Cloudflare) is often the single biggest speed win and is low-effort.
Evidence: Live response headers; 3× curl timing runs.
High Page-builder & plugin bloat
- Elementor + Elementor Pro load 20 separate stylesheets; legacy jQuery is still present; only 7 of 34 scripts are deferred.
- A leftover salient-core plugin (from a previous theme) loads 7 files of pure dead weight on every page.
- Heavy builders are convenient to edit but expensive to load — a lean block theme or a headless build removes most of this overhead.
Evidence: Homepage asset inventory; active-plugin fingerprints in page source.
Accessibility
High Low colour contrast throughout
- Grey body text on white and on yellow frequently falls short of WCAG AA contrast; the footer's grey compliance text on black is close to unreadable.
- Placing text over busy photos (hero, plan cards) compounds the problem.
- Beyond compliance, stronger contrast simply makes the site look more confident and premium.
Standard: WCAG 2.2 AA — 4.5:1 for normal text.
Medium Images that search engines & screen readers can't see
- Most visuals are Elementor CSS background images, not real <img> tags — so they carry no alt text and aren't indexed by Google Images.
- The handful of real image tags are only partly alt-tagged.
- The rebuild should use proper, optimised, alt-described images (WebP) as content, not decoration.
Evidence: Only ~5 <img> tags on the homepage; most media is CSS-backgrounds.