commit | 03d69e53b120d06572eb50e5a1caf98b0b069b48 | [log] [tgz] |
---|---|---|
author | Maks Orlovich <morlovich@google.com> | Mon May 30 12:52:41 2016 -0400 |
committer | Maks Orlovich <morlovich@google.com> | Mon May 30 12:52:41 2016 -0400 |
tree | 90217c65e18af02a1772522c6ac036b2f1c4384c | |
parent | 15c6f7c345f9c155b5b9097bd85642d3406a81f4 [diff] |
Update for API change: kProcessScope is about to become kLegacyProcessScope (#1205) The renaming is to make it clear that kProcessScopeStrict (aka what ngx_pagespeed does for everything already) is what new code should be using, rather than current kProcessScope/upcoming kLegacyProcessScope which does weird backwards compatible things in mod_pagespeed.
ngx_pagespeed speeds up your site and reduces page load time by automatically applying web performance best practices to pages and associated assets (CSS, JavaScript, images) without requiring you to modify your existing content or workflow. Features include:
To see ngx_pagespeed in action, with example pages for each of the optimizations, see our demonstration site.
Follow the steps on build ngx_pagespeed from source.
Follow the steps on PageSpeed configuration.
For feedback, questions, and to follow the progress of the project: