How much time your page takes to load on the browser?
If it’s taking more than 3 seconds then you should be really worried about your site speed. Because No-one really likes slow loading websites.
There is no meaning of doing all the hard work to produce amazing content because if your website is too slow to load, the user is going to get bounced from your website.
So if you are really worried about your website speed and want to optimize it for your user and SEO you are at the right place.
By end of the article, you will be able to boost your page speed so much that any page on your website will be loading within 1-2 seconds.
Fast-loading sites perform better on all fronts: better user experience, higher conversions, more engagement and even higher search rankings. Page speed becomes more important in case you are targeting mobile traffic(Actually everyone is targeting).
Google does not benefit the fast loading websites. But for sure It penalizes the slow loading website and that means a lot.
The reason why it’s important right now is not that end users have noticed. It’s because Google has noticed.
With Google’s introduction of a mobile-first index, page speed is now more important than ever.
In 2006, Amazon reported that for every 100 milliseconds they speed up their website, they see a 1% increase in revenue.
There are always chances of improvement but it’s great if your page load within 1 second. Still, if you manage to load your page within 3 seconds, you are doing great. But when your page load time is going beyond 3 seconds, You need to pay serious attention towards it.
Over 10 seconds you are losing most of the audience of your site.
What Google say about page speed-
Here I am listing some of the important factors. After fixing these I am pretty much sure that your page will be loaded in 1-2 seconds.
For most of the website, the time consumed in loading a page is consumed by images/CSS/JS
Loading Resources(CSS/JS) asynchronously make your web pages amazingly fast. Because your content will not be waiting for any resource to be loaded.
If you manage to load them asynchronously, It will impact the speed amazingly.
Compression reduces response times by reducing the size of the HTTP response. Gzipping generally reduces the response size by about 70%. Some caching extensions/plugins do it automatically, sometimes you need to set it up manually at the web server level.
This will really improve your page speed.
You may need to load some CSS files in the header because in absence of these CSS your page will load broken or just white content until the CSS is loaded. The same case is for the jquery.js
A Content Delivery Network (CDN) is a collection of web servers distributed across multiple locations to deliver content more efficiently to users. The server selected for delivering content to a specific user is typically based on a measure of network proximity.
For example, When a user visits your site from India, they are downloading files from the server that is closest to them. Because the bandwidth is spread across so many different servers. Its really going to help you to improve the page speed.
Hosting your media files on a content delivery network is one of the best ways to speed up your site, and can often save up to 60% bandwidth and halve the number of requests your website makes.
Remember that 80-90% of the end-user response time is spent downloading all the components in the page: images, stylesheets, scripts, Flash, etc. This is the Performance, Golden Rule.
Always try to show more content using less HTML. Google also calculate the text to the content ratio which tells how much HTML you are writing to show a piece of content.
Make sure your page view source (press CTRL+U for view source) have the least space.
Most of the website doesn’t validate this But trust me it is one of the most important factors affecting your page speed. Make sure your content is W3c validated.
If your HTML is W3c validated means your HTML is more structured and authentic. It will help browser to understand and structure the HTML of your page.
If you have a decent amount of traffic, you should not be on hosts like Bluehost, Hostgator, GoDaddy and other low-budget web hosts like that.
There are a lot of premium hosting service provider with awesome speed. Using them you can boost your page speed amazingly.
Redirects are accomplished using the 301 and 302 status codes. Here’s an example of the HTTP headers in a 301 response:
HTTP/1.1 301 Moved Permanently
The main thing to remember is that redirects slow down the user experience. Inserting a redirect between the user and the HTML document delays everything in the page since nothing in the page can be rendered and no components can start being downloaded until the HTML document has arrived.
One of the most wasteful redirects happens frequently and web developers are generally not aware of it. It occurs when a trailing slash (/) is missing from a URL that should otherwise have one.
For example, going to http://yahoo.com/astrology results in a 301 response containing a redirect to http://yahoo.com/astrology/ (notice the added trailing slash). This is fixed in Apache by using Alias or mod_rewrite, or the DirectorySlash directive if you’re using Apache handlers.
@import uses up more resource than directly linking to your stylesheets despite achieving the exact same result. Another reason why not to use @import is that some of the older browsers do not support it, so it’s best to avoid it where possible.
Another reason why not to use @import is that some of the older browsers do not support it, so it’s best to avoid it where possible.
Expires headers tell the browser whether a resource on a website needs to be requested from the source or if it can be fetched from the browser’s cache.
When you set an expires header for a resource, such as all jpeg images, the browser will store those resources in its cache.
Next time the visitor comes back to the page it will load faster, as the browser will already have those images available,
There are two aspects to this rule:
For static components: implement “Never expire” policy by setting far future Expires header.
For dynamic components: use an appropriate Cache-Control header to help the browser with conditional requests.
Expires headers speed up your site in two ways. First of all, they reduce the need for users to download the same files from your web server twice.
Secondly, it reduces the number of HTTP requests that need to be made, further speeding up the time it takes for the page to load.
Adding Expires Headers is extremely easy. You just need to follow the instructions here to add a bit of code to your .htaccess file.
Keep in mind if you use a far future Expires header you have to change the component’s filename whenever the component changes.
Before your browser can display your web page it has to figure out how to lay out your content around your images.
Without knowing the size of these images the browser works it out, causing it to work harder and take longer.
Specifying your image dimensions saves the browser having to go through this step, which helps to speed things up.
To specify height and width in <img> elements, use height and width tags specifications.
<img alt="" width="150" height="200" />
HTTP Keep-Alive refers to the message that’s sent between the client machine and the web server asking for permission to download a file.
Enabling Keep-Alive allows the client machine to download multiple files without repeatedly asking permission, which helps to save bandwidth.
To Enable Keep-Alive, simply add this code in your .htaccess file
Header set Connection keep-alive
Specify a character set in HTTP headers to speed up browser rendering. This is done by adding a simple piece of code to your header:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Remove query strings from your static content because the browser can’t cache a link with ? in the URL. So it will improve your page speed.
Sometimes you are using more and more plugins on your site because of the functional requirement, But unknowingly you are using resources from a lot of the domains.
The browser has to make a new connection for every domain which is also time taking. So avoid loading your content from different servers. If you have to, download CSS, JS, images and upload these to CDN or your own server.
There are other ways to improve the speed of a web page, but I have tried to write about the most important ones which even professional bloggers (like SEOmoz) can sometimes overlook.
Of course, site speed is not the main goal but even an ideal website with a bad load time will find it hard to achieve success. So always try to improve page speed and run the fastest website you can in order to reach your goals faster.
I am the owner of acmeextension. I am a passionate writter and reader. I like writting technical stuff and simplifying complex stuff.