But is there a way to build pages with richer content while also achieving fast response times?
Here are some techniques for reducing the number of HTTP requests, while still supporting rich page designs.
If more than two people tell you that you’re being an asshole, consider that maybe you’re being an asshole.
That being said, it sucks to read shitty stuff about yourself so find an honest friend to read your criticism and tell you if it’s something worth listening to or if the critic is just a crazy fucking douche-canoe. Real bullies are complete assholes but they can’t recognize themselves as such so maybe spray paint an “x” on their forehead so that we can all just recognize them from a distance and ignore them.
Critics aren’t automatically bullies and you’re doing yourself a disservice if you ignore all of them out of hand.
It literally makes me want to stab you a little but I don’t do it because that’s illegal and also because I have a very limited amount of knives.
Don’t use the word “literally” when you really mean “figuratively”.
Because Laura Ingalls is fascinating and there’s nothing wrong with obsessively knowing every detail about her life and death.
You can always spit it out on the floor if you decide you don’t like it.
If people make fun of you, kick them in the back and then blame it on a ghost. Don’t let other people on the internet tell you what to do.
tag: content 80% of the end-user response time is spent on the front-end.
Most of this time is tied up in downloading all the components in the page: images, stylesheets, scripts, Flash, etc.
Reducing the number of components in turn reduces the number of HTTP requests required to render the page. One way to reduce the number of components in the page is to simplify the page's design.