Display Ads and Page Speed: Keep Revenue Without Slow Pages

Short answer: Display ads slow a page because each ad slot loads scripts from several outside companies, which then fetch images or videos and often shift the layout while doing so. You can keep the income and still limit the damage by reserving space for each slot, loading ads below the first screen later, using fewer slots and partners, and measuring the page with ads on and off to see what they really cost.

Why ads are so heavy

An ad slot is not a simple image. When a page loads, an ad script starts an auction or a request chain: it contacts the ad network, which may contact several buyers, which then return the winning creative and tracking code. That creative can be a large image, an animated file or even a video, and it may bring its own scripts.

Multiply this by several slots on one page, and the browser is busy with outside code long after your own content has arrived. This is the same problem we describe in our article on third-party scripts and performance, but with ads the effect is larger because the content changes each time the page loads, so you cannot tune it once and forget it.

There is another effect that is easy to miss. Ads are chosen at the moment the page loads, so two visits to the same page can behave very differently. One visitor gets a small static image, and the next gets a heavy animated creative that fills the network for several seconds. This variation is why a single speed test on an ad page can be misleading, and why repeated tests give a more honest picture.

Which speed measures ads damage

Ads affect more than one metric, and the biggest damage is often to stability and responsiveness, not to raw loading time. Three measures matter most:

Layout shift. An ad that arrives late and pushes the text down makes the page jump, which hurts the score described in our guide to fixing cumulative layout shift.
Responsiveness. Heavy ad scripts occupy the main thread, so taps and clicks feel slow. See our article on interaction to next paint.
Loading of the main content. If ad requests compete with your images and text for bandwidth, the largest element appears later.

Together these shape how a visitor experiences the page, especially on a mid-range phone with a mobile connection.

Reserve space for every ad slot

The single most effective fix is to give each slot a fixed size in the layout before the ad arrives. If you reserve a container of the right height, the text does not move when the ad loads, and the layout shift score improves right away. Ad networks offer several sizes for a slot, so choose the most common size and set the container to match, or set a minimum height that fits the largest likely ad.

A reserved empty space may look odd when no ad is shown, but a quiet gap is better than a page that jumps while somebody reads. A neutral background or a small label such as the word advertisement makes the gap look intentional. Do the same for sticky ads and ads inside the text: decide the space first, and let the ad fill it.

Test the layout on different screen widths, because ad sizes change between mobile and desktop. A container reserved for a tall desktop ad will leave an ugly gap on a phone, while a small container will cause a jump when a larger ad arrives. Set reserved heights separately for each breakpoint, and check them again whenever you add a new ad format.

Load ads later, not first

Ads below the first screen do not need to load before the visitor sees your content. Most ad platforms support lazy loading of slots, which means the ad is requested only when the visitor scrolls near it. This saves bandwidth for the content that matters and cuts the number of early requests. It also reduces wasted requests for slots that nobody scrolls to.

The same idea applies to ad code itself. Load the main ad script with the async attribute so that it does not block the page, and use the techniques in our guide to preload, preconnect and prefetch to warm up connections to the ad network only where it helps. Keep the first screen light so that the visitor sees something useful right away.

Use fewer slots and fewer partners

More ads do not always mean more income. A page with eight slots may earn little more than one with four, while loading much slower and driving visitors away. Test with fewer slots and watch the effect on both income and engagement. Place the remaining ads where they are most visible and least disruptive, usually beside or between paragraphs, not on top of the main content.

The same applies to ad partners. Every extra network adds scripts and requests. Consolidating to fewer partners, or using a single management platform, often reduces load without a meaningful loss. Avoid ads that auto-play video with sound, ads that refresh every few seconds and overlays that cover the page. They damage both speed and trust, and several of them break the rules of ad platforms and the policies of browsers.

Look at how ads are placed on mobile in particular. A layout with an ad after every second paragraph may be acceptable on a wide screen but turns a small screen into a stream of adverts with a little text between them. Visitors notice quickly, and they leave. Fewer, better placed slots on mobile are usually the wiser choice, even if the number of impressions per visit drops.

Consent banners and tracking

In many regions, ads that use personal data require visitor consent, and the consent banner is itself a script and a layout element. A banner that loads late and pushes the page down is another common cause of layout shift, and a heavy consent tool can slow the page before any ad appears. Our article on cookie consent banners and page speed shows how to keep that part light.

Also review the tag manager. Ad and tracking tags are frequently added through it, and old tags are rarely removed. A clean-up often removes scripts that no longer serve any purpose, as described in our guide to Google Tag Manager and page speed.

How to measure what ads really cost

Do not guess. Measure the same page twice, once with ads and once without. Many ad platforms or your own test settings allow you to switch them off for a test visit, or you can compare with a similar page that has no ads. Look at the loading time of the main content, layout shift and the time the browser spends running scripts. Our guide to total blocking time explains the last measure.

Then compare the cost to the income. If the ads on a page bring a small amount but cost a large share of speed, they are a poor deal. If they earn well and the damage is modest, keep them and focus on the fixes above. Check from time to time, because ad code changes without notice and a page that was fine last quarter may have slipped.

Balancing income and visitors

Speed affects the very thing ads depend on: visitors who stay, scroll and return. A slow, jumpy page earns fewer views per visit and fewer returning readers, and in many cases the lost traffic costs more than the saved space earns. Our article on how speed affects sales and conversions shows the link between speed and results.

Set a simple budget. Decide how many slots a page type may have and what its loading time and layout shift should be, and treat a breach like any other bug. This keeps the discussion practical and prevents slow creep as new partners and formats are added.

How Site AI Audit helps

Site AI Audit’s speed results include the Google PageSpeed score, LCP, CLS and INP, server response time and the compression and weight of your pages. Run it on a page with ads to see how the layout shift and loading figures look, and run it again after you reserve space or remove a partner. It does not manage your ad setup or report revenue, but it shows whether the changes help. You can run a free check of your website or see the plans.

The bottom line

Ads and speed do not have to be enemies. Reserve space for every slot, load lower ads later, keep the number of slots and partners modest, tidy your consent and tag setup and measure with ads on and off. Treat speed as part of the income plan, because the visitors who stay are the ones who see the ads.

FAQ

Do ads hurt my search rankings?

Ads themselves are not a penalty, but slow loading, layout shifts and intrusive formats can hurt the experience that search engines measure.

How do I stop ads from moving my text?

Give every ad slot a fixed container size in your layout, so the space is reserved before the ad arrives.

Should all ads load lazily?

Ads below the first screen can. The first slot may need to load early to be seen, so test the effect on both speed and income.

Is it better to have fewer ad slots?

Often yes. Extra slots can add load and drive visitors away without adding much income. Test a smaller number and compare.

How can I test the speed cost of ads?

Measure the same page with and without ads, and compare layout shift, loading of the main content and script time.