Most UK Websites Are Too Slow for AI Search to Bother With (And Here’s Why)

There’s a quiet problem sitting under most of the AI SEO advice being sold to UK businesses right now. Almost all of it assumes your website is actually capable of doing what’s being asked of it. If you’ve been reading anything about AI search lately, you’ll have noticed most of it ends in the same place. The work you’ve already done counts; it just needs to catch up with how AI tools now consume it. Add the schema, write the FAQ blocks, and properly structure the content. 

For most UK SME websites, that’s a big assumption. And it’s the one thing nobody’s properly talking about. None of that work will catch up unless something more fundamental changes first. The site itself.

All of that work eventually depends on the website being fast enough and clean enough for AI tools to read and trust in the first place.

This is the part of the conversation that’s harder to have, because it goes a layer below content and SEO and lands in development territory. But it’s the layer that decides whether any of the AI work above it actually pays off. So let’s talk about it properly.

The Thing Nobody Mentions about AI Tools and Your Website

Most people picture AI search engines as patient. They sit, they read, they decide. That isn’t what happens. When ChatGPT, Gemini, AI Mode or Google’s AI Overview goes to retrieve a page, it isn’t browsing the way a human does. It’s running a tightly time-boxed fetch. 

AI bots behave very differently from Google’s traditional crawler. They prioritise speed and tend to be far less patient with slow-loading pages, which means a site that takes too long to respond often doesn’t make the cut at all. If your site takes too long to load, or if the HTML it returns is too heavy to parse cleanly, the bot gives up and moves on. It doesn’t reschedule. It doesn’t try again gently. It just doesn’t include you.

And here’s the bit that catches most business owners off guard. The page never appears in any kind of error log. The bot didn’t fail. It just chose a faster competitor. 

Your traffic dashboard looks fine. Your rankings look fine. You’re simply not being cited, and the only way you’d know is if you actually went and ran your customer queries through ChatGPT and Gemini yourself, which most businesses still don’t.

What we see consistently across the sites we audit is that strong performance doesn’t guarantee AI citation, but poor performance reliably prevents it. Speed isn’t a lever you pull to win. It’s the floor you have to stand on to be in the game at all. 

If your site sits below that floor, no amount of AI SEO or GEO advice will rescue it.

What “Too Slow” Actually Means In 2026

Google’s Core Web Vitals are the technical thresholds Google uses to measure whether a website performs well enough to be worth ranking. Most UK SME websites haven’t been audited against them in years, and the numbers worth knowing are:

• Largest Contentful Paint (LCP) is the time it takes for the main bit of content on your page to appear. The “good” threshold dropped from 2.5 seconds to 2.0 seconds. Anything slower starts to hurt you.
• Interaction to Next Paint (INP) replaced First Input Delay back in 2024. It measures how quickly your page responds to clicks, taps and key presses throughout the session, not just the first. Anything above 200 milliseconds is a problem.
• Cumulative Layout Shift (CLS) measures how much your page jumps around as it loads. Anything above 0.1 hurts your business.

Alongside those three, AI tools are paying close attention to two more things that don’t appear in the official Core Web Vitals at all. 

The first is Time to First Byte (TTFB), which is how long your server takes to send the first scrap of data after it’s been asked.  Anything above 200 milliseconds starts to push AI crawlers towards giving up. 

The second is HTML payload size. AI bots have memory and compute budgets. The leaner your raw HTML (before images or scripts), the easier it is for them to fetch, parse and use your content. Heavy HTML payloads make a site harder to read and quietly push you down the citation queue.

In our experience, we routinely audit UK websites that ship 2-3 MB of HTML per page. Those sites are quietly invisible to AI search, and no one is telling them.

You can check most of this for free in about ten minutes. PageSpeed Insights, Google Search Console, and Chrome’s built-in DevTools (right-click any page, select Inspect, then open the Lighthouse tab) all provide the relevant numbers.  Those ten minutes are the cheapest research you can do.

So, Why Are Most UK Websites Slow?

Two things, mostly and with time they compound. And neither of them is anyone’s fault exactly, which is why they’re so hard to spot.

The Page-Builder Problem

The vast majority of UK SME websites are built with visual page builders. WordPress with Elementor, Divi or WPBakery. Wix. Squarespace. GoDaddy’s site builder. Shopify with various theme builders sitting on top. These tools made building a website cheap, fast and accessible, which is genuinely a good thing. 

The trade-off, which nobody mentions when they’re selling you the build, is what they do to the underlying HTML.

Visual page-builders work by wrapping every element on your page in stacks of nested divs, so they can be moved, styled, and rearranged inside the editor. The result is HTML that’s three or four times longer than it needs to be, full of inline styles, and packed with JavaScript that runs on every page load. Add a few animations, a slider, a pop-up builder, a cookie banner, and you’ve got a page that takes 3 to 5 seconds to become interactive on a decent connection, and significantly longer on a slower one.

For a human user, that’s frustrating but tolerable. They wait. For an AI crawler operating on a one-second budget, it’s a polite refusal. They leave.

This isn’t an argument against WordPress or against page-builders themselves. It’s an argument against using them lazily. A WordPress site built with disciplined development hours, sensible plugin choices, and proper performance tuning can be fast and AI-readable. A WordPress site built by dragging and dropping in Elementor and ticking every “add this feature” box can’t.

The Plugin Tax

The other half of the problem is plugin sprawl. The average UK WordPress site we audit runs somewhere between 25 and 40 active plugins. 

Each one was installed for a reasonable reason at the time. SEO plugin. Form plugin. Backup plugin. Security plugin. Booking plugin. Live chat. Reviews. Cookie compliance. Newsletter signup. Image gallery. Social sharing. Accessibility widget. Page builder. Page-builder add-on. Page-builder add-on extension.

Each plugin loads JavaScript, often loads its own CSS, often makes its own database queries and often loads on every single page, whether it’s needed there or not. The cumulative effect is brutal. The HTML balloons make the page slow to interact with, and the page’s structure becomes harder for an AI crawler to make sense of, even when it does manage to download it. 

The actual content is buried under layers of widget markup.

You can have the world’s best-written service-area page with perfect FAQ blocks and beautiful schema, and an AI tool will still skip it if the page takes 4 seconds to load and the actual answer is hidden 1.4MB deep in the HTML.

What “Fast And AI-Readable” Actually Looks Like

Here’s the bit most UK businesses haven’t been told. Sites that AI tools love tend to share a few characteristics, and almost none of them have to do with how the site looks.

• Clean, semantic HTML – Headings that are actually <h1> and <h2> tags, not styled divs. Lists that are actually <ul> and <li>. Article content wrapped in <article>. The structure of the document tells the AI tool what’s important, before it even reads the words.
• Server-rendered or static HTML – The actual content of the page is in the initial HTML response, not built in the browser by JavaScript afterwards. AI crawlers vary in how well they handle JavaScript rendering, and the safe assumption is that if your content isn’t there in the initial HTML, some of them won’t see it at all.
• A small, lean payload – Modest plugin footprint. Compressed images. JavaScript only where it’s actually needed. CSS that doesn’t ship the styles for every page on the site every time.
• Quick server response – Decent hosting (not the £3-a-month shared plan), proper caching, and a CDN if you’re serving any sort of geographic spread.
• Schema in the right place, in the right shape – Not seven different plugins all generating overlapping schema, which is what we see most of the time.

None of this requires throwing your website away. Some of it does require having a developer (an actual one, not a designer with a page builder) take a proper look at the foundations.

What You Can Do Without Rebuilding

Most UK businesses can’t credibly rebuild their website tomorrow, and most don’t need to. There’s quite a lot you can do on the existing site to get meaningful performance back.

The first thing is a plugin audit.

Open your WordPress admin, look at every plugin, and ask honestly: do we actually use this? We routinely deactivate 30 to 50% of plugins on first audits, and the site immediately gets faster and tidier without losing any functionality that the business actually noticed.

The second is image optimisation. 

Most UK SME sites are still serving uncompressed JPGs and PNGs at desktop size to mobile users. Modern formats like WebP and AVIF significantly reduce image file size. There are plugins that do this automatically, and yes, that’s one plugin worth keeping.

The third is to defer or remove non-critical JavaScript. 

Things like chat widgets, pop-up builders, and tracking scripts often load and run before the main content does. Pushing them to load later, or only on the pages that actually need them, often shaves a full second off LCP on its own.

The fourth is to look at your hosting honestly. 

If you’re paying £4 a month for shared hosting and wondering why your site is slow, you’ve found your answer. Decent UK hosting costs £20 to £50 a month, depending on the size of the site, and the difference in TTFB is often the single biggest performance gain you can buy.

The fifth is to clean up your schema. 

Pick one source of truth (usually a single SEO plugin properly configured), and turn off the schema output on every other plugin that’s quietly generating its own. Duplicated and conflicting schemas are a real problem on UK sites and a real reason AI tools struggle to parse them.

Together, those five fixes move most UK SME sites from being skipped by AI bots to being properly read by them. That’s the threshold that matters.

When a Rebuild Is Genuinely The Right Call

Sometimes the foundation is past saving. A few honest signs:

• The site is built on a page builder that’s been replaced or abandoned by its developer (older WPBakery setups, legacy Visual Composer builds, certain GoDaddy generations).
• LCP and INP are bad and can’t be fixed without restructuring the whole template, because the slowness is baked into the theme.
• The site is genuinely old (5 to 8 years old) and has accumulated so many half-implemented changes that no one on your team can confidently say what’s safe to remove.
• You’ve already spent meaningful money on plugins, optimisation, and “speed services”, and the numbers haven’t moved.

If two or three of those sound familiar, you’re probably looking at a rebuild. The fear most UK businesses have is that a rebuild will tank their rankings, and that fear is reasonable, because most rebuilds are handled badly. 

A proper migration, planned by people who understand both SEO and development, doesn’t have to cost you rankings. We’ve done dozens of rebuilds where the new site outranks the old one within weeks because the foundations are now actually capable of supporting the content. Anyway, that’s a different conversation, and one we’d rather have once you’ve seen the audit numbers for yourself.

How Does This Connect Back To Your AI Search Visibility

Here’s the part that matters. All the AI SEO advice floating around assumes the website itself is something AI tools can actually read.

If your foundations are sound, all that work compounds beautifully. Schema gets parsed correctly. FAQ blocks get cited. Service-area pages get recommended in AI answers. Reviews get pulled into AI summaries. The whole investment starts paying off in places it never used to.

If your foundations aren’t sound, none of it quite works. The AI tool gives up before it sees the schema. The FAQ block lives at the bottom of a 3MB page and never gets read. The service-area page is technically beautiful, but it never makes the cut because INP is at 800 milliseconds, and the bot moved on. You end up paying for the GEO work, not seeing the return, and concluding that AI search is a fad, when actually the website was the problem all along.

Which is why we’ve started running performance and AI-readability audits as the first step in any new client engagement. Not because we love technical work for its own sake, but because the technical layer turns out to be the difference between AI search advice that pays off and AI search advice that quietly doesn’t.

What To Do Next

If you’ve read this and you’re not sure whether your website is fast enough or clean enough for AI tools to read properly, the cheapest first step is to run your homepage and your top three commercial pages through PageSpeed Insights. 

If LCP is above 2 seconds, INP is above 200 milliseconds, or your HTML payload is over 1MB, you’ve got something to look at.

If the numbers are bad, or you’d rather have someone else look properly, book a free website performance and AI-readability audit with us. We’ll show you exactly where your site sits against the new 2026 thresholds. 

We’ll show you where AI tools are giving up on your site, what’s pulling your performance down, and what it would take to fix. No assumption a rebuild is the answer. Just a straight read of where you stand.

The thing worth remembering is this. AI search rewards businesses that have done the technical groundwork. That’s actually good news for the kind of UK businesses that take their websites seriously, because it puts the bar back where it should be: on whether the work is done properly, not on who can shout the loudest about doing it. 

The businesses that quietly fix their foundations now will be the ones recommended by ChatGPT, Gemini, AI Mode, and AI Overview, while their competitors are still wondering why their traffic looks healthy, but their enquiries are quietly drying up.

Remember, Foundations first. Everything else follows.