Every euro you spend on a Google Ads click for a slow website is doing less work than the euro your competitor spends on a fast one, and the gap is priced into the auction whether you have looked for it or not. Reviewing server response logs this morning, the gclid parameter Google Ads stamps onto every paid click is impossible to miss once you know what to look for. So is how long some of those specific requests take to return a usable page. Nobody sets out to waste ad budget on purpose. Most businesses just never connect a slow site to what they pay per click, because nothing in the Google Ads dashboard spells it out.

What Quality Score Actually Measures

Google Ads Help describes Quality Score as a diagnostic estimate calculated from three components: your expected click-through rate, how relevant your ad is to the search, and something Google calls landing page experience, how relevant and useful the page someone lands on actually is. That third one is the one hosting and page speed touch directly. A landing page that matches the ad's promise, loads properly on a phone, and does not bury the offer under a slow-loading hero banner scores better on that component than one that does not.

So what does that mean in practice for a business running a campaign? It means your ad copy and your bidding strategy are only two-thirds of the story. The page a click actually lands on is doing real work in Google's own assessment of whether that click was worth showing you in the first place. Write the sharpest ad in your sector, bid aggressively, and still hand a share of every click's value back if the page behind it takes its time answering.

That third component is also the one most business owners have the least visibility into. Nobody reviews ad copy without reading it first. Plenty of people run a Google Ads campaign for months without ever loading their own landing page on a phone, on an ordinary mobile connection, the way an actual customer would meet it.

The Score You See Is Not What Sets Your Price

This is the part that trips up plenty of agencies, never mind business owners running their own campaigns. Google Ads Help states directly that Quality Score, the 1-10 number in your account, is not an input in the auction. It is a diagnostic tool for identifying where your ads and pages are underperforming, not a lever the auction pulls on directly.

That does not mean landing page speed is irrelevant to price. Google's Ad Rank documentation explains that Ad Rank, the calculation that actually determines whether your ad shows and what you pay, factors in your bid alongside "auction-time ad quality." That auction-time quality includes the same three ingredients as the diagnostic score: expected click-through rate, ad relevance, and landing page experience, recalculated fresh for every single auction rather than reported once as a static number. The dashboard score is a monthly-ish snapshot. The real pricing mechanism runs the same underlying signals live, every time someone searches.

What a Slow Page Actually Costs, in Cash

Google's own advertiser guidance does not hedge on this point: "the speed at which your page loads can be the difference between someone bouncing or buying." Its research arm, Think with Google, has published mobile page speed data showing that in retail specifically, a one-second delay in load time can reduce mobile conversions by up to 20%, a figure that has held up across years of Google's own published testing, not a single vendor's marketing claim.

Twenty per cent fewer conversions on the same spend is not a rounding error. It is the difference between a campaign that pays for itself and one a business owner quietly stops running six months later, having concluded, wrongly, that "Google Ads just does not work for us." Consider a fairly ordinary case: a driving instructor in Leitrim topping up her weekly ad budget every time bookings slow down, without ever timing how long her lesson-booking page takes to become usable on a learner's phone. The campaign was never the problem. Nobody had ever timed the page.

A slow landing page does not refuse the sale outright. It just quietly leaks a share of every one.

Core Web Vitals Are Not Only an SEO Checkbox

Google Search Central's Core Web Vitals guidance sets out three thresholds worth knowing even if you have never touched a ranking report: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. These exist as an organic search signal, and our Core Web Vitals guide covers why most Irish WordPress sites still fail at least one of them on mobile.

They matter here too, for a simpler reason: the same slow server response, unoptimised images, and layout-shifting page that fails a Core Web Vitals test is very often the same page failing Google's landing page experience assessment for paid traffic. You are not managing two separate problems, one for SEO and one for ads. You are managing one page, and it either loads properly or it does not, regardless of which channel sent the visitor.

That overlap cuts both ways, and it is good news if you treat it that way. Fix the server response time and caching behind a landing page for your Google Ads campaign, and the organic version of that same page benefits from the identical work. Nobody has to choose which channel gets the faster page. There is only one page to fix.

A Mistake I Would Not Repeat

I once told a client his Google Ads campaign "just needed more budget" after his enquiry numbers dipped, without first checking his site's own response times against his ad traffic logs. Turned out his checkout page was taking upwards of six seconds to become usable on mobile. More spend on the same slow page just meant burning through the extra faster. Cheap lesson, in hindsight. Would check the page load time before touching the budget every time now.

How to Check This on Your Own Site

Verify your current landing page speed. Run the specific page your ads point to, not your homepage, through Google's PageSpeed Insights or Search Console's Core Web Vitals report, and note the mobile score specifically.

Check your Landing Pages report inside Google Ads. Under Campaigns, the Landing Pages report shows conversion rate and cost per conversion by URL, which tells you whether a specific page is underperforming relative to the rest of the account.

Fix the actual bottleneck. Slow WordPress landing pages are usually a server response or caching problem, not a design one. Confirm your host is serving cached pages rather than rebuilding them from scratch on every single visit, and our complete guide to WordPress performance for business owners covers the full caching stack behind that if you want the detail.

Confirm the fix in production, on mobile, on a real connection. A page that loads fine on office broadband can still be sluggish on a customer's phone on mobile data. Test it the way an actual click will experience it.

The One Thing Speed Cannot Fix on Its Own

Landing page speed is one component of one component. A fast page with an offer that does not match the ad, or copy nobody was searching for, still scores badly on ad relevance and expected click-through rate, and no amount of caching repairs that. Fixing speed narrows the gap on the part hosting genuinely controls. It does not replace writing an ad that matches what the page actually delivers.

There is a real trade-off worth naming honestly too. If you are running a national campaign across hundreds of dynamically generated landing pages with a dedicated PPC agency and in-house development resource, a specialised landing page platform built for testing dozens of page variants against each other genuinely earns its keep at that scale. That is not most local businesses running a handful of campaigns for their own trade or shop, where the fix is simpler: one fast, well-cached set of pages, properly hosted.

Why This Sits With Your Host, Not Just Your Marketing

The CSO's most recent enterprise figures put internet sales at just over a third of small enterprises in 2025, slightly down on the year before, which means every enquiry a paid click generates matters more, not less, for the businesses that do run online campaigns. A landing page rebuilding itself from a database on every visit, with no object caching layer sitting in front of it, is going to lose that race before the click even lands.

Web60 runs on a stack built around exactly this problem: Nginx and PHP-FPM handling requests, FastCGI page caching serving pre-built pages instead of rebuilding them each time, and Redis object caching taking the database load off the slowest parts of a WordPress page. None of that requires a business owner to touch a server setting or hire anyone to tune one. It is included in the same €60 a year as the hosting itself, not an upsell you discover you need after your ad costs creep up. If you are building or moving a site that is going to carry paid traffic, it is worth trying that stack under your own landing page before your next campaign, rather than after you have already noticed the cost per click creeping up.

Conclusion

Check your own landing page before you touch your next bid. A page that loads properly on a phone, on mobile data, is not a marketing nice-to-have. It is the difference between a click that becomes a customer and one that becomes a number on an invoice from Google with nothing to show for it. The fix is rarely the ad. It is usually the five seconds nobody timed.