3 ms·

That article gets a score of 15% on Google PageSpeed - https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.theverge.com%2F2015%2F7%2F

• omouse 11y ago
  Still loads faster than The Verge ;)
  • EdiX 11y ago
    It's The Verge's article that gets 15%, OP gets 63% (faster than The Verge, obviously).
    • lmorchard 11y ago
      Huh. Interesting that mine is so bad. The PageSpeed report is fair, though. I didn't optimize images, set expires headers, etc. Weird that Amazon isn't serving things up gzip'd - oh, interesting, I have to gzip the stuff in my build script and deploy it compressed.
• ubernostrum 11y ago
  PageSpeed is... a mixed bag. It likes to yell at me that my font size is too small, and tell me to "set a legible font size". When I'm not actually setting a base font size and instead adjusting things relative to the browser's default. Their recommendation to "fix" this is to specify absolute font sizes, which is the opposite of basically every accessibility requirement I've ever read. Similarly, they complain that I'm not "leveraging browser caching" -- but the un-cached resource is the Google Analytics JavaScript. It also doesn't catch the one actual user-experience-problem bug that I know about and am working to fix. So while it's enjoyable to poke fun at someone through PageSpeed results, I'd take it with an extremely large grain of salt.