Insights from Google PageSpeed
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 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. Report Snapshots 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. Additional Languages (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 Troubleshooting 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. I received a Javascript or PHP error. 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
Top keywords
- page23×2.00%
- report23×2.00%
- reports14×1.22%
- pages13×1.13%
- pagespeed13×1.13%
- google11×0.95%
- api9×0.78%
- time9×0.78%
- google pagespeed8×0.69%
- performance8×0.69%
- snapshot8×0.69%
- urls8×0.69%
Asset CleanUp
WordPress themes and plugins often load CSS and JavaScript on pages that do not use them. A contact form may load on the homepage, a slider may load on a plain article, or store-related files may load outside the shop. Asset CleanUp shows you what each page loads and lets you unload what is not needed. This can reduce HTTP requests, page weight, and browser work while complementing your existing caching setup. Use Test Mode to validate changes as an administrator before they affect visitors. Asset CleanUp gives you precise, testable control over every optimization. A safer workflow, without giving up control The Dashboard keeps the technical detail experienced users need while guiding first-time users through Getting Started, Test Mode, and the central Overview page. Test changes before they affect visitors, then review and manage existing or leftover rules from one place. CSS and JavaScript management View loaded stylesheets and scripts, organized by their source. Unload unnecessary CSS and JavaScript on the homepage and on individual posts, pages, and custom post types. Manage assets from the Dashboard, the post/page edit screen, or the front-end view. Review unload rules, exceptions, asset attributes, page options, and leftover entries from the Overview page. Minify and combine supported CSS and JavaScript, including supported inline code. Preload selected CSS and JavaScript files when they need to be discovered earlier. Granular manual Critical CSS management Add, edit, and remove your own Critical CSS directly from the Dashboard. Keep manual CSS organized by supported page context instead of maintaining one large global block. Asset CleanUp does not automatically generate Critical CSS. It gives you a structured way to manage CSS that you prepare yourself. Fonts and resource loading Combine, preload, asynchronously load, or remove Google Fonts requests, with font-display and preconnect controls. Preload local font files and apply font-display. Add fetchpriority, loading, and decoding attributes to images using simple matching or regular expressions. Lazy-load images where appropriate. WordPress cleanup options Remove unused WordPress features such as Emojis, Dashicons for guests, and Comment Reply. Remove selected discovery links, metadata, and oEmbed resources from the document HEAD. Disable RSS feed links or feeds when they are not needed. Restrict or disable XML-RPC when your site does not rely on it. Strip supported HTML comments, with exceptions where required. Works with your caching setup, it does not replace it Asset CleanUp is not a page-caching plugin. It controls what WordPress outputs; a page cache, server cache, or CDN can then store and deliver the optimized result. After changing rules, clear every active cache layer. Avoid enabling the same minify or combine feature in multiple optimization plugins at the same time. Asset CleanUp Lite and Pro Lite includes page-level asset management, Test Mode, manual Critical CSS for supported contexts, resource-loading controls, and WordPress cleanup options. Go beyond individual CSS and JavaScript files with the Plugins Manager. Lite includes an interactive preview of the Plugins Manager (rules can be explored, but saved only in Pro). In Pro, it can prevent entire plugins from running on frontend or Dashboard pages where they are not needed, not merely remove their CSS and JavaScript. This can reduce PHP work, database queries, and potential conflicts before the page is generated. Asset CleanUp Pro also adds broader conditional rules, hardcoded asset management, device-specific rules, and advanced JavaScript attribute and placement controls. Documentation and support Read the Asset CleanUp documentation. Ask a question in the WordPress.org support forum. External Services and Privacy WordPress.org plugin icon service When an authorized administrator opens an Asset CleanUp Dashboard screen and the local plugin-icon cache is missing or incomplete, Asset CleanUp may request public plugin information from https://api.wordpress.org/plugins/info/1.2/. The request is used only to retrieve icons for active plugins displayed inside Asset CleanUp. It can include the corresponding WordPress.org plugin slugs and standard HTTP metadata, including the server IP address. Asset CleanUp does not intentionally include the site URL, administrator details, or site content. See the WordPress.org Privacy Policy. Google Fonts preload audit When an authorized administrator explicitly runs the Google Fonts preload audit, Asset CleanUp may request discovered Google Fonts stylesheets from https://fonts.googleapis.com/ and process font-file URLs from https://fonts.gstatic.com/. Requests can include the stylesheet URL and its font-family, variant, subset, or text parameters; the browser user-agent used by the audit; and standard HTTP metadata, including the server IP address. These requests are made only as part of the administrator-initiated audit. See the Google Privacy Policy. The following two Asset CleanUp-operated services are optional. Both are disabled by default and require an administrator to opt in from Asset CleanUp > Settings > Plugin Usage Preferences. Dashboard announcements When an administrator explicitly enables announcements, Asset CleanUp periodically requests the Asset CleanUp Lite announcements feed. The feed is used to show maintenance information, important update notices, optimization guides, and occasional product offers in the WordPress Dashboard. Asset CleanUp does not intentionally add the site URL, administrator details, or site content to this request. As with any HTTP request, the service receives the server IP address and standard HTTP metadata. When announcements are disabled, this feed is not requested. Optional usage tracking When an administrator explicitly enables usage tracking, Asset CleanUp sends an initial technical check-in and then no more than one check-in per week to the Asset CleanUp usage-tracking endpoint. The payload can include the PHP, WordPress, and Asset CleanUp versions; Asset CleanUp settings; first-use and review-notice state; server software; multisite status; the active theme name and version; active and inactive plugin file identifiers; and the WordPress locale. The site URL, administrator name, and administrator email are not intentionally included in the tracking payload. Disabling the setting stops future check-ins. The announcements and usage-tracking services are operated by the Asset CleanUp developer. See the privacy policy. CloudFront infrastructure is provided by Amazon Web Services and is also subject to the AWS Privacy Notice.