Performance-First Website Stack Choices for UK SMEs

Your website's speed isn't determined by the hosting plan you pick last minute. It's baked into the stack decisions you make at the start: rendering model, asset strategy, image formats, script budget, and server architecture. Get those right and everything else is fine-tuning. Get them wrong and no amount of caching will save you.

We've built hand-coded sites across Wakefield and West Yorkshire that consistently hit LCP under 1.5 seconds. The reason isn't magic — it's deliberate technical choices made before writing the first line of code. Here's what actually moves the needle.

Rendering model: server-side wins for most business sites

Client-side rendering (React SPAs, for example) sends an empty HTML shell and builds the page in the browser. That means users see nothing until JavaScript finishes loading and executing. For a marketing site or service business, that delay is pointless. Nobody needs a single-page app to read your "About" page.

Server-side rendering sends complete HTML to the browser. Content appears immediately, before JavaScript even loads. For brochure sites, service pages, and portfolios, this is the fastest option. Our builds use server-side PHP rendering — the HTML arrives ready to display.

Asset strategy: every kilobyte is a choice

A typical WordPress theme loads Bootstrap (150KB), jQuery (85KB), a slider library (90KB), and the theme's own framework (200KB+). That's over 500KB of JavaScript before your content loads. Most of that code is unused on any given page.

Performance-first means zero framework overhead. Write only the CSS and JavaScript the page actually needs. Our median total JavaScript payload is under 50KB — roughly 10% of a typical page builder site.

The same discipline applies to CSS. We write component-scoped styles compiled through Tailwind's purge process. The shipped CSS contains only the classes the page uses. No 300KB stylesheet loaded on every page "just in case."

Image discipline: the biggest LCP lever

Images are typically the largest asset on any page and the primary driver of LCP. Getting images right means:

• •Modern formats: WebP as baseline, AVIF where browser support allows. Both are 25–50% smaller than JPEG at equivalent quality.
• •Explicit dimensions: every <img> tag carries width and height attributes. This prevents layout shift (CLS) and lets the browser reserve space before the image loads.
• •Hero preloading: the LCP image gets a <link rel="preload"> in the document head, so the browser fetches it before parsing the rest of the page.
• •Lazy loading everything else: below-the-fold images use loading="lazy" so they don't compete with critical content.

This isn't complex. It's just disciplined. Most slow sites we audit have oversized PNGs with no dimensions and no lazy loading — fixable in an afternoon if you know what to look for.

Hosting: the floor under everything

You can build the fastest site in the world and lose it all on a £3/month shared hosting plan with a server in Virginia. For UK businesses serving UK customers, your server needs to be in the UK.

Our managed hosting through Unity Tech runs on NVMe storage with UK-based infrastructure. That's a measurable LCP advantage over shared hosting — typically 200–400ms faster on Time to First Byte alone. It's not the glamorous part of web performance, but it's the foundation everything else sits on.

The 5-step stack selection process

1. Define your goals and conversion priorities. What's the site's job? Lead generation? Bookings? Portfolio showcase? The answer narrows your options immediately.
2. Set CWV non-negotiables. Decide upfront: LCP under 2.0s, INP under 150ms, CLS under 0.08. These become your acceptance criteria, not aspirations.
3. Shortlist 2 stack options. Don't evaluate 10 platforms. Pick the 2 most credible routes for your use case and compare them head-to-head on speed, cost, maintenance, and team fit.
4. Prototype key templates. Build the homepage and one service page in each option. Measure real performance, not theoretical benchmarks from the platform's marketing site.
5. Select based on measured outcomes. The stack that hits your CWV targets with the lowest maintenance overhead and best cost-over-3-years wins. Not the one with the nicest dashboard.

If you're not sure how to run this process yourself, our platform decision support service does exactly this.

Stack choices: common questions