4 ms·
WashingtonPost.com serves many ads and consumes too much memory resources - thanks for crashing my Safari (iPad) while reading the article, a very unnerving mom
by frik 11y ago
WashingtonPost.com serves many ads and consumes too much memory resources - thanks for crashing my Safari (iPad) while reading the article, a very unnerving moment.
I still have no Safari adblocker installed, as I believe in ads. But such bad ads citizens needs a disruption ala Google text-based Ads 10 years ago that changed the ads landscape.
- Symbiote 11y agoGhostery counts 16 things to block on the article's page, and without it I was shown two large, animated adverts.
- frik 11y agoGhostery found: Amazon Associates (Advertising, Affiliate Marketing) ChartBeat (Analytics) Criteo (Advertising, Search) DoubleClick (Advertising) Effective Measure (Analytics, Analytics) Krux Digital (Beacons) MediaMath (Advertising) Moat (Advertising) Omniture - Adobe Analytics (Beacons) OpenX (Advertising) Outbrain (Widgets) Polar Mobile (Advertising) Sailthru Horizon (Beacons) ScoreCard Research Beacon (Beacons, Analytics) Twitter Button (Widgets, Social) Way too much "Analytics" in the list. 116 requests; onload: 7.77s Chrome DevTools timing said: 2.71s Scripting; 636ms Rendering; 210ms Painting Dozens of reflows are visible in the flame graph! Poor mobile devices, such websites eat battery like there's no tomorrow. Summary: One hell of a page.