OptimizeForBandwidth setting provides a stronger guarantee of safety then
CoreFilters and is suitable as a default setting for use with sites that are not aware of PageSpeed.
pagespeed RewriteLevel OptimizeForBandwidth
The bandwidth savings resulting from this option are, of course, dependent on the source site. Our tests with the default settings for
OptimizeForBandwidth indicate an average bandwidth reduction of roughly 37% over the content of 1000 large web sites with a client that is capable of displaying webp images, and 25% improvement with older clients.
Adding Additional Options
Additional latency optimizations that modify HTML can be layered on top of
OptimizeForBandwidth in the root, but where individual sites have added
prioritize_critical_css, or simply turned on
CoreFilters, the following configuration fragment may be used:
As of PageSpeed 184.108.40.206 and later, In Place Resource Optimization is enabled by default. In earlier versions, turning on
OptimizeForBandwidth automatically enables In Place Resource Optimization to optimize the resources without needing to change their URLs. In these earlier versions, when a VirtualHost overrides the
CoreFilers, that turns off In Place Resource Optimization, but it can be re-enabled explicitly:
pagespeed InPlaceResourceOptimization on
Note: OptimizeForBandwidth is a new feature as of PageSpeed 220.127.116.11