Blocking requests in webpagetest? Don't use Chrome.
Read OriginalThis technical article details a performance testing issue where Chrome inefficiently handles blocked third-party requests in WebPageTest, causing sequential requests and high CPU usage. It demonstrates the problem using a real website example, compares results with Firefox and Internet Explorer, and concludes that IE provides the most accurate visualization of third-party content's impact on page load performance.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
2
Using Browser Apis In React Practical Guide
Jivbcoop
•
2 votes
3
Better react-hook-form Smart Form Components
Maarten Hus
•
2 votes
4
Top picks — 2026 January
Paweł Grzybek
•
1 votes
5
In Praise of –dry-run
Henrik Warne
•
1 votes
6
Deep Learning is Powerful Because It Makes Hard Things Easy - Reflections 10 Years On
Ferenc Huszár
•
1 votes
7
Vibe coding your first iOS app
William Denniss
•
1 votes
8
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook
•
1 votes
9
Quoting Thariq Shihipar
Simon Willison
•
1 votes
10
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft
•
1 votes