Post by account_disabled on Dec 26, 2023 1:38:45 GMT -5
This goes for page and post redirects, image redirects, and everything in between. A redirect shows up as a blue circle in Pingdom, along with a 301 or 302 response header status. minimize redirects 301 in Pingdom How much impact do redirects have on your site? Let's do a little test. First, let's run a speed test on our contact page: . As you can see below, we get a total load time of 417 ms. Website speed test without redirects Website speed test without redirects So let's change the URL slightly and run another speed test to see the impact of multiple redirects. the same page now takes 695 ms to load. That's a 66% increase. Yikes! Website speed test with multiple redirects Website speed test with multiple redirects Check out our in-depth post on WordPress redirects and best practices for better performance.
Add Header Expires This tip was previously called “leverage Country Email List browser caching.” To lay it out, every script on your WordPress site needs an HTTP cache header attached (it should have it). This determines when the cache on the file expires. To avoid this warning, make sure your WordPress host has the right headers set cache-controlup expires. Kinsta provides these headers on all servers: take a look at the steps required to manually add caching headers on your server and read our guide on how to add expire headers . Leverage browser caching – caching header Leverage browser caching – caching header The other problem is that when you load third party scripts you don't have access to add cache headers, as you have no control over your web servers.
Common culprits include Google Analytics script and marketing pixels, such as Facebook and Twitter. To solve this problem you can host your Google Analytics script locally (although this is not officially supported) with a plugin like Perfmatters . WP Rocket also now has an option to host your Facebook marketing pixel locally. Moving scripts locally can have a different effect on the performance of your site. The only advantage is that you will have complete control over the file and can serve it from your CDN. This also eliminates a third-party DNS request. However, it is also important to remember that these files may already be cached in visitors' browsers. Read our in-depth post on how to eliminate the “leverage browser caching” warning . Remove Query Strings from Static Resources Another common problem is dealing with query strings. Your CSS and JavaScript files usually.
Add Header Expires This tip was previously called “leverage Country Email List browser caching.” To lay it out, every script on your WordPress site needs an HTTP cache header attached (it should have it). This determines when the cache on the file expires. To avoid this warning, make sure your WordPress host has the right headers set cache-controlup expires. Kinsta provides these headers on all servers: take a look at the steps required to manually add caching headers on your server and read our guide on how to add expire headers . Leverage browser caching – caching header Leverage browser caching – caching header The other problem is that when you load third party scripts you don't have access to add cache headers, as you have no control over your web servers.
Common culprits include Google Analytics script and marketing pixels, such as Facebook and Twitter. To solve this problem you can host your Google Analytics script locally (although this is not officially supported) with a plugin like Perfmatters . WP Rocket also now has an option to host your Facebook marketing pixel locally. Moving scripts locally can have a different effect on the performance of your site. The only advantage is that you will have complete control over the file and can serve it from your CDN. This also eliminates a third-party DNS request. However, it is also important to remember that these files may already be cached in visitors' browsers. Read our in-depth post on how to eliminate the “leverage browser caching” warning . Remove Query Strings from Static Resources Another common problem is dealing with query strings. Your CSS and JavaScript files usually.