Adding ads to a website looks simple: paste a script, drop a few banners, done. Then the page starts jumping while it loads, mobile visitors complain and search performance slips. The problem is rarely the ads themselves but how the ad zones are added. Done carefully, you can add ad zones to a website and keep Core Web Vitals in good shape.
This publishers' guide covers the metrics that matter, how to choose sizes such as 300x250 and 728x90, how lazy loading helps, and how to handle mobile layouts without hurting the reading experience.
Why ads can hurt Core Web Vitals
Google's Core Web Vitals measure real user experience with three main metrics. Ads can affect all three if they are added carelessly.

- Largest Contentful Paint (LCP): how fast the main content appears. Heavy ad scripts loaded early compete with your headline and hero image for bandwidth.
- Cumulative Layout Shift (CLS): how much the page moves while loading. An ad slot that appears without reserved space pushes text down, which is the most common ad-related issue.
- Interaction to Next Paint (INP): how quickly the page reacts to taps and clicks. Too many scripts running at once can make the page feel sluggish.
The good news: each problem has a well-known fix, and most of them are about layout and loading order rather than removing ads.
How to add ad zones to a website step by step
1. Plan placements before writing code
Decide where ads go based on how people read your pages. On an article page, a typical setup is one banner near the top, one unit inside the content and one at the end. Fewer, better-placed zones usually earn more than many slots nobody sees.
2. Load the ad script asynchronously
Ad scripts should never block rendering. Use the "async" or "defer" attribute, or load the script near the end of the page, so your content paints first. Most modern ad networks provide asynchronous tags by default; check before you install one.
3. Reserve space for every slot
This is the single most important step for CLS. Give each ad container a fixed minimum height that matches the expected ad size, so the layout does not move when the creative arrives. The web.dev guide to CLS recommends reserving space for ads for exactly this reason. If a slot sometimes stays empty, keep the reserved space or show a neutral placeholder rather than collapsing it suddenly.
4. Lazy load ads below the fold
Ads far down the page do not need to load when the page opens. Lazy loading, typically using the Intersection Observer API, requests the ad only when the reader scrolls close to it. This saves bandwidth, speeds up the first view and often improves viewability, since ads load when someone is actually there to see them.
5. Be careful with auto-refresh
Some networks let you rotate creatives every minute or so. If you use refresh, keep the slot size identical between rotations and avoid refreshing ads that are out of view.
Choosing ad sizes: 300x250, 728x90 and friends
Standard IAB sizes are supported by almost every advertiser and network, which helps fill rate. The most useful ones for publishers are:
| Size | Name | Best placement |
|---|---|---|
| 728x90 | Leaderboard | Top of page or between sections on desktop |
| 300x250 | Medium rectangle | Inside article content, sidebar; works on mobile too |
| 300x600 | Half page | Desktop sidebar, especially sticky |
| 160x600 | Wide skyscraper | Narrow desktop sidebars |
| 320x50 | Mobile banner | Top or bottom of mobile pages |
| 468x60 | Full banner | Older layouts, between content blocks |
The 300x250 rectangle is the most flexible choice because it fits both desktop and mobile layouts. A 728x90 leaderboard is too wide for phones, so pair it with a 320x50 or 300x250 on smaller screens.
Mobile first: keeping phone readers happy
On many sites most visits come from phones, and that is where badly placed ads hurt most.
- Swap sizes by screen width. Use CSS media queries or responsive zones so desktop units are not squeezed onto small screens.
- Keep ads out of the first screen of text. Let readers see the headline and opening paragraph before the first in-content unit.
- Leave breathing room. Space ads away from buttons and links to avoid accidental clicks, which annoy readers and advertisers alike.
- Avoid intrusive formats. Full-screen interstitials and popups that cover content create a poor experience on mobile.
- Test on a real device. Desktop emulation is useful, but a mid-range phone on mobile data shows the real picture.
Picking a network that respects page speed
Your setup can only be as light as the ad code you install. Before choosing a network, check the size of its script, whether it loads asynchronously and whether it supports the sizes you need. Some crypto-focused networks are built with this in mind. The integration described on affizy.com, for example, uses one asynchronous script plus a div for each ad zone, supports standard IAB sizes and offers adaptive zones in which the server picks a suitable size per request, with optional creative refresh.
Whichever network you choose, measure before and after installing it. Run Lighthouse or PageSpeed Insights on a few key pages, then check field data over the following weeks to confirm real users are not affected.
FAQ
Do ads always lower Core Web Vitals scores?
No. Ads add some weight, but with asynchronous loading, reserved space and lazy loading, many sites keep good scores. Layout shift from unreserved ad slots is the most common problem and is also the easiest to fix.
Which ad size should I start with?
The 300x250 medium rectangle is a safe first choice because it works on desktop and mobile and is widely supported by advertisers.
Should I lazy load every ad?
Lazy load ads below the fold. An ad at the very top of the page is usually visible immediately, so loading it normally, with reserved space, makes more sense.
Conclusion
To add ad zones to a website without hurting UX, plan placements first, load scripts asynchronously, reserve space for every slot, lazy load lower units and adapt sizes for mobile. Then measure. A few well-built zones can bring revenue while your pages stay fast and readable.