For example, if you have a plugin that adds no value to your site and is loading its own CSS and JavaScript, just completely remove that plugin to get rid of all of its HTTP requests. If possible, you should completely remove every unnecessary HTTP request.
#Http request analysis how to
How to Optimize and Make Fewer HTTP Requests in WordPressĪt a high level, there are two broad strategies to make fewer HTTP requests: In this way, you can see if any plugins that you’re using are adding a lot of HTTP requests (especially slow-loading requests). For example, you can see that WooCommerce adds seven of its own HTTP requests: You can also find HTTP requests from the different WordPress plugins that you’re using by searching for the name of that plugin’s folder on your server. For example, the 839.3 KB image takes 1.12s while the 57.6 KB image took just 87.5 ms: You can see how not all HTTP requests are equal. Here, you’ll see a list of each individual HTTP request on your site along with information on how long that HTTP request took to download: To analyze your individual requests, go to the Waterfall tab below. This shows you how many HTTP requests your site has, but it doesn’t break down the individual requests: Once you plug in your URL, you’ll see a basic summary box at the top. However, we’ll use GTmetrix for our screenshots. You can also use your browser’s developer tools. Most speed test tools offer this, but the interfaces at GTMetrix and Pingdom are very convenient. To analyze your site’s HTTP requests, you can use something called Waterfall analysis. If you want to make the biggest improvement to your site, focusing on the big, slow-loading HTTP requests first will have the biggest return on your investment. Some are slower than others.įor example, the request for a huge 3 MB image file will take a lot longer than the request for a tiny 20 KB image. Some HTTP requests are bigger than others. However, all HTTP requests aren’t always “equal”. How to See and Analyze Your Site’s HTTP RequestsĪbove, you learned that all things being equal, reducing the number of HTTP requests will speed up your site. So if a website has to make 70 HTTP requests before it can display the page, that’s going to take longer than if it has to make 40 HTTP requests.Īdditionally, some HTTP requests will “block” other HTTP requests, which means that the browser can’t start downloading certain HTTP requests until it finishes downloading the HTTP requests before it.īottom line is: when you make fewer HTTP requests, you make your website load faster.
While this is a bit of an oversimplification, the basic idea is that the web browser will only display the website to your visitor once it’s finished downloading all of the HTTP requests (though there are some tactics to tell the browser it’s ok to wait for certain files). So if you want to make your website load faster, you need to optimize and reduce the number of HTTP requests that your site requires. In general, the more HTTP requests your website has, the slower it’s going to load. Why Is It Important to Reduce HTTP Requests? Similarly, if you use four WordPress plugins and each plugin adds its own CSS stylesheet, the visitor’s browser will need to make four separate HTTP requests, one for each plugin’s stylesheet. For example, if you have five image files on a webpage, the browser needs to make five separate HTTP requests, one for each image. One important thing to understand is that each separate element is a separate HTTP request. HTTP, short for Hypertext Transfer Protocol, is how these computers (the visitor’s browser and your webserver) communicate. Of course, it’s a little more complicated than that, but that’s the basic idea. Once the web browser gets those files, it can assemble the web page for your visitor. The server then responds to those requests with the files in question. To do that, it makes HTTP requests to the server for each individual resource.įor example, it might say, “hey server, I need that coolimage.png file” and “hey server, I also need the CSS stylesheet for that contact form plugin“.
#Http request analysis download
When someone visits your website, their browser needs a way to download all of the resources required for that page from your server. You have the different image files that you use on a page, the CSS stylesheets that control how content looks, the JavaScript files that add all that cool functionality, and so on. When you build a website, it has a lot of different parts. See how Kinsta stacks up against the competition.
0 kommentar(er)
