Pack Hosting Panel


How to test the behaviour of the Percolate Pagespeed Optimizer.

Why you need to test

After Percolate has been installed and configured for your application, it's important do a functional test in order to prove that:

  • Percolate is configured and optimized correctly.
  • All resources can be optimized.
  • Your application functions the same with and without Percolate.
  • Your application performs better with Percolate activated compared to without.
  • Percolate will be purged (direct or delayed) after the application cache has been cleaned.

Verifying the resource optimization status on the Percolate status page

When Percolate is installed and configured correctly, you can find a list of all resources that will and have been optimized on the Percolate status page: yourapplication.com/.percolate/status.

If all listed resources have been optimized succesfully, they will show at least 1 at optimize counter, and won't show any errors on the error counter.

The following image shows two different resources, both optimized for 3 different user agents:


Inspecting the Percolate HTTP response headers

Percolate comes with two response headers that can be inspected in order to verify if a requested URL has been optimized by Percolate and served by the proxy: x-percolate-hitmiss and x-percolate-optimized-at, with the latter indicating the timestamp of the actual performed optimization.

The following image shows a Chrome DevTools fragment, indicating that the url has been optimized and served by Percolate succesfully:


Verifying if the application looks and behaves the same with versus without Percolate

Every url of your application can be appended with querystring paramater ?nocache=1 in order to force the Percolate proxy to serve the original resource instead of the optimized resource. This enables you to test and compare the look and feel of your page, and you can use it to compare both versions of a page with web performance testing tools like PageSpeed Insights or GTmetrix.