HTML5 ad performance preflight

Heavy Ad Intervention: why Chrome removes HTML5 ads and how to test before upload

Chrome unloads ads that use too much CPU or network before the viewer interacts with them. Learn the three thresholds, why a banner that runs fine on your workstation still gets removed, and how to measure the risk in every size before handoff.

The short version

The banner passes upload validation and looks fine on a developer workstation, but in the wild Chrome replaces it with a grey "Ad removed" box. Nothing in the ZIP is invalid - the creative simply costs too much to run. That only shows up when the ad is executed and measured, not when its files are inspected.

Real desktop capture: an 8-size campaign runs in a local browser, and the 300x1050 unit is grounded for sustained CPU use even though its static checks pass.

What Heavy Ad Intervention is

Since Chrome 85, the browser watches how much CPU and network each ad iframe consumes. If an ad crosses a limit before the viewer has clicked or tapped it, Chrome unloads the frame and shows an "Ad removed" placeholder in its place. The impression is spent, the creative is gone, and neither the ad server nor the upload validator reports an error.

The intervention is applied to the ad frame as a whole, including anything it loads inside nested frames. Once the viewer interacts with the ad, the limits no longer apply - which is why click-to-play video is safe and autoplaying video often is not.

The three thresholds

  • •Network: more than 4 MB transferred by the ad frame.
  • •Peak CPU: more than 15 seconds of main-thread time within any 30-second window.
  • •Total CPU: more than 60 seconds of main-thread time over the life of the ad.

Chrome deliberately adds some variability to these limits for privacy reasons, so a creative sitting just under a threshold is not safe. Treat the numbers as a budget to stay well inside, not a line to approach.

Why it passes on your machine and fails in production

  • •ZIP weight is not network usage. A 150 KB package can still pull video, fonts, libraries, or trackers at runtime, and those bytes count toward the 4 MB limit.
  • •CPU time depends on the device. An animation that costs a few seconds of main-thread time on a workstation can cost several times more on a mid-range phone or a busy laptop.
  • •Loops add up. An animation that never stops keeps accumulating CPU time for as long as the page stays open, so the 60-second total is eventually reached even by a modest creative.
  • •Platform validators inspect files. They check dimensions, click handling, and package contents - they do not run the ad long enough to measure its cost.

Common causes in HTML5 banners

  • •Infinite animation loops, or requestAnimationFrame callbacks that keep running after the last frame has been drawn.
  • •Full-canvas redraws on every frame when only a small region changes.
  • •Autoplaying or preloaded video and large image sequences.
  • •Blur, filter, and shadow effects animated across large layers.
  • •Timers that poll continuously, and third-party scripts that do work the creative does not need.
  • •Oversized sprite sheets and uncompressed assets loaded after the initial package.

How to check it by hand in Chrome

You can reproduce the intervention manually. Open chrome://flags, enable "Heavy Ad Intervention" and disable "Heavy Ad Privacy Mitigations" so the thresholds are applied exactly, then load the creative inside an iframe on a test page and leave it running without touching it. In DevTools, the Performance panel with CPU throttling shows main-thread time, and the Network panel shows the total transferred.

This works, but it is slow: one size at a time, at least a minute of waiting per run, and the result depends on remembering the same settings every time. On a campaign with eight sizes and several rounds of amends it rarely gets done.

How to bring a creative back under budget

  • •Stop the animation. End on a static frame after a fixed number of loops - most platforms already require animation to stop within 30 seconds.
  • •Cancel requestAnimationFrame and clear timers when nothing is changing on screen.
  • •Animate transform and opacity instead of layout properties and filters.
  • •Load video and other heavy assets only after the viewer interacts with the ad.
  • •Compress images, trim sprite sheets, and drop libraries used for a single effect.
  • •Re-measure after every change, under the same conditions, in every size.

What Ad-Preflight checks

  • ✓Main-thread time and long tasks while the creative runs
  • ✓Network requests and total download activity
  • ✓Runtime behavior under CPU throttling
  • ✓Visual and animation behavior at each ad size

What it cannot guarantee

  • !Chrome adds privacy-related variability to intervention thresholds
  • !The measurement is a risk signal, not a deterministic promise of intervention
  • !Publisher wrappers and descendant frames can change the final serving behavior

Run it in the desktop app or CLI

Designers and AdOps can drop a campaign folder into the desktop app and follow the visual report. If you work in a terminal or CI pipeline, the same checks are available through the CLI.

  1. 1.Run Deep Audit on each size rather than relying on a static ZIP size.
  2. 2.Review CPU and network findings in the report.
  3. 3.Reduce expensive loops, oversized resources, and unnecessary requests.
  4. 4.Re-run under the same audit conditions before handoff.

CLI equivalent

npx @ad-preflight/cli package ./my-ad --fix

Questions

What are heavy ads?
Chrome calls an ad "heavy" when its frame uses more than 4 MB of network, more than 15 seconds of main-thread CPU in any 30-second window, or more than 60 seconds of CPU in total, before the viewer interacts with it. Chrome then unloads the ad and shows an "Ad removed" box.
What are Heavy Ad privacy mitigations?
Chrome adds random noise to the thresholds so the moment an ad is removed cannot be used to measure a device. In practice a creative can be removed somewhat below the published limits. To test against the exact limits, disable "Heavy Ad Privacy Mitigations" in chrome://flags; to be safe in production, stay well under them.
Does Heavy Ad Intervention apply to every ad?
It applies to ad frames Chrome identifies as ads, including everything they load in nested frames, and only until the viewer clicks or taps the ad. Interaction lifts the limits.
Will the platform validator warn me about Heavy Ad risk?
No. Upload validators inspect the files. CPU and network use only exist while the ad runs, so they have to be measured by running the creative, which is what Deep Audit does for each size.
How do I enable Chrome's Heavy Ad Intervention for testing?
Open chrome://flags, enable "Heavy Ad Intervention" and disable "Heavy Ad Privacy Mitigations", restart Chrome, then load the creative in an iframe on a test page and leave it untouched for at least a minute. DevTools shows CPU in the Performance panel and bytes in the Network panel.

Still rejected? Send it to us

Send the rejection message and your free check result, and within 3 working days you get a written answer: what failed, on which platform, and the fix. No files, no call, no sign-up.

Send it to us

Platform reference: Chrome for Developers: handling Heavy Ad Interventions

Related guides