How to see where an HTTP request comes from

[mouakter13]

At a high level, there are two broad strategies for making fewer HTTP requests:

Remove HTTP requests. If possible, you should completely remove all unnecessary HTTP requests. For example, if you have a plugin that doesn't add any value to your site and is loading its own CSS and JavaScript, completely remove that plugin to get rid of all its HTTP requests.
Combine HTTP requests. If you have HTTP requests that need to be loaded, you can combine them into a single file. For example, instead of six small CSS files, you can combine them into a single, larger CSS file, which will load faster because the browser needs to make fewer requests (this is not always the case with HTTP/2 , which we'll cover later).
We'll start with tactics that focus on dropping HTTP requests and then look at how to merge the remaining HTTP requests. The main idea is to drop as much as possible and then merge what's left.

1. Remove unnecessary WordPress plugins
To start, you’ll want to use waterfall analysis to get all of the requests from your plugins. You can do this by searching for “plugins,” which will show all of the HTTP requests originating from the wp-content/plugins folder .

If you hover over the file name, you can see which plugin chile phone number data it came from. For example, here you can see a request for the slider plugin you might be using.

If we dig a little deeper, we'll see that Slider Revolution adds three of its own HTTP requests, even though this test page doesn't contain any sliders:

If you're using Slider Revolution for a key slider, then you may need to keep it. But if you installed it for testing, and then removed the slider, and now you're not really using it… then you should remove it to get rid of those HTTP requests.

Basically, you need to go through the entire list and ask yourself if each plugin is actually adding value to your site. If a plugin isn't (but is adding HTTP requests), then you're better off removing it.