Google Ads TTFB: why ad clicks wait longer
Ad clicks wait longer for the first byte for two reasons. Either the click takes an extra hop, or the query string misses your cache.
Why are visitors from Google Ads slower?
In short
- Visitors from Google Ads and campaign links get a slower first byte for two reasons: a redirect on the way to the landing page, or a cache miss caused by tracking parameters such as gclid and utm_source.
- The parts of Time to First Byte tell the two apart: time before the browser sends the page request points to the click path, a slow answer from the server points to a cache miss.
- Point each ad straight at the final landing URL, and let your CDN and page cache ignore tracking parameters instead of redirecting them away, so conversion tags still read the click ID.
One ad click can hit both at once: the visitor arrives cold from another host, often through a tracking hop, on an address with a query string your cache has never seen.
Time to First Byte (TTFB) is judged at the 75th percentile (p75): 800 ms or less is good. On a page where ads bring most landings, slow ad clicks push it past that line while everyone else gets a fast answer.
Is it the ad click redirect or a cache miss?
Two TTFB sub-phases tell a click redirect from a cache miss. A high Waiting + Redirect means the extra time came before the browser sent the request for your page: a redirect hop or browser start-up. Request goes up when your CDN or server takes longer to return the HTML, usually because the query string missed the cache.
The "TTFB sub-phases" card in CoreDash shows all five parts against their good lines. Worker & Cache there is only the browser's own cache; a miss in your CDN or page cache lands in Request.
Across 57 CoreDash sites, on full page loads from outside in the 28 days to 22 November 2026, Google Ads clicks (942,814 page views) had a Waiting + Redirect p75 of 306 ms against 25 ms without a query parameter (1,293,527). Their Request was lower: 425 against 545 ms. Other campaign links, with utm_ and no click ID, look the same (502 against 20 ms, 54 sites). Other query parameters differ in Request: 651 ms against 468 ms (58 sites). These splits mix different pages, phones and networks, so that is a correlation; the next step compares one URL.
When Waiting + Redirect is furthest over its good line and few visits redirected on your own site, the card's verdict puts your slowest campaign group next to visits without a query parameter, with Request beside it.
435 ms+385 ms
21 ms
56 ms+6 ms
148 ms
144 ms
How do I compare campaign visits with other visits fairly?
Compare campaign visits only with other full page loads from outside your site, on the same URL, without a query parameter. An ad click is always a cold page load from outside, while the rest of your traffic includes clicks within the site, reloads and back button visits that reuse a connection or come from memory.
The Campaign list in the "Arrival" card on CoreDash's TTFB page does that filtering. It keeps only Navigation type "Page load" with Navigation origin "From outside", puts gclid, gad_source, gad_campaignid, gbraid and wbraid under "Google Ads click" and utm_ links without a click ID under "Other campaign", and compares each with "No query parameter".
172,089 page views · 89,500 over 0.80 s1.20 s
69,497 page views · 4,170 over 0.80 s0.30 s
26,475 page views · 3,180 over 0.80 s0.61 s
6,619 page views · 660 over 0.80 s0.52 s
26,260 page views · 1,580 over 0.80 s0.39 s
30,000 page views · 1,500 over 0.80 s0.36 s
For one landing page, pick it in the URL tab and read Campaign and the sub-phases for that page alone. Across 47 CoreDash sites and 186 URLs in the same 28 days (136,621 Google Ads clicks against 113,138 page loads without a parameter), Google Ads clicks had a higher TTFB on 65% of URLs. The median difference per URL was +80 ms on TTFB, +47 ms on Waiting + Redirect and +11 ms on Request.
Came here from a "Slow campaign parameters" issue? It opens when a marketing parameter's TTFB on one device is over 800 ms and at least 1.5 times the TTFB without query parameters. That baseline is every page view without a parameter, so its gap is wider than one landing page against another; pick the landing URL for the fair comparison.
Why does my redirect count say 0 when the click redirected?
The browser's redirectCount is 0 whenever any hop in the chain is on a different origin (scheme, host or port) from the final page. An ad click tracker, a link shortener and even your own http to https or example.com to www.example.com redirect all leave it at 0. Their time still lands in Waiting + Redirect.
CoreDash shows that counter as "Same-site redirects". Across the same 57 sites, 896,179 of 942,814 Google Ads clicks (95%) had "No redirect", with a Waiting + Redirect p75 of 280 ms against 22 ms for visits without a parameter or a redirect. Read Waiting + Redirect, never the count on its own.
How do I shorten the click path before the request?
Make the final URL of every ad and campaign link the exact address of the landing page: https, the right www or bare host and the trailing slash your server wants. Then your own domain adds no redirect.
That starts in the ads account (ask whoever runs your Google Ads): check each Final URL, put landing page parameters in Final URL suffix and a third-party tracker in Tracking template. Parallel tracking then sends the browser straight to your page and counts the click in the background. It is required for Search, Shopping, Display, Video and Performance Max; on Hotel campaigns you switch it on in the account settings.
Next come the newsletters, social bios and partner links (ask whoever sends the mailings). A mail tool's click tracking and a link shortener add a hop on another host on every click, so keep them only where the campaign needs those click counts.
A developer sees every hop with curl -sIL on the exact URL from the ad or the mail:
curl -sIL "http://example.com/landing-page?gclid=test" | grep -iE "^(http/|location:)"
Each location line is a hop the browser waits through; point the Final URL at the last one. A hop owned by an ad platform or mail tool you can't switch off is out of your server's hands: measure it in Waiting + Redirect per Campaign group and decide with marketing whether that tracker is worth the wait. Redirect caching and HSTS are in waiting duration and redirects on corewebvitals.io.
How do I make the cache ignore gclid and utm parameters without breaking ad tracking?
Let your CDN and page cache ignore tracking parameters in the cache key, or strip them between the CDN and your origin, and leave the address in the browser as it is. Every ad click then gets the stored HTML, and the tags still read gclid and utm_ from window.location.
By default the query string is part of the cache key, or the page cache skips the page, and auto-tagging adds a new gclid to every click (wbraid or gbraid on some iOS visits), so each click is a miss that ends up in Request.
Without code, turn on the setting that ignores marketing parameters, or ask your host. WP Rocket ignores the Google Ads, standard utm_, fbclid and msclkid parameters by default, as long as every parameter on the URL is on its list. LiteSpeed Cache (on LiteSpeed Enterprise) drops fbclid, gclid, utm* and _ga under Cache, Drop Query String; add gad*, gbraid, wbraid and msclkid there. Cloudflare APO's list leaves out gad_source, gad_campaignid, gbraid and wbraid. Cache key rules per parameter need Cloudflare Enterprise, so on Free, Pro and Business a Transform Rule (Rewrite URL, Dynamic query) strips the parameters at the edge before the cache lookup, in one line:
remove_query_args(http.request.uri.query, "gclid", "gbraid", "wbraid", "gad_source", "gad_campaignid", "fbclid", "msclkid", "utm_source", "utm_medium", "utm_campaign", "utm_term", "utm_content", "utm_id")
The rewrite happens only inside the edge request, so the address bar keeps its query string for gtag.js and Google Tag Manager.
The workaround people try first is a 301 or 302 that strips gclid and utm_ from the address. I always strip campaign parameters at the edge or in the cache key, never with a redirect in the browser: that redirect adds a hop to every click and removes the click ID before the Google tag runs, so conversions lose their click. Keep search, filter, language, session and cart parameters in the key so one visitor's page is never served to the next. The full rule and a Cloudflare Worker are in stripping tracking parameters at the Cloudflare edge.
How do I check a campaign URL with curl?
Run curl -sI twice on the clean landing URL, so the second answer hits the cache, then once with a brand-new gclid value. When that third answer is also a HIT, with no location header, your cache ignores the click ID.
URL="https://www.example.com/landing-page/"
curl -sI "$URL" | grep -iE "^(http/|cf-cache-status:|x-cache:|x-litespeed-cache:|age:|location:|no-vary-search:)"
curl -sI "$URL" | grep -iE "^(http/|cf-cache-status:|x-cache:|x-litespeed-cache:|age:|location:|no-vary-search:)"
curl -sI "${URL}?gclid=test-$(date +%s)&gad_source=1" | grep -iE "^(http/|cf-cache-status:|x-cache:|x-litespeed-cache:|age:|location:|no-vary-search:)"
Use a fresh value every time (the extra gad_source=1 tests the parameter APO leaves out): a fixed ?gclid=test is a HIT on its second run even when every real click misses. What the second and third answers mean:
- HIT, often with an age header: cached HTML. A HIT on both means the cache key ignores the tracking parameters.
- MISS on the third: the query string is still in the cache key, so every new click ID goes to your origin.
- DYNAMIC or BYPASS: on Cloudflare, HTML isn't cached at the edge for that URL, or a header such as Cache-Control: private or Set-Cookie stopped it. A page cache can still answer behind it (x-litespeed-cache, x-cache, or WP Rocket's comment at the bottom of the HTML).
- location: the address redirected before any cache lookup. Test the exact Final URL from the ad.
A No-Vary-Search: params=("gclid" "gad_source" "gad_campaignid" "wbraid" "gbraid" "utm_source" "utm_medium" "utm_campaign") response header tells browsers which parameters leave the page unchanged. Chrome, Edge and Firefox reuse their HTTP cache with it and Safari doesn't, but no major CDN reads it, so it never speeds up the first cold ad click.
Once a new gclid is a HIT, watch Request on "Google Ads click" in the Campaign list over the next 7 days.
What about query parameters that change the page?
Parameters that change the HTML stay in the cache key: site search (?q= or ?s=), filters (?color=), sorting (?sort=) and pagination (?page=). Drop them and the next visitor gets the first shopper's results.
In CoreDash these landings sit under "Other query parameter", their extra time shows in Request, and a slow one opens a "Slow query parameter" issue. Without code, add public filter and pagination parameters to WP Rocket's Cache Query String(s), or mark those pages eligible in a Cloudflare Cache Rule; cart, session and logged-in pages stay out of shared caches. A developer can cache them per query string at the edge for ten minutes:
Cache-Control: public, max-age=0, s-maxage=600, stale-while-revalidate=60
The slow query behind them and Server-Timing are in request duration and slow server responses on corewebvitals.io.
The owner checks that every Final URL lands without a redirect and that the setting ignoring campaign parameters is on. The developer reads Waiting + Redirect against Request for one URL, strips only tracking parameters at the edge or in the cache key, and tests a fresh gclid with curl.
Without RUM, start with how to identify and fix slow TTFB on corewebvitals.io. The reference has Waiting + Redirect, Request, Campaign and Same-site redirects.
Sources: Time to First Byte (TTFB) (web.dev), Navigation Timing Level 2: redirectCount (W3C), About parallel tracking and About auto-tagging (Google Ads Help), Cache Keys and APO query parameters (Cloudflare), No-Vary-Search (MDN).