3 ms·

A new version of Windows Server doesn't address the problem of loading 64 JE files and 11 CSS files on every page. There is some programming ineptitude at play

• acdha 13y ago
  That's also a minor side issue: it'll cost you a sub-1-second page load time but it doesn't cause the kinds of problems people are talking about where the backend components are overloaded to the point of failure. The size of healthcare.gov is actually well under the average: http://www.webpagetest.org/result/131010_ZG_X5C/1/details/ http://www.webpagetest.org/result/131010_ZG_X5C/1/details/ (see http://www.webperformancetoday.com/2013/06/05/web-page-growth-2010-2013/ http://www.webperformancetoday.com/2013/06/05/web-page-growt...) For comparison, look at WashingtonPost.com: it uses considerably more data and more total requests and yet the page loads much faster: http://www.webpagetest.org/result/131010_GG_XDK/ http://www.webpagetest.org/result/131010_GG_XDK/ If you look carefully, though, you'll see a) that they aren't setting Cache-Control headers and are setting ETags (both performance killers) and b) there's this weird staggered response behaviour which indicates something is seriously wrong. It seems to handle much better in Chrome - 3s vs 70! - so presumably there's some interaction with the browser going on as well: http://www.webpagetest.org/result/131010_ZW_XD6/1/details/ http://www.webpagetest.org/result/131010_ZW_XD6/1/details/