A fast website is one that shows its main content quickly, reacts as soon as someone taps, and does not jump around while loading. Google's Core Web Vitals turn that into three numbers to aim for: the largest content appears within 2.5 seconds, the page responds to a tap within 200 milliseconds, and the layout barely shifts (a score of 0.1 or less). Design for a phone first and most of the work is already done.
Here is how to measure your site and what usually slows small business sites down.
Measure before you change anything
- PageSpeed Insights (pagespeed.web.dev) tests a page and shows both lab results and, for busier sites, real visitor data.
- Google Search Console has a Core Web Vitals report that groups your pages into good, needing improvement and poor.
- Your own phone on mobile data. Open your site on an average phone, not the newest one, away from Wi-Fi. That is how many of your customers meet you.
- Your analytics. Check what share of your visitors are on phones. For most consumer businesses it is the majority, which is why the phone version matters more than the desktop one.
The usual culprits, and the fixes
Oversized images. The most common problem by far: a photo straight from a camera, thousands of pixels wide, shown in a box the size of a thumb.
Fix: resize images to the size they are shown, use modern formats such as WebP or AVIF, and load images below the first screen only when the visitor scrolls to them.
Too many scripts. Chat widgets, trackers, pop-ups and "just in case" libraries each add downloading and processing time, and they make taps feel sluggish.
Fix: list every script, remove what you do not use, and load the rest after the main content.
Web fonts. Several font families in several weights can delay text.
Fix: use one or two families, host them yourself, and let text show immediately in a fallback font.
Layout that jumps. Images, ads or banners without reserved space push content down while the page loads, and visitors tap the wrong thing.
Fix: give every image and embed its width and height, and reserve space for anything that loads late.
A slow server or no caching. If the server takes seconds to answer, nothing else can be fast.
Fix: decent hosting, caching for pages that do not change per visitor, and compression for text files.
Mobile-first in practice
Mobile-first does not mean shrinking the desktop site. It means designing for the small screen first and adding to it on larger ones.
- Put the one important action first. On a phone, the first screen should say what you offer and how to act on it: call, message, buy, book.
- Make tap targets large and keep them apart, so thumbs hit what they aim for.
- Use readable text sizes without zooming.
- Simplify navigation. A few clear sections beat a menu that copies the desktop one.
- Make forms easy on phones. Use the right keyboards for phone numbers and emails, allow autofill, and ask only for what you need.
- Test checkout on a phone. It is where most sales are won or lost.
- For Arabic sites, do right-to-left properly: mirrored layouts, correct alignment and fonts designed for Arabic, not just translated text.
Orlisse, a store on our portfolio, was designed mobile-first for exactly these reasons.
Builders or custom code?
Website builders have improved, but you only control what the template allows: you cannot remove code you do not need. A site built for you can ship only what each page uses. If your builder site fails Core Web Vitals and the template settings do not help, that limit is usually the reason.
How we help
- Bug Fix & Optimization, $30: something broken or slow? We diagnose, fix and optimise, whether or not we built the site.
- Website Refresh, $60: an updated design and better layout for an existing site.
- Seeker, $91: a new professional website, delivered in 5 business days.
- SEO Starter, $61: technical setup, metadata and structured data so search engines understand your pages.
The code 40 takes 40% off eligible plans.
FAQ
Does page speed affect Google rankings?
Page experience, including Core Web Vitals, is one of the signals Google uses. Relevance and quality of content matter more, but between similar pages a fast one has an advantage, and visitors are more likely to stay.
What is a good loading time?
Aim for the main content to appear within 2.5 seconds on a phone, which is Google's threshold for a good Largest Contentful Paint.
Why is my site fast on my computer but slow on my phone?
Phones have slower processors and often slower connections. Heavy scripts and large images hurt far more on a phone, so always test there.
Can you speed up a site someone else built?
Yes. That is exactly what our Bug Fix & Optimization service is for.
See all our fixed-price plans on the web services page.