4 ms·

For reference, we haven't spent any time trying to optimize the react website for perf. Also that front page really needs to be rethought, we haven't updated it

• spicyj 11y ago
  I'll add: the React site uses the (larger and slower) development build of React because it can be useful to people visiting the site. Ordinarily you would use the prod build. Not to mention the lack of script bundling and inefficient (blocking) loading. Just hasn't been a priority for us.
  • inian 11y ago
    Oh thats why the dev build of React was there in the page. Makes sense!
• Touche 11y ago
  > For reference, we haven't spent any time trying to optimize the react website for perf. That's probably true of every slow site on the web. Part of the purpose of AMP is that it forces your site to be fast. Of course you can optimize a regular HTML page and make it faster, but you can't pass AMP validation with a slow site.
• ageitgey 11y ago
  I randomly picked the React website as an example github-hosted page to compare with (it was one of the first google results for github-hosted pages). I definitely didn't mean to pick on you all in particular! I'm not suggesting you should have spent a bunch of dev time making the landing page for a developer tool really fast on mobile devices (and React is a great tool!). I updated my README file to compare page load speed with the Jekyll homepage too since it's a closer analog. But comparing to a random page that wasn't too optimized was sort of the point - most of the time, speed isn't the priority and that can make a big real-world difference for mobile users.