Someone taps your link from WhatsApp or Google. They don’t know your business yet. They’re standing in a queue, or on a sofa with a bad signal, and they’ll give your page a few seconds before they decide to stay or go back.
A lot happens in those seconds, mostly out of sight. Knowing the order of events is useful because each step can be slow for a different reason, and the fix for one isn’t the fix for another. So let’s walk through it as it happens.
Before your page exists: finding and reaching your server
The moment the person taps, their phone has to work out where your website lives. It looks up your domain name to get the server’s address, then opens a secure connection to it. You can’t see any of this, but it takes time, and it takes longer on a weak mobile network.
Then the server has to answer. If your site runs on WordPress or a PHP framework, the server runs code and asks the database for content before it can send anything back. A cheap, overcrowded hosting plan makes this step slow, and no amount of image compression will fix it. If a page feels slow to even start, this is usually where the time went.
- Good hosting: a server that responds quickly, ideally close to your visitors.
- Caching: save a ready-made copy of pages so the server doesn’t rebuild them for every visitor.
- A CDN: serve images and files from a location nearer the visitor.
The browser reads your page and starts collecting things
Once the first chunk of the page arrives, the browser reads it and discovers everything else it needs: stylesheets, scripts, fonts, images. Each of these is a separate trip to fetch. Some of them are “render-blocking”, which means the browser won’t show anything until they’ve arrived. A big pile of scripts from chat widgets, analytics tools, sliders and marketing plugins is the usual reason a page stays blank for a while.
A simple rule helps here. Ask of every script and plugin: does a visitor need this in the first second? If not, it can wait until after the page shows.
The first thing appears
Then comes a good moment: something shows on the screen. A background colour, a menu, some text. It’s a relief for the visitor, because it proves the page is working. But the page isn’t useful yet.
What matters more is when the biggest piece of content in view is ready, usually a banner image or the main headline. Google calls this Largest Contentful Paint, or LCP, and the target is 2.5 seconds or less. A huge unoptimised hero image is the most common reason sites miss it. A 3 MB photo straight from a camera or a stock site doesn’t belong on a mobile page.
- Resize images to the size they’re actually shown at.
- Use modern formats like WebP where you can.
- Don’t lazy-load the main banner. Lazy loading is for images further down the page, and applying it to the first image delays it.
The page jumps around
You’ve probably tapped a button and had it move away at the last second because an image or an ad loaded above it. That’s layout shift, and it’s annoying enough that Google measures it. The score is called Cumulative Layout Shift, or CLS, and the target is 0.1 or lower.
The usual causes are boring, which is good news because they’re easy to fix. Images with no width and height set, so the browser doesn’t know how much space to save. Fonts that load late and swap in with a different size. Banners or pop-ups that push content down after it appears. Reserve the space in advance and most of it goes away.
The visitor tries to do something
By now the visitor has seen your page and is trying to act: opening the menu, tapping “Call now”, or scrolling to a form. If your page is still busy running heavy JavaScript in the background, it responds late, and a tap that does nothing feels broken. The metric is called Interaction to Next Paint, or INP, and the target is 200 milliseconds or less.
This is the one most often caused by too many third-party scripts. Every chat widget, tracker and pop-up tool competes for the phone’s processor, and a mid-range Android phone has far less to spare than the laptop your developer tests on.
Meanwhile, the visitor is making up their mind
While all this technical activity happens, a person is silently asking questions. Is this the right place? Does it look trustworthy? Where do I tap? They won’t read your page. They’ll scan it. A slow, jumpy page makes the answer to “can I trust this?” less likely to be yes, even if your business is excellent.
That’s why the first screen matters so much. A clear headline that says what you do, one obvious button, and a phone number or WhatsApp link that’s easy to find. All the speed work in the world doesn’t help if the first screen is confusing.
Test on a real phone, not just your laptop
This is where many people get fooled. A site feels instant on a developer’s fast laptop and office Wi-Fi, then crawls on a mid-range phone on a patchy 4G connection, which is how a lot of your visitors will actually see it. Phones have slower processors and less reliable networks, so the same page scores worse on mobile than on desktop.
Check it yourself. Open your site on a regular phone with mobile data and watch what happens, in the first few seconds especially. Then run it through Google’s PageSpeed Insights, and look at the Core Web Vitals report in Search Console if you have access. Those use real visitor data, which tells you more than a single test does.
The short list of fixes
If you only have time for a few things, these tend to help the most.
- Compress and resize images, especially the one at the top of the page.
- Set width and height on images so the layout doesn’t jump.
- Turn on caching and consider a CDN.
- Remove scripts and plugins you don’t use. Be honest about which ones those are.
- Delay non-essential tools, like chat widgets, until after the page has loaded.
- Upgrade hosting if the server itself is slow to respond.
Don’t over-tune it
A word of balance. Speed is one signal among many, and Google’s targets are a guide, not a guarantee of ranking well. A fast page with unclear content still won’t convert visitors. A slightly slower page that answers the visitor’s question clearly often does better. Fix the obvious problems first, then spend the rest of your effort on the content and the first screen.
Conclusion
Those first three seconds are a chain: server, browser, first paint, main content, layout, response to a tap. A weak link anywhere is felt by the visitor as one thing, “this site is slow”. Once you know which link is weak, the fix is usually much smaller than you’d think.
At Next Generation Technologies, we build and tune websites and web apps so they load quickly on the phones and networks your customers actually use. Not sure why your site feels slow? Contact us and let’s talk it through.
