The campaign looks healthy inside Google Ads. Impressions are steady, the click-through rate is reasonable, the cost per click is what you expected. Then you open your analytics and the landing page shows noticeably fewer sessions than the clicks you paid for, a short average engagement time, and very few form submissions. Somewhere between the click and the page, people are disappearing.
Landing page speed for Google Ads is one of the first things to check when that happens, because an ad visitor who leaves during loading costs you exactly as much as one who stays and buys. Below you will find what Google says about landing pages in general terms, why ad visitors are less patient than other visitors, and how to build and test a page that loads quickly without losing the tracking you need to judge the campaign.
The click you paid for but never saw
Every ad click starts a race. The browser has to reach your server, receive the page, download the files it depends on and draw something useful on screen, while the visitor decides whether to wait. If the visitor goes back first, Google still counts the click, but your analytics may never record a visit, because its tracking script had not run yet.
That is why a gap between ad clicks and landing page sessions deserves attention. Some gap is always there: people decline cookies, block scripts, or click twice. Our post on why ad numbers and analytics rarely match explains the normal reasons. What should worry you is a gap that is much wider on mobile than on desktop, or much wider on one landing page than on another page receiving similar traffic. Both patterns often point at load time. If you are new to the measurements involved, our complete guide to website speed explains how the separate parts fit together.
What Google says about landing page experience
Google Ads uses Quality Score as a diagnostic for keywords, and it has three components: expected click-through rate, ad relevance and landing page experience. Landing page experience is Google’s view of how useful and relevant your page is to people who click the ad. Google’s own guidance on improving it covers relevant and original content, clear navigation, trustworthiness, and pages that work well and load quickly on mobile devices.
Two cautions keep this in proportion. First, Google does not publish a load-time number that earns a good rating, so be wary of anyone who quotes one. Second, landing page experience is about the whole page, not speed alone. A fast page that does not match the ad’s promise will still disappoint visitors and Google alike. Matching the message is the subject of our Google Ads landing page design service page; this post stays with the loading side.
What you can say with confidence is that Google states better ad quality, including landing page experience, can lead to lower costs and better ad positions. Speed is one part of that you can actually control.
Why landing page speed for Google Ads matters more
Someone who searches for your business by name will wait for your site. An ad visitor is different, and it helps to be clear about how.
- They have not chosen you yet. They chose an ad among several, and the other ads are one tap back.
- Many of them are on a phone. Check the device report in your account; for a lot of small businesses, phones bring most of the clicks, and that means slower processors and less reliable connections than the laptop you built the page on.
- Some arrive inside an app. Clicks from apps can open in an in-app browser, which starts without your site’s files cached and sometimes behaves differently from a normal browser.
- It is often their first visit. Nothing from your site is stored in their browser cache, so they download everything from scratch.
Put together, the ad visitor is close to the worst case for page loading. Test for that visitor, not for yourself.
Building a lean landing page
The fastest landing pages are usually the plainest ones. That does not mean ugly. It means every item on the page earns its place.
One clear first screen
The first screen on a phone should show the headline that matches the ad, a short line of support, and the action: a call button, a short form or a WhatsApp link. Use one image at most, sized for the space it fills and compressed properly. A slider or autoplay video at the top of an ad landing page is weight the visitor pays for before they read a word.
No site-wide baggage
If the landing page is built inside your main WordPress site, it inherits everything the site loads on every page: the full menu, footer widgets, slider scripts, popup plugins, a chat widget, social feeds. Many landing pages do not need any of that. A template with no header navigation, or a page builder layout that loads only what it uses, can remove a lot of work. Check what is actually loading rather than assuming.
Fonts and icons
One font family in two weights is usually plenty for a landing page. Loading a whole icon library to show three icons is a common, avoidable cost.
A form that does not wait
Form plugins sometimes load heavy scripts, spam protection and styling on page load. Keep the form short, make sure its spam protection does not delay the page from becoming usable, and send yourself a test submission from a phone after every change.
Agreeing limits for all of this before the page is designed saves arguments later. A performance budget for the page is a simple way to write those limits down.
The tracking scripts trade-off
Ad landing pages attract scripts. The Google Ads tag, Google Analytics, perhaps a Meta pixel, a call-tracking script, a heatmap tool someone tried last year, a tag manager containing tags nobody remembers adding. Each one is code from another server that the browser has to fetch and run.
You cannot simply strip them all out, because without conversion tracking you cannot tell whether the campaign is working, and automated bidding has nothing to learn from. The answer is to keep what you use and remove what you do not:
- List every tag that fires on the landing page. Tag Assistant, your tag manager’s preview mode, or the browser’s network panel will show them.
- For each one, write down who uses its data and for what. If nobody can answer, it is a candidate for removal.
- Keep the Google Ads conversion tracking and your analytics. Those are the minimum for judging the campaign.
- Remove duplicates. The same tag installed both by a plugin and through a tag manager is surprisingly common.
- Delay anything that is not needed for the first view, such as heatmaps and chat, until after the page has loaded, and check that the delayed tools still record what you need.
The wider problem of external scripts is covered in how third-party scripts slow a website down.
Testing the real ad URL
Most people test their landing page by typing its plain address into a speed tool. Ad visitors do not arrive at that address. Their URL carries extra parameters, such as the click identifier Google adds when auto-tagging is on, and your own UTM tags if you use them.
This matters because some caching setups treat a URL with an unfamiliar query string as a different page. Instead of serving the ready-made cached copy, the server builds the page from scratch for every ad visitor, which can make the ad landing page load time far worse than your test suggested. Many caching plugins have a setting to ignore common tracking parameters; check that yours does, and confirm it by testing.
A practical routine before a campaign goes live:
- Copy the final URL from the ad, add a made-up click identifier parameter, and test that exact address in PageSpeed Insights on mobile.
- Run the same test two or three times and compare, since a single run can vary.
- Open the URL on an ordinary phone using mobile data, with Wi-Fi off, and time how long it takes before you could tap the main button.
- Submit the form or tap the call button, and confirm the conversion is recorded in Google Ads.
What to measure after launch
Once the campaign runs, compare clicks with landing page sessions by device each week, and keep an eye on conversion rate per landing page. If you make the page faster, note the date in a shared place so that a later change in results can be traced back to it. Other changes, such as bids, budgets and keywords, will be happening at the same time, so treat the comparison as evidence rather than proof. How speed connects to enquiries more generally, and how to measure it fairly, is the subject of our look at whether speed affects conversions.
The ad strategy itself, from keywords to bidding, is a separate subject and outside what this page covers. If the page is fast and matched to the ad but still not converting, the problem is likely to be the offer, the audience or the follow-up.
Frequently asked questions
Does a faster landing page lower my cost per click?
It can help, but there is no fixed relationship you can count on. Landing page experience is one of the three Quality Score components, and Google says better quality can lead to lower costs. Speed is only part of landing page experience, and bids and competition also decide what you pay.
Should I build ad landing pages outside my main website?
Not necessarily. A page inside your WordPress site can be fast if it uses a lean template and does not load site-wide plugins it does not need. A separate builder or tool can also work. Choose whichever lets you control what loads and keeps conversion tracking reliable.
Is it safe to delay the Google Ads tag to make the page faster?
Be careful. If the tag loads too late, visitors who convert quickly or leave early may not be recorded, and your campaign data becomes less reliable. It is usually better to keep the ads and analytics tags loading normally and delay less important scripts such as heatmaps or chat.
How do I know if a slow landing page is hurting my campaign?
Compare ad clicks with recorded landing page sessions by device, and compare conversion rates between landing pages that receive similar traffic. A much wider click-to-session gap on mobile, or one page converting far worse than the rest, suggests visitors are leaving while it loads.
Running Google Ads to pages on a WordPress site is one of the cases our speed optimisation service was set up for. Tell us which pages receive ad traffic when you get in touch; that way the audit can test the URLs your ads actually use, and anything in the fix list that touches your conversion tags can be agreed before it is changed.
Next in this series: Website Speed Audit Checklist: What a Real Audit Covers
