Speed up your website: This blog series about site speed has a ton of fun ride you just have to read to the end. Up until this point, we’have learnt that Amazon would lose $1.6 BILLION if their site’s slow down.
We’ve likewise learnt precisely what’s happening behind the scenes to cause site slowdown.
It takes us to our natural conclusion: how precisely would you be able to speed up your website? We’re covering everything from server speed, to optimization and a couple of extra additional items in the middle.
To start with, we should recap what’s causing slow speed:
When you load up my site here at Akeentech, your browser (Safari, Firefox, Chrome and so on) begins a conversation with my web server.
- It says: “Hello web server! Would you be able to get me every one of the pieces and bits to show akeentech.com please?”
- Web server says: “Yeah sure thing let me look for them, and send them over”.
At that point, the web server puts all the site parts into a tunnel, and sends them crosswise over to your web browser to load it up.
Sounds sufficiently straightforward, yet this is what will slow things down:
- A very lazy server that takes forever to respond to requests.
- A server that is managing parts for lots of other sites simultaneously.
- Lots of big site ‘parts’ that each need to be found and pass down the tunnel.
- A very busy tunnel.
There is a lot which can go wrong here.
So, how do we help to speed up your website?
#1. Upgrade to a better web host
Your website host is the company that gives the server. It just like leasing a plot of web land, where you’ll store all the site parts.
Majority of us tend to purchase the least expensive plot of land we find. In any case, that is not really a wise solution.
Cheap web hosts rent servers that are small, and crowded. Keep in mind, you need your server to respond rapidly to requests, and send your site down the tunnel to the browser speedily to speed up your website.
Read Also: 5 MOST IMPORTANT ON-PAGE SEO TIPS
#2. Switch from shared hosting to a VPS
Cheap website hosts will put your site on a server alongside huge amounts of other sites. It’s called shared hosting, and it implies you need to battle it out for resources.
In the event that one site all of a sudden gets loads of traffic, it will slow down your site, while they eat up the bandwidth.
By changing to a VPS (a virtual private server), your web host will fence off a corner of the shared server only for you. It implies you don’t need to stress over other sites taking your resources and that will speed up your website.
Read Also: The Best 7 Essentials for a Profitable Blog
#3. Move the server closer to your audience
Each time somebody clicks on your site, your server needs to physically send the information over the planet to their PC screen.
On the off chance that the server is on the other side of the world, that will take quite a while. If you know where majority of your traffic is originating from, you can ask that your website host put your site on a server nearest to your main readers or audience and that will speed up your website.
#4. Make use of a content delivery network
The issue with moving your server nearer to a specific group of audience is that somebody will miss out. In the event that you move your server to California, your visitors from Australian will get a slow loading time. So also your European visitors and so on.
A CDN or content delivery system puts your information on servers all over the world. So when somebody clicks on your site, the server nearest to them sends the data.
It implies your visitors get a super fast speed wherever they are on the planet. Therefore, you need to make use of a CDN to speed up your website.
#5. Activate the ‘keep alive’ setting
At the point when your server sends your site files down the tunnel, each part travels independently. Your logo, your CSS style sheets every one of your images, and so on.
Clearly, the most effective way to do this is sending them all down the same huge tunnel.
That is the place where the ‘keep alive’ setting comes in. At the point when it’s activated, the main tunnel remains on, and everything comes down the same connection. (This is superbly fast).
However, when the setting is off, a new tunnel must be made for each component. (This is superbly slow).
Most web hosts keep this setting on (which is great), yet at times shared hosts close the connections all of a sudden without warning.
Since we’ve made your server as efficient and fast as possible, how would we optimize the site parts themselves?
#6. Reduce round trip time
Your browser as of now needs to ask the server for every element, each one at a time. Your logo, every one of the images, then your CSS stylesheet. The time it takes to get (receive) it is one round trip.
The more round trips you need to make, the more it takes the whole site to load. It resembles packing up your car with boxes, and moving them to another house.
The more boxes you have, the more round trips you must make. The solution? Cut down the boxes amount you’re taking.
Decrease the amount of elements your server needs to send down the tunnel. Less images, fewer code, less plugins to speed up your website.
Read Also: 12 HABITS OF SUCCESSFUL BLOGGERS
#7. Enable compression on your website
Unfortunately, it’s not only the number of boxes. It’s the means by which heavy they are. In the event that most of your elements are heavy and big, it will take up a lot of space in your tunnel. They’ll likewise move slower. It just like lorries building up. Each loaded with heavy boxes.
Fortunately, to speed up your website you can get your site compressed, and everything on it. Utilizing a tool like Gzip. (90% of browsers recognized it. – That’s pretty much aside from a couple of stragglers still using IE Internet Explorer 4.)
Fun fact: The average weight of a website is 2MB, however it’s developing bigger each year.
#8. Optimize your site images
Images are generally the weightiest part of any site. They’re the biggest, slowest, fattest, loading element.
Begin by editing them down to the correct size you need them. Try not to upload tremendous images, and scale them down in the HTML. Simply transfer them at the correct size.
Additionally, compress your pictures before you upload them. If you are using WordPress, plugins like WP Smush could get the image size cut down by a great 80%.
Read Also: 10 things you should do on forum
#9. … Or make sprites
A sprite is one single image which contains loads of little images. It’s awesome for sharing buttons or any other image elements.
Presently, your site simply needs to make one single request, as opposed to ten separate ones. You would then be able to use CSS to pick which parts of the image are shown where.
#10. Trim your site code
HTML is heavy and dense. It’s additionally incredibly repetitive. CSS is somewhat more streamlined, however bunches of it is redundant.
It is time to go through your code with absolute attention to detail, and dispose of all the unecessary bits.
In case you’re using a WordPress template, Tumblr template and so forth, then there is likely loads of code you’re not using. These templates are set up to give you loads of choices for functionality. However, majority of us needn’t bother with it at all.
#11. Uninstall useless plugins
We have all experimented with huge amounts of plugins throughout the years. However, we forget to uninstall them. Each plugin is also another server request. It’s another heavy package obstructing high-speed tunnel. In case you’re not using it, turn it off.
Read Also: Blogging 101
#12. Reduce redirects
For each redirect, your packages go all over (up and down) the tunnel twice. Unless you totally need to, don’t use redirects on your site to speed up your website.
Read Also: Adsense approval within 3 days
#13. Reduce DNS lookups
There’s one a part in the process we haven’t discussed yet. It happens right at the very beginning. Prior to your browser begins the conversation with the server, it needs to discover the server’s location (By looking for its IP address). It resembles looking into the server’s number in the telephone book. That takes a brief period. (Normally 20-100 milliseconds).
It takes considerably longer if there are numerous domain names associated with your site. Regular examples include: blog.yourwebsite.com, forum.yourwebsite.com, or extra domains for stylesheet, flash objects and images. If your browser needs to do it five times, you may lose half a second. Keep it to as couple of domain as you could reasonably keep.
#14. Browser caching
Imagine how quick things would be if your browser could keep a duplicate of all the site files. That way, it wouldn’t need to contact the server so often. It could simply load them up from memory.
That is the thing that caching is. It implies your browser ‘remembers’ the site. Whenever you load it up for a second time, it’s superbly fast.
Phew! That was a bit longer post than regular, however I think it was justified, despite all the longevity.
Now that you know everything there is to know on how to speed up your website. These traps could shave seconds off your site load speed. That implies happy readers or visitors. Also, it implies more sales. As usual, thanks for reading and feel free to drop your comment, questions and thoughts on site load speed.