Here are some stories that WordPress can like if it wants to speed up. The other day, I created a shiny website. I have tried my best to add woocommerce, Google tag manager, onesignal, help desk, yoast, live radio (oh, yes, yes), cookie notification, social media and many other plug-ins. I’m as keen to impress visitors as you are, or think so. But then things got unbearably slow. After careful consideration, we ran gtmetrix to solve the problem. The
Disappointingly, I saw this. Was I moved? Naw hell! I got the perfect a and wanted to reduce the page load time to less than 2 seconds. So I pressed the retest button. What happens? Or the same painful result. I got goose bumps and even got angry. But even if we can’t tolerate these, we won’t give up easily. Do you know what I did next? I tested the site at pindom because gtmetrix can wash it. But here are the bleak results again. I am angry. My body’s saying is that the wrong HTTP request enables me to quickly fix many other problems. The
To make matters worse, in order to build the website, I used the e-commerce WordPress Theme loaded with 1billion elements. In my defense, it looks incredible. Some users agree with the design points. So yay, I haven’t been cheated. However, excellent visual design and slow speed cannot be balanced. I need solutions and fast things. How can I reduce HTTP requests on my WordPress site? Every time you visit the WordPress web site, a large amount of data moves between the browser and the web server. That is, WordPress sends HTTP requests to various servers to build what users see when they load the site. The
If more elements need to be loaded on the WordPress site, there will be more HTTP requests, and vice versa. More HTTP requests mean slow websites, poor user experience (UX), poor SEO scores, and low conversion rates. WordPress sites are usually dynamic. That is, rendering a web site in a browser requires many different parts. The good news is that you can reduce HTTP requests and greatly improve the site speed. And in today’s post, you learned that method exactly! Reports from gtmetrix and pindom usually show the location of the problem. Therefore, use these two tools to test the site to find areas that need improvement. How to reduce http\/s requests and speed up the word press site when preparing reports: The
Step 1: To sum up, if there are many items on the WordPress website, there are too many HTTP requests. No idea. The first step in reducing HTTP requests is cleanup. That is, delete all unnecessary plug-ins. The WordPress plug-in comes with many files, such as PHP, CSS, or JavaScript (JS). All files that each plug-in runs generate HTTP requests. If there are many plug-ins, there will certainly be more HTTP requests. The fewer plug-ins, the fewer requests. Simple. What are you doing? Perform a plug-in audit. What plug-ins are required to run the web site? Are there any unnecessary plug-ins? Are there any plug-ins that utilize third-party servers? Can you do it without this plugin? The
To reduce HTTP requests, remove all unnecessary plug-ins. If you need plug-ins occasionally, install them only when you need them
Please pay attention here. You do not have to move all scripts to the bottom. This is because pages may need CSS and JS to provide a completely engaging experience. If you delay some CSS or JavaScript files, a distorted version of the web page may be displayed to the user until the page is fully loaded. This is the exact opposite of what you want to achieve. Therefore, you only need to delay loading scripts that are not needed by the page. In this way, the user will not wait too long until the page is loaded. What’s the matter. Because fewer HTTP requests are required to deliver messages. Since all scripts and files will eventually be loaded, the HTTP request itself will not be reduced, but the number of HTTP requests required to render the page will be reduced. This is very similar to deferred loading of images. The image is loaded only in the viewport, not when the rest of the page (and the most important part) is loaded. Incidentally, modifying CSS and JS that prevent rendering may display files and scripts that are not needed to build web pages. For example, if it takes a long time to load some external social sharing JS scripts, it may be delayed. On this basis, you can remove it and build social sharing on your theme. You can delete HTTP requests and speed up your site while retaining the same functionality. It is difficult for most beginners to code functions into topics. Please confirm with advanced WP users or developers. As an alternative, you can use the WP rocket plug-in to modify scripts that prevent rendering, but be careful. Read the documentation because if the problem gets worse, the site can easily be damaged. Is there a free option? Of course! We are working with word press. Remember? You can use async JavaScript in other plug-ins. Step 5: did you know that caching and CDN can reduce HTTP requests? It may not seem true at first, but considering what happens later, you can use caching and CDN advantageously. Caching includes saving static files in the browser to prevent users from ing files in subsequent visits. Suppose you have a caching plug-in and the cached content when the user accesses it for the first time. During subsequent visits, your site will not make requests to the server. On the contrary, browsers provide cached resources, reduce HTTP requests, and improve site speed. CDN is the global location server network (or C is d elify twork). CDN also uses caching, but for faster speed, the CDN provider will provide cached content on the server closest to the visitor. The shorter the distance, the faster the content transmission speed. Caching means that the website does not need to re the same content from the central server. Does it mean anything to you? Check the information and the demo. The most important thing is that there are many free CDN options. Wpexplorer uses cloudflower and selects the CDN that is actively recommended but most suitable. Bonus: check whether http\/2 is supported. You can make every effort to reduce HTTP requests, but the web host may be the cause of the problem. Don’t be surprised. In this era, who uses anything other than http\/2? You may not even know what http\/2 is. First, http\/2 supports asynchronous loading of files. Although there are other advantages compared with HTTP 1.0, this is a lesson for other days. If HTTP is below 1.0, you can view a large number of HTTP requests. Don’t jump to judgment. I still see web hosting providers using HTTP 1.0 and older versions of PHP. Yes, the obvious advantages of http\/2 and php7
