- The average top 1,000 web page is 1575 KB.
- More than half of this page size is due to images.
- Flash is on the decrease. Custom fonts are on the increase.
Interestingly, CEO’s direct phone number is one of the options on the pricing page.
Echo is quite handy for web developers. On those pages that feature a lot of images, things can get slow and the server might get too much of an abuse (with more traffic thrown at it). One way to work around this is to only load those images that are in the visible part of the screen. Here is a demo of how it works. Just keep scrolling down and notice how by default you have a blank.gif image shown, with a standard loading indicator and a split second later you see the actual image which was supposed to be in there.
Simple, easy, elegant – and that’s how I like it.
I’ve praised GitHub many a time in posts on this blog and in numerous conversations over a pint. Today, I found yet another reason to do so – GitHub error pages. We’ve all seen a parallax 404 by now, right?
Today was the first time I looked into the source code of the page. It greets one with the following words right under the HTML 5 Doctype definition:
Hello future GitHubber! I bet you’re here to remove those nasty inline styles,
DRY up these templates and make ’em nice and re-usable, right?
Please, don’t. https://github.com/styleguide/templates/2.0
The link provides even more goodness. The list of other (all?) GitHub error templates is provided with explanation of which one fires when, as well as an insightful list of rules that GitHub uses for building error pages. Have a look:
If you’re visiting from the internet, feel free to learn from our style. This is a guide we use for our own apps internally at GitHub. We encourage you to set up one that works for your own team.
The following are banned from every error page:
<script>tags with an
<img>tags with an
srcpointing to a URL.
It’s things like that that keep me coming back and looking for more web development elegance all around GitHub.