When a page is requested by an end user, many of the page resources are static files such as javascript, css, and fonts. When these files are requested from Pagebuilder, they must have a deployment parameter (?d=) added to the url. This is obviously useful because it avoids the user from having stale versions of these files, however the vast majority of these files do not change in a given deploy. This has a negative impact on site performance, because it means that files that may have TTLs of 30 days or even 1 year effectively have a TTL of whatever the median time between deploys is.
Ideally, Pagebuilder would support another method of ensuring that users always have the latest version of these types of files without needlessly fetching copies of files that have not actually changed. As an example, I have seen an md5sum in a `?v=` parameter used for this.
Guest
This is more than just a cache-busting param and it's actually required for Fusion deployment infrastructure (files are written in the bucket with this token so we know where to look for them). We can think about other ways to address this.