Make Landing Page Redirects Cacheable (Deprecated)

Earlier in this article, we discussed avoiding landing page redirects. Obviously, web pages change and evolve over time, so they are necessary in certain circumstances. If you must create redirects, and this is especially important for redirecting to mobile-specific pages, make them cacheable to reduce the load time for visitors on subsequent visits. Additionally, PageSpeed recommended that these redirects should be set as 302 Found redirect and be made private through the cache-control header. This ensures proxies do not serve mobile redirects to non-mobile users.

Typically, mobile users will find themselves with less-than-ideal network coverage. Every millisecond is critical, and when the network conditions are poor, it makes waiting even that much more painful. This message has been mostly deprecated because website front-end platforms and frameworks now include the ability to automatically create pages that are responsive to desktop and mobile devices right out of the box. However, for any redirects you currently have, it is best practice to regularly review them to ensure the load and response times are within acceptable limits.



Lighthouse is an open-source tool that is used to run an audit against your web pages and provides scores and suggestions for improving page performance, accessibility, SEO, and more.


PageSpeed Terms

PageSpeed Insights is a tool created by Google that reports on the performance of a page on both mobile and desktop devices, and provides suggestions on how that page may be improved.



YSlow is an open-source website analysis tool that can be used to identify web page performance issues. Learn more about the YSlow to enhance your web pages and the user experience.