PHPackages mediarox/pagespeed - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. mediarox/pagespeed ActiveMagento-module[Utility & Helpers](/categories/utility) mediarox/pagespeed ================== 1114.1k[1 PRs](https://github.com/mediarox/pagespeed/pulls) Since Sep 23Compare [ Source](https://github.com/mediarox/pagespeed)[ Packagist](https://packagist.org/packages/mediarox/pagespeed)[ RSS](/packages/mediarox-pagespeed/feed)WikiDiscussions Synced 2w ago READMEChangelogDependenciesVersions (1)Used By (0) Magento Google PageSpeed Optimization Extension ----------------------------------------------- [](#magento-google-pagespeed-optimization-extension) This extension should help, to fulfill the requirements of the tool [Google PageSpeed Insights](https://developers.google.com/speed/pagespeed/insights/). ### Current features [](#current-features) 1. Move all Javascript tags (head & inline) to the bottom. `({stripped_html}{js})` - including conditional js units `()` - including external js tags - including "inline" js tags 2. Move all CSS tags (head & inline) to the bottom. `({stripped_html}{css})` - including conditional css units `()` - including external css tags - including inline css tags 3. Backend configuration option to exclude specific js tags/units or css tags/units from the move. (regex pattern) ### Compatibility [](#compatibility) From Magento 1.5.x to Magento 1.9.x . ### Backend Configuration [](#backend-configuration) All modules (Pagespeed\_Js, Pagespeed\_Css) are disabled by default. Configuration path: System > Configuration > ADVANCED > Pagespeed ### How it works ? [](#how-it-works-) Simple parse the final html stream on the event "controller\_front\_send\_response\_before". ### What about performance/parsing time ? [](#what-about-performanceparsing-time-) On our local hardware the html parsing requires a maximum of 4 milliseconds. ### Requirements from PageSpeed Insights and planned features [](#requirements-from-pagespeed-insights-and-planned-features) 1. [Eliminate render-blocking JavaScript and CSS in above-the-fold content](https://developers.google.com/speed/docs/insights/BlockingJS) (feature 1 & 2) 2. [Prioritize visible content](https://developers.google.com/speed/docs/insights/PrioritizeVisibleContent) (possible with feature 3) ### Requirements from PageSpeed Insights which are covered by 3rd party extensions [](#requirements-from-pagespeed-insights-which-are-covered-by-3rd-party-extensions) 1. [Minify CSS](https://developers.google.com/speed/docs/insights/MinifyResources) 2. [Minify JavaScript](https://developers.google.com/speed/docs/insights/MinifyResources) - Both are covered by [Speedster Advanced by Fooman](http://www.magentocommerce.com/magento-connect/speedster-advanced-by-fooman.html) (note: that we have no experience with this extension, but Fooman seems to be a good guy.) 3. [Optimize images](https://developers.google.com/speed/docs/insights/OptimizeImages) - [Image Optimization](http://www.magentocommerce.com/magento-connect/image-optimization.html)(note: no experience too.) 4. [Minify HTML](https://developers.google.com/speed/docs/insights/MinifyResources) - Based primary on [Minify CSS](https://developers.google.com/speed/docs/insights/MinifyResources) and [Minify JavaScript](https://developers.google.com/speed/docs/insights/MinifyResources). ### Requirements from PageSpeed Insights which are covered by your server admin :) [](#requirements-from-pagespeed-insights-which-are-covered-by-your-server-admin-) 1. [Enable compression](https://developers.google.com/speed/docs/insights/EnableCompression) 2. [Avoid landing page redirects](https://developers.google.com/speed/docs/insights/AvoidRedirects) 3. [Leverage browser caching](https://developers.google.com/speed/docs/insights/LeverageBrowserCaching) 4. [Reduce server response time](https://developers.google.com/speed/docs/insights/Server) ### Goal [](#goal) [![Goal](https://camo.githubusercontent.com/687b167e1c91bee4f46d6e43e0379c01e0c31297a0667d7521a23bcda274e879/687474703a2f2f7777772e6d65646961726f782e64652f676f616c2e706e67)](https://camo.githubusercontent.com/687b167e1c91bee4f46d6e43e0379c01e0c31297a0667d7521a23bcda274e879/687474703a2f2f7777772e6d65646961726f782e64652f676f616c2e706e67) ### Notices [](#notices) 1. There is also a great tool called [PageSpeed Module](https://developers.google.com/speed/pagespeed/module)for common webservers like apache and nginx. If you have the opportunity: Use it, but read the manual. 2. Test before use. There are also "great" things like multiple `` tags, that will crash the party. 3. Front Page Cache: Test it. Look that our event "controller\_front\_send\_response\_before" is called before your FPC-Extension starts to observe. 4. If an Javascript use the outdated "document.write", it must be excluded by the regex pattern. ### Developers [](#developers) - Steven Fritzsche [@de\_mediarox](https://twitter.com/de_mediarox) - Thomas Uhlig [Xing](https://www.xing.com/profile/Thomas_Uhlig24) ### Special thanks [](#special-thanks) - Sander Kwantes [sanderkwantes](https://github.com/sanderkwantes) - Adam Johnson \[adamj88\] () - Ben Corlett \[bencorlett\] () ### Features inspired by [](#features-inspired-by) - Daniel Chicote [Github](https://github.com/danielchicote) - Henk Valk [Github](https://github.com/henkvalk) - Dan Stevens [from Activ8](https://twitter.com/Activ8Ltd) ### Licence [](#licence) [OSL - Open Software Licence 3.0](http://opensource.org/licenses/osl-3.0.php) ### Copyright [](#copyright) (c) 2015 mediarox UG (haftungsbeschraenkt) () ### Health Score 26 — LowBetter than 40% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity29 Limited adoption so far Community2 Small or concentrated contributor base Maturity41 Maturing project, gaining track record How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Community Maintainers ![](https://avatars.githubusercontent.com/u/1479824?v=4)[mediarox](/maintainers/mediarox)[@mediarox](https://github.com/mediarox) ### Embed Badge ![Health badge](/badges/mediarox-pagespeed/health.svg) ``` [![Health](https://phpackages.com/badges/mediarox-pagespeed/health.svg)](https://phpackages.com/packages/mediarox-pagespeed) ``` PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)