5 ms·

I'm a developer at GitHub. This is a really good writeup and touches on many of the frontend issues we've had our eye on for a while. In fact, the <script> rel

I'm a developer at GitHub. This is a really good writeup and touches on many of the frontend issues we've had our eye on for a while. In fact, the <script> related bits are already dated. We've just rolled out defer support for these for instance. I really liked the wrap up section on choosing which aspects of performance to concentrate on and can maybe answer some questions here: > Yet, I am wondering what would be the performance business > case for GitHub? Even if GitHub does not feel slow, faster > is always better. We want GitHub to be insanely fast and are pouring a significant amount of time and energy into this. We think it's more important than a lot of feature-type additions we also have planned. (I also left a similar comment on JP's blog that's waiting for moderation.)

xpose2000 14y ago
In reference to the Gravatar icons in the post. You guys are always asking for the 140x140 sized icons and they are then re-sized to 20x20 or 30x30. You have the ability to ask for the gravatar icons in your specified format, which will save a lot of bandwidth. https://secure.gravatar.com/avatar/e7e8748f7897c2d9a3da0afe4deb6d14?s=140 https://secure.gravatar.com/avatar/e7e8748f7897c2d9a3da0afe4... 32kb vs https://secure.gravatar.com/avatar/e7e8748f7897c2d9a3da0afe4deb6d14?s=30 https://secure.gravatar.com/avatar/e7e8748f7897c2d9a3da0afe4... 2.71kb Making this one change alone will make a huge difference.
- jphpsf 14y ago
  That is a great tip. Thank you! I just mentioned it in the comment thread of the blog post. JP