How to increase the speed of your web

1. 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 .

2. 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.)
The chunkiest parts of your website are the HTML, CSS, Javascript and images. By compressing them, you can decrease the average 'weight' of your website while it transfers.

1. 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%.

1. …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.

1. 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.

1. 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.

1. 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 .

1. 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.

1. 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.