Web AI Processors
This blog explains website speed and Core Web Vitals in plain English. No dev jargon, no scare tactics, and we don't sell website builds.
An oversized hero image, six plugins loading in the background, and a visitor who's already gone.
Compressed images, fewer scripts, and a page that actually shows up when someone needs it to.
Most small business sites don't fail overnight. They pick up weight slowly: another app here, a bigger photo there, a plugin nobody remembers installing. Here's what we cover.
Google measures three things when it decides whether your site feels fast: how quickly the biggest element appears, how fast the page responds when tapped, and whether things jump around while loading. We break down each one in everyday language, including the actual published thresholds so you know what "good" looks like.
Jump to Core Web VitalsThat beautiful full-width photo at the top of your homepage is often the single heaviest file on the page.
See whyEvery extra chat widget, slider or form builder adds another script your visitor has to download first.
See what adds upYou don't need to pay anyone to find out how your site is performing right now.
Show me the toolsGoogle publishes three metrics it uses to judge how a page feels to use. They sound technical. They aren't, once you see what they're actually measuring.
How long it takes for the biggest visible element, usually your hero image or heading, to actually appear on screen.
How quickly the page responds after someone taps a button or clicks a link. Sluggish scripts make this feel laggy.
Whether text and buttons jump around while the page is still loading images or fonts underneath them.
You don't need an account, a subscription or a developer to find out how your site is doing right now. These are the same tools we reference throughout this blog.
Paste your homepage URL in and get a plain score plus a breakdown of your Core Web Vitals, on both mobile and desktop.
If you've verified your site, this shows real visitor data over time rather than a single test.
A free waterfall view of every file your page loads, useful for spotting which image or script is the heaviest.
Right click, Inspect, then Lighthouse. Built into the browser you're probably already using.
It's almost always the same story. Someone uploaded a beautiful photo straight from a camera or a stock library, dropped it into the homepage banner, and never touched it again. That single file can end up heavier than every other element on the page combined.
Because it's usually the largest thing visible when the page loads, it's often exactly what LCP is measuring. A slow hero image doesn't just look fine while loading slowly. It actively drags down the metric Google uses to judge your homepage.
The fix is rarely "use a smaller photo." It's resizing the file to the dimensions it's actually displayed at, exporting it as a modern compressed format, and making sure it isn't set to lazy-load, since the one image visible immediately shouldn't wait in a queue behind ones further down the page.
No single extension usually breaks a site. It's the accumulation. Here are the categories that show up again and again across Squarespace, Wix and WordPress sites we've looked at.
Drag-and-drop builders on top of builders, each adding its own stylesheet and script bundle to every single page, whether that page uses the feature or not.
Auto-rotating image galleries are popular but tend to load every slide's full-size image upfront, whether a visitor scrolls through them or not.
Handy for support, but many load their full script on every single page load rather than only when a visitor opens the chat window.
Two or three plugins each generating their own schema markup, sitemap and firewall checks in parallel, duplicating work in the background.
Loading an entire icon set or several font weights when the site only ever uses a handful of them anywhere.
Squarespace handles a lot of optimisation itself, so the usual weight comes from uncompressed uploaded photos, video backgrounds, and third-party embeds like booking widgets or fonts pulled from outside the platform.
Animation-heavy templates and additions from the Wix App Market are common causes. Each app tends to add its own script, and it's easy to end up with several running that nobody actively uses anymore.
The plugin count, theme quality and hosting plan all matter here more than on hosted platforms. A cheap shared hosting plan paired with a heavy theme and a dozen plugins is a common combination.
Written so you can follow along on your own site, without needing to hire anyone. Have a look through our full topic library for the details.
Free tools and the settings that actually matter.
What each section actually means, in order.
How to test before you remove anything permanently.
Why your browser remembers a page and when that stops helping.
Why your phone experience can differ a lot from desktop.
They're a set of measurements Google uses to judge how a page feels to actually use, covering loading speed, responsiveness and visual stability. They matter because a slow, jumpy site tends to frustrate visitors before they read a word of your content.
Hosted platforms handle a lot of the technical groundwork, but they can't control what you upload or install. A large uncompressed photo or a handful of third-party apps can slow a site down regardless of which platform it's built on.
Not necessarily. Many common issues, like image size and unused plugins, can be addressed by the site owner directly through the platform's own dashboard. Our guides are written with that in mind. We don't offer web development services ourselves.
It can, if the plugin is doing something the rest of your site depends on. That's why our guides recommend testing changes one at a time and checking the site afterwards, rather than removing several things at once.
A quick check after any change, such as a new photo, plugin or template update, is a reasonable habit. Beyond that, an occasional look every few months is usually enough to catch anything that's crept up gradually.
Speed is one of several factors that shape how visitors experience a website, alongside content, design and relevance to what they were searching for. This blog focuses specifically on the technical performance side of that picture.