Running a PageSpeed report on a site powered by SearchSpring may report some speed improvements possible in the handling of SearchSpring CDN resources. Below is a list of commonly reported issues.
SearchSpring’s resources should already be minified before being pushed to our servers. If you’re seeing this being reported it’s most likely due to professional services work done for your integration. Please report this to email@example.com.
Setting a cache expiration delay on many of our resources is complicated by a few factors that make setting long expiration times not possible at this time:
- Our resources are hosted on a Content Delivery Network (CDN) with hundreds of servers worldwide.
- We need to ensure that updates to our libraries are able to be quickly received by all of our clients and their customers. If we were to accidentally introduce a bug to one of our libraries we would not want our customers to have to wait a day to receive a fix.
- Many assets on our CDN are directly editable by our customers in our management console. When a customer makes a change to an asset they do not want to have to wait hours to be able to see that change.