Skip to main content

Cache hit rate optimization

Query string sorting#

For most cache implementations the URL, as requested, is part of the cache key. This also includes query strings, in the order they are appended to the URL. As far as the cache is concerned, that means that the following two URLs are not treated as the same resource:

https://example.com/?a=1&b=2
https://example.com/?b=2&a=1

In Accelerated Domains we sort the query strings alphanumerically in ascending order before a request is matched against the cache. That way, we make sure that the two URLs above is treated the same and will match against the same resource in cache.

Ignoring query strings used for JavaScript based tracking#

The internet often feels slower when you click on advertisements, newsletters and other campaigns. With cache hit rate optimization, your marketing campaigns will not suffer from the usual performance hit you get when using marketing services. You’ll perform as if people were hitting your website directly.

Accelerated Domains removes the following query string keys, and it's value, before the request is passed on to the origin server:

gclid
utm_source
utm_campaign
utm_medium
utm_content
utm_term
utm_expid
omnisend
_ke
_sgm_(action|campaign|term|source)
mc_eid
mc_cid
fb(cl)?id
fbclid
klaviyo
cn-reloaded
__hs
_ga(.*)
_ga
fb_(action_(ids|types)|source)
action_(object|type|ref)_map
epik
hubs_(campaign|content|post(-cta)|signup-cta?)
hsfp
hssc
(__)?hstc
__twitter_impression
ao_noptimize
usqp
mkt_tok
epik
ck_subscriber_id