Simon Hearne • 7/11/2016

Blocking requests in webpagetest? Don't use Chrome.

This 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.

0 comments

#webpagetest #performance testing #Chrome Devtools