How quickly the contents of a page are visually loaded, in milliseconds. A plugin such as Async JavaScript or WP Rocket can be helpful here.įor more information, see first contentful paint in Google’s references.Eliminate Render-blocking Javascript and reduce JavaScript load.Minify and compress text-based assets to speed up their download time.Improve cacheability to speed up repeat visits.Utilize a CDN (content delivery network) and reduce TTFB (time to first byte).This can be done with a plugin like WP Rocket.Minimize the number of render-blocking external stylesheets and scripts.This is important because it confirms to the user the page is actually loading. The amount of time until the first item is visually loaded. The audits, listed lower on Google Pagespeed Insights, do not directly influence this score, however there are suggestions around each area that may help improve scores overall in more detail below. Your website may not have any Field data if the page has not received ample traffic yet and it’s okay for these values to not match up exactly, as they were collected under different conditions. It is best to simply click the suggestion in Google Pagespeed Insights for more relevant information as to how to address it.įor a full list of audits, refer to Google’s “Lighthouse” reference guide.įield data is data collected over time for the page and Lab data is data collected under a fixed set of conditions. Passed Audits – Audits the page has successfully passed.Īs there are dozens of insights available under these 3 groups.Diagnostics – Extra information around best practices.Opportunities – Suggestions to improve metrics, with an estimated load time savings.These values do not directly impact the Performance Score, but rather are suggestions based on algorithms. There are an extensive number of audits PageSpeed Insights performs that can be broken down into 3 groups. It’s best to review all of the recommendations Google provides, then implement all of the changes possible. No audit directly impacts the overall Performance Score, which means you cannot focus one or two audits and expect to see any real change. These recommendations usually come back to a few categories: database, code, media, and assets. Improving your Google PageSpeed scores typically requires optimizations be made across the board. We recommend placing less weight on the high-level Performance score, and largely focusing instead on the individual audit recommendations. Instead, think of the PageSpeed insights tool as a guide for what Google thinks will improve your site performance by adhering to the newest generation metrics, and not as the final say on overall performance. Many pages may never be able to receive a perfect score due to the specific needs or configuration. A website can score perfectly on Pagespeed Insights, and yet still be largely unsatisfactory to the needs of your visitors. Pagespeed Insights is designed as a series of guidelines (or “insights”), targeted around meeting specific standards that Google has deemed important for current and future readiness. Any green score (90-100) is considered Good, yellow score (50-89) is considered Average, any red score (0-49) is considered Poor. However, it’s important to understand what the score means in terms of your business, alongside performance reports from a variety of other locations. Many people strive for a perfect 100/100 score on Google, whether it’s because a client demands it or because Google largely governs SEO so Google’s tool appears to hold more weight. Therefore a newer device, on a fast network, may not see your website the same way PageSpeed Insights reports. The test leverages a mid-tier device on a mobile network, meaning it tests your site for performance from a single device and fixed set of network conditions. Google PageSpeed Insights can be used when benchmarking page performance, however we do not recommend using it as your only speed test. Having a more complete picture of a web page arms your team with enough information to target and correct issues efficiently across more browsers, more devices and more users. Some common examples include, Pingdom, and Google PageSpeed Insights. We recommend using a combination of services as they will test from a variety of locations and server types, helping to build a more complete picture of a website’s performance. As we discussed in “ Optimizing WordPress for Speed and Performance”, one of the first steps to make a site faster is to measure how the site is currently performing. Benchmarking pagespeed is a great way to determine the efficacy and performance of your WordPress website.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |