AI website speed and performance

AI website speed and performance: a practical checklist

Published 2 March 2026 · 9 minute read · By AI Website Builder UK

Why AI-built sites are so often slow, what Core Web Vitals actually measure, and the fixes that make the biggest difference.

An AI builder optimises for looking impressive in a demo, not for loading quickly on a five-year-old Android in a car park with two bars of signal. That is where most of your customers actually are.

Why AI-built sites are slow

Three causes, in order of impact. First, uncompressed hero images straight from a stock library at 3000 pixels wide. Second, template JavaScript bundles that ship animation, carousel, lightbox and analytics libraries whether or not the page uses them. Third, web fonts: four weights of two families, each a separate download that blocks text rendering.

What Core Web Vitals actually measure

Metric	What it means	Target
Largest Contentful Paint	When the main content becomes visible	Under 2.5s
Interaction to Next Paint	How quickly the page responds to a tap	Under 200ms
Cumulative Layout Shift	How much the layout jumps while loading	Under 0.1

On template sites, LCP is nearly always the hero image and CLS is nearly always images or ads without reserved space. Both are cheap to fix.

Images: the biggest single win

1. Export at the maximum size actually displayed. A 1600px-wide hero does not need a 3000px file.
2. Convert to WebP or AVIF. Expect 50-80% smaller files at the same visual quality.
3. Always set width and height attributes so the browser reserves space.
4. Add loading="lazy" to everything below the fold, and never to the hero.
5. Add fetchpriority="high" to the hero image so the browser fetches it first.
6. Use decoding="async" to keep image decoding off the main thread.

On the average AI-built site, doing only this halves the load time.

Scripts, fonts and third-party bloat

• Remove any script the page does not use. Chat widgets, heat maps and A/B tools are the usual offenders.
• Load remaining scripts with defer so they never block rendering.
• Limit yourself to two font families and at most three weights, with display=swap.
• Preconnect to font and CDN origins so DNS and TLS happen early.
• Prefer CSS transitions over JavaScript animation libraries.
• Respect prefers-reduced-motion: it is both an accessibility win and a performance one.

Hosting and caching

Cheap shared hosting with a slow time to first byte undoes everything else. Look for a host with a UK or nearby data centre, HTTP/2 or HTTP/3, and Brotli or gzip compression enabled. Set far-future cache headers on static assets and version filenames when they change.

Enable HTTPS everywhere and make sure exactly one hostname is canonical, with everything else redirecting to it in a single hop.

A one-hour speed checklist

1. Run PageSpeed Insights on your busiest page, mobile tab only.
2. Find the LCP element it names and optimise that one asset first.
3. Compress and convert every image above 200KB.
4. Add width, height and lazy loading attributes site-wide.
5. Defer all non-critical scripts.
6. Cut unused font weights.
7. Enable compression and caching at the server.
8. Re-test and record the numbers so you can prove the improvement.

Most AI-built small business sites go from a mobile score in the 40s to the high 80s in an hour of this work.

Frequently asked questions