SXG tests

New vs established subresources demo

  1. Open Network tab in Chrome Dev Tools.
  2. Set the desired number of new and established subresources and click the button.
  3. Wait for the SXG cache (up to 1 minute, typically 15 seconds). Continuing without waiting won't break anything, but keep in mind results may not be final and you may need to repeat the next step one or more times.
  4. Click the same button again.
  5. Observe the Warning header in the HTTP response if number of new subresources is too high.



Explanation

If the page contains too many new subresources, Cloudflare may struggle to generate SXG page quickly and fallback to HTML response.
This leads to Google SXG cache receiving non-SXG response and caching an error for some time.

For the context see this article.