PHPackages monogo/pagespeed-analysis - 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. monogo/pagespeed-analysis ActiveMagento2-module[Utility & Helpers](/categories/utility) monogo/pagespeed-analysis ========================= Magento 2 module for Google PageSpeed Analysis 1.3.4(4y ago)610.9k2[2 issues](https://github.com/MonogoPolska/monogo-m2-pagespeed-analysis/issues)MITPHPPHP ~7.3.0||~7.4.0 Since May 29Pushed 4y ago1 watchersCompare [ Source](https://github.com/MonogoPolska/monogo-m2-pagespeed-analysis)[ Packagist](https://packagist.org/packages/monogo/pagespeed-analysis)[ RSS](/packages/monogo-pagespeed-analysis/feed)WikiDiscussions develop Synced today READMEChangelogDependencies (3)Versions (22)Used By (0) #### Magento 2 module for Google PageSpeed Analysis. [](#magento-2-module-for-google-pagespeed-analysis) This module will work only with Magento 2.4.0 and higher Module is using chart.js : **Install** =========== [](#install) ### Git [](#git) - Locate the **/app/code** directory which should be under the magento root installation. - If the **code** folder is not there, create it. - Create a folder **Monogo** inside the **code** folder. - Change to the **Monogo** folder and clone the Git repository () into **Monogo** specifying the local repository folder to be **OptimizeDatabase**e.g. ` git clone https://github.com/MonogoPolska/monogo-m2-pagespeed-analysis PagespeedAnalysis` ### Composer [](#composer) `composer require monogo/pagespeed-analysis` ### Magento Setup [](#magento-setup) - Run Magento commands `php bin/magento setup:upgrade` `php bin/magento setup:di:compile` `php bin/magento setup:static-content:deploy` **App Configuration Options** ============================= [](#app-configuration-options) Go to Stores->Configuration->Monogo->Pagespeed Analysis - Enable module **Default value is 1 (Yes)** - Provide PageSpeed API Key. You can get one from -> Get A Key - Select strategy \[Mobile,Desktop\] - Use Magento Cron - You can disable Magento cron and run PageSpeed scan from shell (recommended) **Default value is 0 (No)** - Cron schedule - Use Crontab Format (Eg. "0 0 \* \* \*" every day at 01:05) - Provide website / websites to scan - Additional charts configuration (show last X days, colors, chart height, use auto scale) - Debug settings ### Default values: [](#default-values) enable: 0 strategy: mobile,desktop use\_cron: 0 height: 150 px history: 30 days **Chart colors** performance: #4268b3 seo: #d46fd4 pwa: #f2970e best\_practices: #24a318 accessibility: #f5d60c ttfb: #0c90f5 **Shell** ========= [](#shell) ``` Usage: php bin/magento monogo:pagespeed:run ``` You can setup external cron to run: `* */4 * * * php bin/magento monogo:pagespeed:run` **Report** ========== [](#report) Go to Reports->Statistics->Pagespeed In tabs you will have charts with desktop/mobile view. Under Show details button you will see last scan details. In Grid you can add comment to specific record (for example: **A/B testing start** or **Production deployment**) This comment will be visible on charts after page refresh. **TODO** ======== [](#todo) - email weekly reports - Tests ### Health Score 33 — LowBetter than 75% of packages Maintenance13 Infrequent updates — may be unmaintained Popularity25 Limited adoption so far Community9 Small or concentrated contributor base Maturity68 Established project with proven stability Bus Factor1 Top contributor holds 100% of commits — single point of failure 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. ### Release Activity Cadence Every ~43 days Recently: every ~27 days Total 20 Last Release 1707d ago PHP version history (3 changes)1.0.1PHP ~7.1.0|~7.2.0 1.0.9PHP ~7.2.0|~7.3.0 1.2.0PHP ~7.3.0||~7.4.0 ### Community Maintainers ![](https://www.gravatar.com/avatar/87059637e00638d5d5d08d8e94ef97b3168cd0b4bfde4e512ed77cef38106ae5?d=identicon)[Monogo](/maintainers/Monogo) --- Top Contributors [![pawel-detka](https://avatars.githubusercontent.com/u/17678684?v=4)](https://github.com/pawel-detka "pawel-detka (27 commits)") --- Tags Insightsmagento 2PageSpeed ### Embed Badge ![Health badge](/badges/monogo-pagespeed-analysis/health.svg) ``` [![Health](https://phpackages.com/badges/monogo-pagespeed-analysis/health.svg)](https://phpackages.com/packages/monogo-pagespeed-analysis) ``` ### Alternatives [magepal/magento2-googletagmanager Google Tag Manager (GTM) for Magento 2 with Advance Data Layer 2671.5M4](/packages/magepal-magento2-googletagmanager)[yireo/magento2-webp2 Magento 2 module to add WebP support to the Magento frontend 2091.2M7](/packages/yireo-magento2-webp2)[tig/postnl-magento2 TIG Magento 2 PostNL extension 58544.2k4](/packages/tig-postnl-magento2)[magepal/magento2-reindex Reindex your Magento2 store quickly and easily from backend/admin, instead of command line. 112649.7k1](/packages/magepal-magento2-reindex)[magepal/magento2-customeraccountlinksmanager Customer Account Links Manager for Magento2 allows you to quickly and easily remove unwanted links from customer account dashboard 4084.9k](/packages/magepal-magento2-customeraccountlinksmanager)[magepal/magento2-preview-checkout-success-page Quickly and easily preview and test your Magento2 checkout success page, without placing a new order each time 7790.6k](/packages/magepal-magento2-preview-checkout-success-page) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)