No one wants to visit a website that takes minutes to load. According to a study, most people will not view and spend time on your website or blog if it takes more than 10 – 15 seconds to load. If you make your website fast there are chances that you can increase your traffic. You will find lots of tips on the web related to making your website load time faster, many of them will give you silly codes (silly because they harm the on-page-SEO of your website) to put in your websites template.
Remove those PC speed calculating widgets and toolbars
I have noticed that many websites have widgets like –
PC speed calculator
IP address locator
Correct the markup errors on your website
Markup errors confuse the system and the server and thus can slow down your website. Now you must be thinking of finding all the errors in your code one-by-one manually, right? Don’t waste your time in that you can easily find all the markup errors and warning using W3C’s official service.
Inline images? Combine them in your stylesheets
According to a source, Inline images use the data: URL scheme to embed the image data on your website, this will increase the size of your HTML document not only affecting the load time but also decreasing the Text-to-HTML ratio of your website (which you must be knowing is bad for SEO). Combining inline images into your stylesheets is a way to reduce HTTP request and avoid increasing the size of your website.
Put stylesheets at top and scripts at bottom
While researching performance at Yahoo!, we discovered that moving stylesheets to the document HEAD makes pages appear to be loading faster. This is because putting stylesheets in the HEAD allows the page to render progressively.Front-end engineers that care about performance want a page to load progressively; that is, we want the browser to display whatever content it has as soon as possible. This is especially important for pages with a lot of content and for users on slower Internet connections. The problem caused by scripts is that they block parallel downloads. The HTTP/1.1 specification suggests that browsers download no more than two components in parallel per hostname. If you serve your images from multiple hostnames, you can get more than two downloads to occur in parallel. While a script is downloading, however, the browser won’t start any other downloads, even on different hostnames.