Landing pages that load before the ad click is wasted

Here's a thing that happens more than people think. A business runs Instagram or Google ads, the clicks come in, the cost per click looks fine, and almost nobody gets in touch. They tweak the ad copy. They change the audience. Nothing moves.

Then I open the landing page on a normal phone, on mobile data, and wait. Four seconds. Six. A big hero image is still drawing itself line by line. Anyone who clicked from a bus or a warung is long gone by then, and the advertiser has already paid for that click.

The click is paid for either way#

Ad platforms charge when someone taps the ad, not when they see your page. If the page takes too long, the visitor leaves and you still get billed.

Google published research a few years ago showing that as page load time goes from one second to three, the probability of a mobile visitor bouncing goes up by 32%. Go to five seconds and it climbs much further. You don't need to memorise the exact figures. The direction is what matters: every extra second loses people who were interested enough to tap.

And a slow page hurts twice on Google Ads. Landing page experience feeds into the quality score, and a lower score usually means paying more per click for the same position.

Why "it's fast on my laptop" means nothing#

Most landing pages get approved on the owner's laptop, on office Wi-Fi, often with the page already cached from twenty previous visits. Of course it feels instant.

Your customers are on mid-range Android phones with a few other apps open, on a 4G signal that drops to something worse whenever they move. A page that weighs 6 MB and runs a pile of scripts behaves very differently there.

So test the way your customers actually browse. Open the page on an average phone, switch off Wi-Fi, and clear the cache or use a private tab.

What usually slows a landing page down#

I've audited a fair number of slow landing pages by now, and the same culprits keep turning up.

Images that are far too big#

This is the most common one by a mile. A photo straight from a camera or a stock site can be 3 to 5 MB. Shown on a phone screen, it needs maybe 150 KB. Resizing to the size actually displayed and exporting to WebP or AVIF often cuts the page weight by more than half on its own.

Sliders and videos at the top#

An autoplaying carousel or a background video in the first screen looks impressive in the design mockup. On a phone it means downloading several big files before the visitor sees anything useful. One strong image and a clear headline nearly always does better.

Too many scripts#

Chat widgets, two analytics tools, a heatmap, a pixel for every ad platform, a popup tool, a font loader. Each one is small. Together they can block the page for seconds. Tracking matters, but it can load after the visitor sees the page.

Heavy page builders and themes#

Some builder themes load every feature they offer on every page, used or not. A one-page offer ends up shipping code for sliders, shops and forms nobody sees.

Fonts#

Four font families with six weights each is a lot of downloading just to render a headline. Two families, two or three weights, loaded properly, is plenty.

Core Web Vitals, in plain words#

Google measures page experience with three numbers it calls Core Web Vitals. You'll see them in PageSpeed Insights.

LCP (Largest Contentful Paint) is how long until the biggest thing in the first screen appears, usually the hero image or headline. Google's target is under 2.5 seconds.

INP (Interaction to Next Paint) is how quickly the page reacts when someone taps a button. Under 200 milliseconds is considered good.

CLS (Cumulative Layout Shift) is how much things jump around while loading. You know the feeling: you go to tap "WhatsApp" and the button moves because an image above it just loaded. Lower is better, under 0.1 is the target.

If your landing page fails LCP on mobile, that's usually the first thing worth fixing for an ad campaign.

How to check your own page#

Go to PageSpeed Insights, paste your landing page URL, and look at the Mobile tab, not Desktop.

If your site gets enough traffic, the top section shows real data from Chrome users. That's the most honest number you'll get. Below it is a lab test, which is useful for finding causes. The suggestions list ("Properly size images", "Reduce unused JavaScript") tells you roughly where the weight is.

Don't chase a perfect 100. A score in the 90s on mobile with good Core Web Vitals is excellent. Going from 40 to 85 matters far more for your ads than going from 92 to 99.

A quick checklist before you spend on ads#

• Open the page on a mid-range phone using mobile data. Does the main message show within about two seconds?

• Is the hero a single, compressed image instead of a slider or video?

• Is the WhatsApp or contact button visible without scrolling, and does it stay put while the page loads?

• Do analytics and pixels load after the page content, rather than before it?

• Did PageSpeed Insights (Mobile) pass LCP and CLS?

• Is there one clear offer on the page, not five?

That last one isn't technically about speed, but it's the same idea. You paid to get someone onto the page. Don't make them work to understand what you want them to do.

How I build them#

When I build a landing page, it's a static page. It's built ahead of time and served from a CDN, with images sized for phones, two fonts at most, and tracking (GA4 and the Meta Pixel, which I set up for free) loaded once the page is usable. The WhatsApp button is in the first screen and pre-fills a message so the lead knows what to say.

None of that is magic. It's mostly saying no to things that look nice in a mockup and cost you money in a campaign.

If you're running ads to a page that feels slow, send me the link on WhatsApp. I'll tell you honestly whether it needs a rebuild or just a few fixes.