Insights from Google PageSpeed vs Lazy Load for Comments

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

Comments are heavy. A long thread can pull in dozens of avatars, gravatar lookups and reply scripts — all of which the browser downloads before the visitor has even reached them. Lazy Load for Comments defers all of that until the visitor either scrolls to the comments area or clicks a button. The result: fewer HTTP requests, faster Largest Contentful Paint and a happier Lighthouse score, without changing how your comment template looks. Version 2.0 is a complete rewrite. It uses the WordPress REST API to fetch the rendered comments on demand and works with both classic themes (comments_template()) and block themes (the core Comments block) out of the box. Features Lazy-load comments on scroll, on button click, or turn the plugin off without deactivating it. Works with classic themes and block themes (the core Comments block). Loads comments inline for search engine crawlers, so indexing and SEO are not affected. Per-post cache of the rendered Comments block — REST renders stay fast. Minimum-comment-count threshold so short threads still render inline. Customisable load-button text, style and extra CSS classes. Clean React settings page under Comments → Lazy Load. No jQuery dependency. Front-end script is vanilla JS and intentionally small. Translation-ready. Hooks and filters available for further customisation. Useful links Plugin website Documentation Support forum