Speed is one of those things you stop noticing when it is good and cannot ignore when it is bad. A page that takes a long time to show anything, a button that lags when you tap it, or text that jumps just as you go to read it all make a site feel unfinished.
AI builders and DIY tools generally produce reasonable code. Where sites slow down is in what gets added afterward: huge photos, background videos, several fonts, a chat widget, a few tracking scripts, a review badge. Each one seems small. Together they add up.
Most speed problems are not about code. They are about weight.
Core Web Vitals, in plain English
Google measures page experience with three numbers called Core Web Vitals. You do not need to memorize them, but it helps to know what they mean.
- LCP, Largest Contentful Paint. How long it takes for the main thing on the page, usually a big image or headline, to appear. Google treats 2.5 seconds or less as good.
- INP, Interaction to Next Paint. How quickly the page responds when someone taps, clicks or types. Google treats 200 milliseconds or less as good.
- CLS, Cumulative Layout Shift. How much the page jumps around while it loads. Google treats a score of 0.1 or less as good.
These are measured on real visitors when Google has enough data, and simulated in a lab test when it does not.
Why it matters
Visitors judge you quickly. A slow or jumpy page feels less trustworthy, and people on phones are the least patient of all. Speed also plays a part in how search engines see your site. Most importantly, it is a matter of respect for the person on the other end.
What people miss
- Oversized images. A photo straight from a phone or stock site can be many times larger than it needs to be. Images should be sized for how they are displayed and saved in a modern format like WebP or AVIF.
- Lazy loading in the wrong place. Images further down the page should load later. The main image at the top should not, or it delays LCP.
- Missing image dimensions. When width and height are not set, the page shifts as images load. That is CLS.
- Too many fonts. Every font family and weight is another download. Two families with a few weights is usually plenty.
- Autoplay background video. It looks great on desktop and can be heavy on mobile. A compressed, short clip with a still image fallback, or no video on phones, is often better.
- Third-party scripts. Chat widgets, heatmaps, pixels, embeds and old tracking tags each add work for the browser. Many sites carry scripts for tools they no longer use.
- Testing only on desktop. Your laptop on office Wi-Fi is the best-case scenario. Your customers are not always in it.
How AftUp handles it
We look at your site the way your visitors experience it, starting on mobile. We work inside your builder, so there is no rebuild.
- Starter gives you 24/7 uptime monitoring and one small change a month, which can be used for a quick win like replacing an oversized hero image. Your monthly report notes anything that looks slow.
- Growth includes page speed tuning as a standing part of the plan, with up to 2 hours a month for fixes. Typical work includes compressing and resizing images, cleaning up fonts, removing unused scripts, fixing layout shift and tuning how video loads.
- Scale adds up to 6 hours a month for deeper work, such as restructuring a heavy page or reviewing how your app loads its code, plus a quarterly strategy call to keep speed in the plan as you add features.
Speed and search go together, so our SEO page is a natural next read. Many speed fixes, like proper image dimensions and clear structure, also help accessibility.
Do it yourself
You can learn a lot in fifteen minutes:
- Run PageSpeed Insights. It is Google’s free tool. Enter your homepage and check the mobile results first. If real-user data appears at the top, that matters most. The lab score below it helps you diagnose.
- Read the top suggestions. Look for items about image size, unused JavaScript and render-blocking resources. They point to your biggest wins.
- Fix your heaviest images. Resize large photos to roughly the width they display at, and export them as WebP. Many builders do some of this automatically, but uploads still matter.
- Count your fonts. Remove weights and families you are not using.
- Audit scripts and widgets. List every third-party tool on the site. Remove anything you no longer use or check.
- Test on your own phone. Turn off Wi-Fi, load your site on cellular, and tap around. Notice what feels slow or jumpy.
- Repeat after big changes. New sections, embeds and apps are where speed usually slips.
If a competitor’s site feels snappier than yours, our post on why competitors can look better in Google covers what else might be going on.
Want to know what is slowing your site down? A free site check will point you to the biggest fixes.