GET parameters

If you suspect that a query string is causing a poor user experience, you can investigate further by using a GET parameter filter to identify the specific parameter at fault. You can try to fix the problematic parameter once you've identified it to improve the user experience.


This filter is frequently used together with the Time to First Byte filter. If this metric fails, the First Contentful Paint and Largest Contentful Paint will suffer as well. Checking to see if there are any improvements here is frequently a good idea.


In this example, it appears that the gclid (google ad click identifier) is significantly higher than the values for "none" or other GET parameters. Which is a pity because you are paying to get this traffic to your website.


Ignore query string parameters that will have no effect on the contents. Many parameters do not have or require this behavior, despite the fact that query string parameters for pagination, search, or filtering will produce different HTML.

It's possible that you overlooked a required query string in your caching strategy. This can be a significant issue for page speed, particularly if you use a Content Delivery Network (CDN) such as Cloudflare. Fortunately, this issue can often be resolved in a matter of minutes.

Table of Contents