Ads on news sites crash your computer because they run too many scripts at once, consume excessive memory, and compete with your browser for processing power
When you load a news article, you are not just loading text and images from one source. You are loading code from the news site itself, plus ads from multiple ad networks, plus tracking pixels, plus video players, plus social media widgets. Each of these runs its own scripts — small programs that execute in your browser. A single page can load 50 to 100 separate scripts. Your browser has to parse, compile, and run all of them simultaneously.
The ads themselves are often the heaviest offenders. Ad networks like Google's DoubleClick, Criteo, and others serve ads that include video, animations, and real-time bidding code. Real-time bidding means your browser is running an auction in the background every time you load a page — sending your data to multiple ad exchanges and waiting for bids to come back. This happens invisibly and uses CPU cycles and memory. If your computer is older or you have limited RAM, the browser runs out of memory and crashes or freezes.
News sites stack multiple ad slots on a single page — a banner at the top, a sidebar ad, an ad between paragraphs, an ad at the bottom. Each slot loads its own ad network code. If one ad network is slow to respond, your entire page load slows down while the browser waits for that ad to arrive. If the ad server is overloaded or unreliable, the browser can hang indefinitely.
Key Takeaways
- Each ad on a news page loads code from a separate ad network, and your browser must run all of these scripts at the same time, which consumes memory and processing power.
- Real-time bidding — the system that auctions your ad impression to the highest bidder — runs invisibly in the background and uses CPU cycles even though you never see the auction happen.
- Older computers and browsers with less than 4 GB of RAM are most vulnerable to crashes because they run out of memory when dozens of scripts compete for space.
- Ads that include video, animations, or auto-play content use significantly more resources than static image ads and are more likely to cause slowdowns.
- Blocking ads or using a reader mode reduces the number of scripts your browser has to run and often stops crashes and freezes.
How ad networks compete for your browser's resources
Ad networks do not coordinate with each other. When you visit a news page, each ad network independently decides to load its code, fetch an ad, and track your behavior. They are all running at the same time. Your browser has a single thread for executing JavaScript on most pages — meaning it processes one instruction at a time, very quickly, but still one at a time. When 50 scripts are waiting to run, the browser queues them up. If one script is slow or stuck in a loop, everything behind it waits.
The problem compounds when ad networks use third-party trackers. An ad from Network A might load a tracker from Company B, which loads a tracker from Company C. Each tracker adds another layer of code and another network request. A single ad slot can trigger 10 to 20 separate HTTP requests. On a page with five ad slots, that is 50 to 100 requests happening at once. Your browser has to manage all of them, and your internet connection has a limit on how many simultaneous connections it can handle.
Some ad networks use what is called "lazy loading" — they wait until you scroll near an ad before loading it. This reduces the initial page load time but means ads load continuously as you read. Others load all ads when ready, which slows down the initial page load but stops once the page is fully loaded. Neither approach is inherently better; both can cause problems depending on your hardware and connection speed.
Why video ads and auto-play content cause the worst crashes
Video ads are exponentially more resource-intensive than image ads. A static image ad is a single file — maybe 50 to 200 kilobytes. A video ad is a video file plus a video player plus autoplay code. The video player alone can be 200 to 500 kilobytes of JavaScript. If the video autoplays, your browser has to decode video frames in real time, which requires significant CPU power. On a page with two or three autoplaying video ads, your CPU usage can spike to 80 or 90 percent.
Auto-play ads are particularly problematic because they start playing whether you want them to or not. Your browser does not know you are not watching the video — it plays it anyway, consuming bandwidth and CPU. If you have a slow internet connection, the video player will buffer, which means it pauses and waits for more data to arrive. While buffering, the player is still running and consuming resources.
Some news sites load video ads that are not visible on your screen. You scroll past them without ever seeing them, but your browser is still decoding and playing them in the background. This is called off-screen rendering, and it wastes resources on content you will never watch.
Memory leaks and ads that never stop running
A memory leak is a bug in code where a program allocates memory but never releases it. Over time, the program uses more and more memory until the computer runs out. Some ad networks have memory leaks in their code. When you load a page with one of these ads, the ad loads, runs, and should stop using memory when it is done. Instead, it keeps holding onto memory. If you stay on the page for 10 minutes, the ad might be using 50 to 100 megabytes of memory even though you are not interacting with it.
Certain ads also use infinite loops or timers that never stop. A timer is a piece of code that runs repeatedly at set intervals — for example, every 100 milliseconds. Some ad code sets up a timer to check for user interaction or to refresh the ad, but the code that stops the timer never runs. The timer keeps firing forever, consuming CPU cycles continuously.
Browser developers have added tools to detect and stop some of these problems. Modern versions of Chrome, Firefox, and Safari can detect when a script is using excessive CPU and will warn you or stop the script. Older browsers do not have these protections, which is why older computers crash more often on ad-heavy pages.
How your browser version and computer hardware affect crashes
A browser crash happens when your browser runs out of memory or encounters an error it cannot recover from. The amount of memory available depends on your operating system, how much RAM your computer has, and what other programs are running. If you have 2 GB of RAM and you are running Windows, Outlook, Slack, and Chrome with 10 tabs open, you might have only 500 MB of RAM available for the browser. A news page with 100 scripts and multiple video ads can easily use 300 to 500 MB, leaving almost nothing for the browser itself to function.
Older browsers like Internet Explorer 11 or older versions of Chrome are less efficient at managing memory. They do not garbage-collect — clean up unused memory — as aggressively as modern browsers. A page that runs fine in Chrome 120 might crash in Chrome 90 on the same computer.
Mobile browsers have even less memory than desktop browsers. A smartphone might have 2 to 4 GB of RAM total, and the browser gets only a fraction of that. News sites often serve the same ads to mobile and desktop, which means mobile users experience crashes more frequently. Some news sites detect mobile traffic and serve a lighter version of the page with fewer ads, but many do not.
What happens when your browser runs out of memory
When your browser runs out of memory, one of several things happens. The most common outcome is that the browser becomes unresponsive — you click, type, or scroll, but nothing happens for several seconds. The browser is using all available CPU to manage memory or process scripts, and it cannot respond to your input. Eventually, the operating system detects that the browser is not responding and offers to close it. You lose your place on the page and any unsaved text you were typing.
In some cases, the browser crashes completely and closes without warning. On Windows, you might see an error message. On Mac or Linux, the browser straightforward quits. If you have not saved your work, it is lost.
A third outcome is that the page becomes extremely slow. The browser is still running, but it is so busy managing memory and running scripts that page interactions take 5 to 10 seconds to register. Scrolling becomes jerky. Clicking a link takes 30 seconds to navigate to the next page. This is often worse than a crash because you are stuck waiting.
How to stop ads from crashing your browser
The most direct solution is to use an ad blocker. Ad blockers like uBlock Origin, Adblock Plus, or built-in browser features like Firefox's Enhanced Tracking Protection prevent ads and trackers from loading. Without the ad code running, your browser uses 30 to 50 percent less memory and CPU. Pages load faster and crashes stop. The trade-off is that news sites lose ad revenue, which is why many sites ask you to disable your ad blocker or show you a paywall.
If you do not want to block ads entirely, you can use a content blocker that stops only video ads or only tracking scripts. uBlock Origin lets you create custom filters. You can block all video players, or all scripts from specific ad networks, or all autoplaying content. This gives you more control than a blanket ad blocker.
Reader mode, available in Firefox, Safari, and some other browsers, strips out ads, scripts, and formatting and shows you only the article text. This is the most aggressive approach and stops almost all crashes, but you lose images and formatting. Most news sites work fine in reader mode.
If you want to keep ads enabled, upgrade your browser to the latest version and make sure your operating system is up to date. Newer versions are more efficient at memory management. Close other programs before reading news sites. If you have fewer than 4 GB of RAM, consider upgrading — 8 GB is standard now and costs less than $50 for a RAM stick.
Why news sites allow so many ads
News sites allow multiple ad networks because each network pays differently depending on the type of ad and the user. A news site might use Google AdSense for baseline revenue, Criteo for retargeting ads that follow you around the internet, and a direct sales team that sells ads to specific advertisers. By stacking multiple networks, the site maximizes revenue from each page view. The cost is paid by readers in the form of crashes, slowdowns, and data usage.
Some news sites are aware of the problem and have started limiting ads or using server-side ad insertion, which loads ads on the news site's server instead of in your browser. This reduces the number of scripts your browser has to run. But most news sites have not made this change because it requires investment and reduces flexibility in ad serving.
Frequently Asked Questions
Can a news site ad actually crash my entire computer, or just the browser?
Ad code runs inside your browser, not at the operating system level, so it can only crash the browser itself. However, if the browser uses so much memory that your operating system runs out of virtual memory, your entire computer can slow down or freeze. This is rare on modern computers but more common on older machines with limited RAM.
Why do some news sites crash my browser and others do not?
Different news sites use different numbers of ad networks and different types of ads. A site with five ad slots using video ads will crash more often than a site with two ad slots using static image ads. Sites owned by large publishers like CNN or The New York Times often have more aggressive ad strategies than smaller local news sites.
Does using a VPN or proxy slow down news sites more?
A VPN adds a small amount of latency — delay — to your connection, which can make pages load slightly slower. But it does not increase the number of scripts or ads your browser has to run. If a page crashes with a VPN, it would likely crash without one too. The VPN is not the cause.
Will clearing my browser cache stop the crashes?
Clearing your cache removes stored copies of images and scripts, which frees up disk space but does not affect memory usage while you are browsing. It might help slightly if your cache is extremely large, but it is not a reliable fix. Restarting your browser or closing other programs is more effective.
Is it safe to use an ad blocker on news sites?
Ad blockers are safe — they do not damage your browser or computer. The only risk is that some news sites will refuse to let you read articles if you have an ad blocker enabled. You can disable the ad blocker for specific sites you want to support, or you can use reader mode instead.