How do ad stacks shape page experience, and what can a buyer read from it?
Part of MFA avoidance
The short answer
Ad scripts compete with a page's own content for network and processor time, and ads that load without reserved space push text around. Chrome's public field data shows the result as Core Web Vitals and, since September 2026, as experimental ad metrics. Buyers can read both as supporting evidence about ad load, never as proof of editorial quality.
Key takeaways
- Core Web Vitals measure loading, responsiveness and visual stability from real Chrome visits, judged at the 75th percentile separately for phone and desktop.
- Google's web.dev guidance names ads as one of the largest contributors to layout shifts on the web.
- Chrome published experimental ad metrics in September 2026: ad count, ad density, ad processor time and ad bytes, for origins with an authorized seller in ads.txt.
- A fast site can still be thin or templated, so page experience belongs beside content and traffic checks, not in place of them.
How do ads affect Core Web Vitals?
Google's Web Vitals guide (opens in a new tab) names three Core Web Vitals: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness, and Cumulative Layout Shift for visual stability. A page meets the good mark when LCP occurs within 2.5 seconds, INP is 200 milliseconds or less and CLS is 0.1 or less. The guide sets the bar at the 75th percentile of page loads, segmented across mobile and desktop, so one fast visit on office broadband proves little.
Ad code touches all three metrics: tags fetch scripts, auctions run in the browser, creatives download and iframes render. The adPerf study by Pourghassemi and colleagues, submitted to arXiv in February 2020, attributed more than 15 percent of page loading work in its sample to ads, mostly JavaScript. It is historical evidence for the mechanism, not a 2026 benchmark.
| Metric | Good threshold | How ad code can move it |
|---|---|---|
| Largest Contentful Paint | 2.5 seconds or less | Ad scripts and creatives compete with the article's own image and text for bandwidth; Google's ad tag guide warns that raising ad script priority may affect Core Web Vitals |
| Interaction to Next Paint | 200 milliseconds or less | Auction and creative JavaScript can keep the browser busy when a reader taps a menu or a link |
| Cumulative Layout Shift | 0.1 or less | Slots without reserved height push the text down when a creative arrives; collapsing an empty slot shifts it back up |
Why are ads singled out for layout shift?
Google's guide to optimizing CLS (opens in a new tab), updated February 7, 2025, states plainly that "Ads are one of the largest contributors to layout shifts on the web." The guide explains why: ad networks support dynamic sizes because more sizes bring more bids, and the publisher may not know the exact height of a creative until it arrives. It also warns that removing reserved space when no ad returns can cause as much shift as inserting content.
The guide says layout shift happens while a reader scrolls, when lazy loaded content arrives without reserved space, so a lab test that loads only the top of a page can miss it. It also notes that shifts near the top of the viewport tend to be larger, which makes a leaderboard above the headline on a phone the pattern to watch.
Can a buyer check a site's page experience?
Yes, from public data, without the publisher's analytics. The Chrome UX Report collects anonymized measurements from real Chrome users and, according to web.dev, powers PageSpeed Insights and Search Console's Core Web Vitals report. PageSpeed Insights (opens in a new tab) shows field data over the previous 28 day collection period next to a lab run in a controlled environment.
A page experience check for one candidate site
- Pick three article URLs, not the homepage. Articles carry the ad slots that buyers pay for, and a homepage can be lighter than the pages under it.
- Run each URL in PageSpeed Insights. Read the field section first and note whether it reports this URL or the whole origin; Google says PSI falls back to origin level data when a page lacks enough samples.
- Record the phone and desktop results separately. The Core Web Vitals assessment passes only when the 75th percentiles of all three metrics are good, so write down which metric failed.
- Open the origin in CrUX Vis and switch to the ads view. Chrome's experimental ad metrics appear there for eligible origins, alongside the vitals history.
- Save the date and the source of each figure. Field data rolls forward daily, so undated numbers cannot be rechecked.
What do Chrome's experimental ad metrics measure?
On September 15, 2026 Chrome published a set of CrUX ad metrics (opens in a new tab), described as experimental measurements of real users' ad experiences. The documentation says they cover a 28 day rolling window, are available in CrUX Vis, the CrUX API, the CrUX History API and the DevTools ad panel, and are not yet in the BigQuery dataset. Each metric is reported at the 75th percentile across page views.
| Metric | What Chrome measures | Unit | How a buyer can use it |
|---|---|---|---|
| Ad Count | The number of ads in the viewport, sampled once per second over the visit and averaged | Ads, to two decimals | A field check on how many units a reader faces at once |
| Ad Density | The share of the viewport covered by visible ads, sampled each second and averaged | Integer percentage | A field reading to set beside a manual ad density estimate |
| Ad Weight: CPU | JavaScript execution time consumed by ad frames and their subresources, excluding main frame ad scripts | Milliseconds | A clue to why INP or loading is poor on an otherwise simple page |
| Ad Weight: Network | Compressed bytes transferred to load all ad related resources over the page visit | Kilobytes | A clue to how much of a page's download is advertising |
Chrome's Ad Weight: CPU documentation (opens in a new tab) adds limits: only pages with ads are considered, origins without an authorized seller in ads.txt have no ad metrics data, and the metrics may evolve. Chrome publishes no thresholds for any of the four, so a buyer compares candidate sites with each other, not with a pass mark.
Why do slow pages signal ad heavy layouts?
A slow or unstable page is a symptom with several possible causes, and the ad stack is one that a buyer can isolate from outside. When a site's articles fail INP while its ad processor time is high, or fail CLS while the ad count is high, the ad layout becomes the first explanation worth testing. The trade groups' MFA definition (opens in a new tab) lists a high ad-to-content ratio and rapidly auto-refreshing placements among its five characteristics, and both of those add work to the page.
| Field symptom | Ad related reading | Other reading to rule out first |
|---|---|---|
| Poor CLS on phone only | Sticky or inline units without reserved height on narrow screens | A mobile template with unsized images |
| Poor INP with high ad CPU time | Auction and creative scripts busy when the reader taps | Heavy analytics or a chat widget |
| Good vitals, high ad count | A fast template carrying many small units | Ad count measures exposure, not speed, so both can be true |
Does a fast site mean a quality site?
No. Google Search says of page experience that "There is no single signal," and its page experience guidance (opens in a new tab), updated September 22, 2026, warns that good Core Web Vitals scores do not guarantee top rankings. The same logic applies to buying. A thin site built on a lean template can pass all three vitals, and the ANA's announcement states that MFA websites exhibit "high measurability rates, good viewability rates, low levels of invalid traffic". A site that publishes little can be fast.
Handle the bottom right quadrant with care. Local and independent newsrooms can run heavy ad loads on older templates and still publish original reporting. A poor vital there is a reason to review the layout, not to drop the site.
How should page experience be weighed in a site review?
Treat page experience as a supporting signal that raises or lowers confidence in other findings. It earns weight when it agrees with a manual visit, and less when field data is missing or covers only the origin. Google's self assessment asks whether content avoids "an excessive amount of ads that distract from or interfere with the main content," which keeps the reading tied to readers, not scores.
Page experience notes for a site review record
- Field data source recorded for each URL: page level, origin level or none.
- Phone and desktop results recorded separately, with the failing metric named.
- CrUX ad metrics recorded where Chrome reports them, with the check date.
- Any poor vital matched to a manual observation of the ad layout before it counts against the site.
- Missing field data noted as missing and never scored as a failure.
Fictional example
A record store's display plan in Louisiana and Mississippi
A fictional New Orleans retailer of vinyl records and turntables asks its agency for a display plan reaching readers in Louisiana and Mississippi, beside music reviews, local concert coverage and audio equipment guides. The planner has 30 candidate sites after a content review.
Field data exists for 21 of them. Two music blogs fail CLS on phones; on a manual visit both load a large unit above the headline with no reserved space, then a second unit in the first paragraph. Their ad counts in CrUX Vis are the highest in the set. Both go to review, and the planner asks the sellers whether a lighter layout is available in a deal.
A Baton Rouge arts weekly also fails INP, but its ad metrics are modest and the lab trace points to a ticketing widget, so it stays. The nine sites with no field data get a manual phone visit instead of a score.
How does PlacementGraph look at the ad layout before a site reaches a plan?
Frequently asked questions
Does Google use Core Web Vitals in search ranking?
Google Search says its ranking systems use Core Web Vitals and recommends good scores, but it also says good results in Search Console or other tools do not guarantee top rankings. For a buyer, what matters more is what the vitals reveal about how ads load on the articles a campaign would buy.
Why does PageSpeed Insights show origin data instead of page data?
Google's PageSpeed Insights documentation says that when a URL lacks enough field samples, the tool falls back to origin level data covering the whole site. An origin result blends the homepage, articles and all other pages, so it can hide an ad heavy article template or flatter it.
Are Lighthouse lab scores enough to judge a site's ads?
Not on their own. Google describes lab data as collected in a controlled environment and useful for debugging, while field data reflects how real visitors experienced a page over 28 days. A lab run may load before late ads, refresh or scroll triggered units appear, so it can miss what readers actually see.
Do Chrome's ad metrics cover sites without an ads.txt file?
No. Chrome's documentation says pages and origins without at least one authorized seller defined in an ads.txt file have no ad metrics data in CrUX, and that only pages with ads are considered. A missing ads.txt file is a separate question for the selling path review, not a page experience finding.
Sources
- Web Vitals (opens in a new tab)Google, web.dev (updated October 31, 2024)
- Optimize Cumulative Layout Shift (opens in a new tab)Google, web.dev (updated February 7, 2025)
- About PageSpeed Insights (opens in a new tab)Google for Developers (updated October 21, 2024)
- CrUX ad metrics (opens in a new tab)Chrome for Developers (published September 15, 2026)
- Ad Weight: CPU (opens in a new tab)Chrome for Developers (published September 15, 2026)
- Ad Count (opens in a new tab)Chrome for Developers (published September 15, 2026)
- Ad Weight: Network (opens in a new tab)Chrome for Developers (published September 15, 2026)
- CrUX methodology (opens in a new tab)Chrome for Developers (updated June 20, 2024)
- Understanding page experience in Google Search results (opens in a new tab)Google Search Central (updated September 22, 2026)
- General best practices (opens in a new tab)Google Publisher Tag documentation (updated October 6, 2026)
- adPerf: Characterizing the Performance of Third-party Ads (opens in a new tab)Pourghassemi, Bonecutter, Li and Chandramowlishwaran, arXiv (February 6, 2020)
- Leading Trade Groups Define Made For Advertising Websites (opens in a new tab)ANA (Association of National Advertisers), September 26, 2023
Researched and written by PlacementGraph Research. Read how we research, source and update these pages. Corrections: diana@placementgraph.com.