You'll be sent to the next test automatically. You can go there manually by clicking here.
This test determines if redirects are cached. Redirects are bad for performance, but they're still used quite a bit. For example, http://google.com/ redirects to http://www.google.com/, and http://www.google.com (without a trailing slash) redirects to http://www.google.com/. If a redirect response includes headers indicating it should be cached, then it would save the user an extra roundtrip next time they hit that redirect. Here, we revisit a redirect that was previously fetched on the Prime the Cache page, and determine whether the redirect was read from cache or was fetched again.