Google Pagespeed Insights is a tool that empowers you to make decisions that increase the performance of your website. Recommendations from Google Pagespeed are based upon current industry best practices for desktop and mobile web performance.
Through the addition of advanced data visualization, tagging, filtering, and snapshot technology, Insights from Google PageSpeed provides a comprehensive solution for any webmaster looking to increase their site performance, their search engine ranking, and their visitors browsing experience.
Detailed Page Reporting
Sort your page reports by their Page Speed Score to prioritize the largest areas of opportunity on your site. Page reports utilize easy to read visualizations that allow you to quickly focus in on the most important data to improve your sites performance.
Report Summaries are a powerful and exclusive feature of Insights from Google PageSpeed. Summaries display your average Page Score, largest areas for improvement across ALL reports, as well as best and lowest performing pages. Report summaries can be filtered to narrow results by: Pages, Posts, Categories, Custom URLs, and Custom Post Types.
Using Report Summaries allows you to ‘zoom out’ from the page-level and better understand the big picture of your sites performance.
Desktop and Mobile Page Reports
Best practices for site performance differ greatly between Desktop and Mobile device usage. Configure Insights from Google PageSpeed to generate Desktop reports, Mobile reports, or both!
Toggle back and forth between report types to see specific suggestions for improving the performance and experience on each platform.
The Report Snapshot tool builds on the power of Report Summaries, to provide historical “Point In Time” data about your website.
Take a snapshot of any Report Summary screen to store that data for future retrieval. Add comments to your snapshots to provide additional meaning, such as “Before Installing W3 Total Cache.” Additionally, filter a Report Summary before taking a Snapshot to save a summary of the filtered data.
Snapshot Comparison Tool
The Snapshot Comparison Tool is an amazing utility that lets you visualize side-by-side results from any two similar Report Snapshots.
Take a Report Snapshot before installing new plugins, or before implementing performance recommendations. Take another snapshot when you are finished and compare your results to measure the effect of your changes.
Add/Import Custom URLs
Easily add additional URLs for inclusion in Pagespeed Reports. Even add URLs for non-WordPress sites, even if they are not hosted on your server. URLs can be added manually, or upload a properly formatted XML sitemap to add multiple pages at once.
Custom URLs can be tagged and filtered in Report Summaries. Take Report Snapshots of your Custom URLs just like you would with any other report type.
Scheduled Report Checks
Configure Insights from Google PageSpeed to automatically recheck your site on a Daily, Weekly, Bi-Monthly, or Monthly basis.
With each scan, any new pages or posts will be discovered, and existing reports will be updated to reflect any changes to your site, as well as any changes in the Pagespeed recommendations.
- (v1.x translation) Russian Translation provided by: Ivanka from coupofy.com
- (v1.x translation) Spanish Translation provided by: Ogi Djuraskovic from firstsiteguide.com
- (v1.x translation) Serbian Translation provided by: Ogi Djuraskovic from firstsiteguide.com
Please find the below list of potential issues that you may encounter, and the recommended next steps.
I entered my API Key and saved the Options, but no Reports are showing up in the Report List.
- Google Pagespeed needs to be able to load each page to create its report. Make sure that your pages are publicly accessible over the internet.
- Ensure that your API key is entered correctly, and that you have enabled the “PageSpeed Insights API” from the Google API Console.
- In the Options page, under “Advanced Configuration” there is a checkbox called “Log API Exceptions”. Any API exception that is not caught and handled automatically will be stored for up to 7 days. This log information can be very helpful when diagnosing issues.
Page report checks never finish all of the way, I have to press “Start Reporting” again and again to get it to finish checking all of my pages.
- If the reports seem to always run for a certain length of time before stopping unexpectedly, you may be exceeding your servers Max Execution time. Try increasing the value in Options->Advanced Configuration “Maximum Execution Time”.
- Some web hosting providers do not allow the Maximum Execution Time to be overridden or increased. In that case you can try setting the Maximum Script Run Time. This will make the script run for the set period of time, then stop and spawn a new script, to get around timeout issues. Start with a low value, and test. Increase the value one step at a time until you find the largest value that allows your scans to finish successfully.
An error was reported while trying to check one of my pages, and it has been added to the Ignored Pages section.
- Navigate to the Ignored Pages tab, find the page, and click “reactivate” to try it again.
- If the page fails again, ensure that the page is publicly accessible from the internet. Non-public pages cannot be checked.
- In some rare cases, pages are not able to be scanned by the Pagespeed API. Try checking your page manually here: https://developers.google.com/speed/pagespeed/insights/. If the page fails to be checked, report the issue to Google so that they can diagnose further.
- If the error appeared while Google Pagespeed was checking pages, you may have loaded the page while it was storing data. Refresh the page in a couple seconds to see if the issue has gone away.
- If issues persist please report the problem with as much information as you can gather, including: What page you were on, the exact text of the error, or a screenshot of the error.
- In the Options page, under “Advanced Configuration” there is a checkbox called “Log API Exceptions”. Any API exception that is not caught and handled automatically will be logged for up to 7 days. This log information can be very helpful when diagnosing issues
My Page Scores seem really low. When I click “Recheck Results” when viewing Report Details, the score jumps up dramatically.
- Your server may have been responding slowly when the first report was generated. A slow server response time can have a large impact on your Page Speed Score. If these problems happen frequently you may want to talk with your hosting provider about the problem, or look into alternative hosting providers.
I want to clear out all of the current page reports and start over.
- Navigate to the “Options” tab
- Expand the “Advanced Configuration” section.
- Find the “Delete Data” Dropdown
- Select “Delete Reports Only” to remove all Page Reports
- Or Select “Delete EVERYTHING” to remove all Page Reports, Custom URLs, Snapshots, and Ignored Pages
- Login to your WordPress Admin page (usually http://yourdomain.com/wp-admin)
- Navigate to the Plugins screen and then click the “Add New” button
- Click on the “Upload” link near the top of the page and browse for the Insights from Google PageSpeed zip file
- Upload the file, and click “Activate Plugin” after the installation completes
- Congratulations, installation is complete; proceed to configuration.
An extended version of the folliowing instructions as well as other documentation are included in the “documentation” folder of this plugin.
Google Pagespeed Insights requires a Google API Key. Keys are free and can be obtained from Google. In order to get a key, you will need a Google account such as a GMail account. If you do not already have a Google account you can create one here: https://accounts.google.com/SignUp.
- Navigate to https://console.developers.google.com/
- Login with your Google Account (Create a Google account if you do not have one)
- Create a new API Key and enable the Google Pagespeed Insights API* (see note about restrictions)
- Paste your API Key into the Options page of Insights from Google PageSpeed
- Try first creating the API key without any ‘restrictions’. In my testing there seems to be a bug with using restricitons with the Pagespeed API.
- Google API Key https://console.developers.google.com/
- WordPress 3.6 or Newer
Bijdragers & ontwikkelaars
“Insights from Google PageSpeed” is open source software. De volgende personen hebben bijgedragen aan deze plugin.Bijdragers
- Additional validating, sanitizing, and escaping the plugin codebase
- Bugfix some validation rule reports not showing properly (some results may need to be rechecked to see the fixes)
- Better styling for readability in report details
- Additional validating, sanitizing, and escaping the plugin codebase
- Bugfix improperly escaped data (xss security issue)
- Rename plugin to “Insights from Google PageSpeed”
- Bugfix loading screenshots ‘filmstrip’ images broken
- Bugfix google has introduced a couple new report types that were not handled by JS templating in this plugin. Added support for the new type and also tried to more gracefully handle this issue if/when this happens again in the future.
- Bugfix removed reference to ‘legend’ template file that was deleted in v4.0.0 and was causing PHP warnings
- NOTICE: This upgrade will remove any existing reports or snapshots created by older versions of this plugin as they are not compatible with the newest version of the pagespeed API (v5)
- Migrating to the latest version of the Google Pagespeed Insights API (v5). This comes with pretty big changes to reporting and is incompatible with reports generated from previous versions of the API (and this plugin)
- Replaced the Google API PHP library previously used by this plugin in favor of a much smaller and simpler class
- Bugfix SQL Mutex lock key not unique per installation causing issues when trying to run this plugin on multiple sites sharing the same SQL server
- Fixed PHP warning when saving settings
- Fixed bug where WordPress heartbeat API filter function failed to return properly
- Added additional options for max runtime to support scenarios where even 60 seconds was over the server max run time
- Fixed bug where Maximum Script Run Time option could not be set to “No Limit” after previously being set to a higher value
- Fixed bug introduced in v3.0.1 effecting servers running PHP 5.4 where a PHP error is produced while trying to perform actions in the plugin like saving options
- Added snapshot comments to the view snapshot / compare snapshot templates
- Fixed bug with snapshot report type label reading ‘both’ when it should read either desktop or mobile
- Fixed bug with snapshot report description label not loading translatable string
- Fixed bug preventing snapshot comments from being displayed in snapshots list table
- Improved hardening against authenticated XSS attacks
- Improved adherence to WordPress coding standards and best practices
- Includes all previously “premium” functionality for free. This includes report snapshots, snapshot comparison tool, custom URL reporting, and scheduled report checks.
- Added in URL hotlinking in report details for paths to assets (images/scripts/etc)
- Updating to latest google api php library 2.2.0 to resolve issues with PHP 7.1
- Fixed bug which improperly returned WP Cron schedules on cron_schedules filter
- Removed phpseclib unit tests from Google PHP API library to avoid false-positive with WordFence
- Major rewrite for better compatibility and performance
- Updated to the latest Google Pagespeed Insights API verison and library
- Fixed issues with bulk installers not generating DB tables
- Consolidated scan methods to a single more reliable method inspired by WP cron
- Better identify, communicate, and resolve issues with environments that have difficulties with scanning pages or API errors
- Improved API error logging
- Added ‘abort scan’ functionality to cancel an in-progress scan
- Added ‘Maximum Script Run Time’ option to advanced configuration to allow scans to run in shorter intervals for web hosts which have script timeouts that cannot be overridden
- Update the codebase to adhere better to WordPress coding standards and best practices
- Fixed error with WP_List_Table introduced with WordPress 4.3
- Added Russian translation. Thank you Ivanka from coupofy.com
- Fixed problem with temp directory used by Google API which was not writable on many shared hosting environments, and prevented the plugin from working properly. Replaced sys_get_temp_dir function with WordPress get_temp_dir function to resolve.
- Added Spanish and Serbian translations. Thank you Ogi Djuraskovic from firstsiteguide.com for providing these.
- Added auto-update capability
- Tweaked interactions with WPDB so that it will properly get the table prefix for WordPress multisite installations.
- Tweaked styles to look better in the new WordPress 3.8 admin theme.
- Fixed accidental use of some php shorttags (<? instead of <?php) that was causing activation errors for some. (Thank you bekar09 for first finding this error)
- Tweaked ajax.js for better performance (Thanks to Pippin for the suggestion)
- Tweaked use of get_pages() for better performance (Thanks to Pippin for the suggestion)
- Fixed a number of php notices
- Fixed a potential conflict with other plugins that also utilize the Google API PHP library. The API is now only included if the Google_Client class does not already exist.
- Added additional checking during plugin activation to fail fast if the server does not meet the minimum plugin requirements.
- Initiële release