Pagespeed insights

Google PageSpeed Insights is without a doubt a useful tool for webmasters, developers, và site owners of all types. However, we’ve sầu noticed that a lot of people spover hours obsessing over optimizing their sites, in order khổng lồ try & score 100/100 on this thử nghiệm.

Bạn đang xem: Pagespeed insights


The truth is that this isn’t how Google PageSpeed Insights is meant to lớn be used, nor is it a worthwhile pursuit. When you focus on implementing the platform’s recommendations instead of zeroing in on the number at the top of the page, you’ll be creating a lot more benefits for your site.

This post is a comprehensive guide lớn using Google PageSpeed Insights to your best advantage. We’ll cover how Google uses your score, as well as how lớn incorporate the recommendations you receive sầu.

Let’s get started!


An Introduction to lớn Google PageSpeed Insights

If you’re not yet familiar with Google PageSpeed Insights, it’s a tool used for testing trang web performance. You can enter any URL và have it analyzed:


*

Smartphone tab in Google PageSpeed Insights


Since more than 73 percent of Smartphone internet users clayên they’ve sầu encountered a site that takes too long to load, the information in the Google PageSpeed Insights Mobile tab is invaluable. Using the recommendations here to decrease loading times on smartphones & other devices should give you a competitive edge.

Google PageSpeed Insights Recommendations (24 Ways to lớn Improve sầu Performance)

We’ve sầu talked a lot about Google PageSpeed Insights’ recommendations in this post. They’re the real meat of your performance kiểm tra results, & far more valuable than your actual score. That’s why we’ve dedicated the rest of this post to lớn them.

Before we dive sầu into the individual suggestions, however, you’ll need lớn understvà the difference between your Field Data và Lab Data. The former compares your site lớn others in the Chrome User Experience Report for the last 30 days.

There are also two charts that show where your average First Contentful Paint (FCP) và First Input Delay (FID) fall:


*

Google PageSpeed Insights Lab Data


You’ll notice that our Field Data và Lab Data don’t match exactly. That’s perfectly normal. The Lab Data is created under fixed conditions, while the Field Data uses actual loading speeds collected over time.

When looked at in combination, the Field Data & Lab Data should give you an idea of your site’s actual loading times. As we mentioned earlier, this is even more important than your overall PageSpeed score, so you’ll want to lớn pay attention to lớn these numbers.

After you’ve sầu considered this information, it’s time khổng lồ start improving your site’s performance with Google PageSpeed’s recommendations.

1. Eliminate Render-Blocking Resources

One of the more common recommendations from Google PageSpeed Insights is lớn Eliminate render-blocking resources:


*

Eliminate render-blocking resources recommendation


This is referring lớn JavaScript & CSS scripts that are preventing your page from loading quickly. The visitor’s browser has khổng lồ download & process these files before it can display the rest of the page, so having a lot of them ‘above sầu the fold’ can negatively impact your site’s speed.

You can learn more about this issue in our guide lớn eliminating render-blocking scripts. As far as Google is concerned, there are two solutions you should consider:

You’ll find a danh sách of the resources that are most affected by this issue below the recommendation in your PageSpeed results.

Check out this đoạn Clip khổng lồ find out more about how lớn eliminate render-blocking resources:

2. Avoid Chaining Critical Requests

The concept of chaining critical requests has khổng lồ bởi vì with the Critical Rendering Path (CRP) and how browsers load your pages. Certain elements – such as the JavaScript và CSS we discussed above sầu – must be loaded completely before your page becomes visible.

As part of this suggestion, Google PageSpeed Insights will show you the request chains on the page you’re analyzing:


*

Avoid chaining critical requests recommendation


This diagram will show you the series of dependent requests that must be fulfilled before your page becomes visible. It will also tell you the kích thước of each resource. Ideally, you want khổng lồ minimize the number of dependent requests, as well as their sizes.

Several methods for accomplishing these goals are covered by other recommendations discussed in this post, including:

Eliminating render-blocking resourcesDeferring offscreen imagesMinifying CSS and JavaScript

Additionally, you can optimize the order in which assets load, in order to shorten the CRPhường. This means moving above-the-fold content to the top of your HTML file. You can learn more about optimizing the CRPhường in our post, “How lớn Optimize the Critical Rendering Path in WordPress”.

It’s important to note that there’s not a magic number of critical request chains that you need lớn work down to lớn. Google PageSpeed Insights doesn’t count this audit as ‘passed’ or ‘failed’, unlike many of its other recommendations. This information is simply made available to help you improve loading times.

3. Keep Request Counts Low và Transfer Sizes Small

The more requests browsers have sầu to make khổng lồ load your pages, và the larger the resources your hệ thống returns in response, the longer your trang web takes khổng lồ load. Therefore, it makes sense that Google would recommover that you minimize the number of required requests and decrease the size of your resources.

Like the Avoid chaining critical requests recommendation, this one does not result in a ‘pass’ or ‘fail’. Instead, you’ll simply see a menu of the number of requests made và their sizes:


*

Keep request counts low and transfer sizes small recommendation


There’s no ikhuyến mãi number of requests or maximum sizes lớn keep in mind. Instead, Google recommends that you phối those standards for yourself by creating a performance budget. This is a mix of defined goals that may be related to lớn aspects such as:

Maximum image sizesThe number of web fonts usedHow many external resources you Call toThe form size of scripts & frameworks

Creating a performance budget gives you a mix of standards khổng lồ hold yourself accountable lớn. When you go over your budget, you can then make decisions about whether khổng lồ eliminate or optimize resources to stichồng lớn your predetermined guidelines. You can learn more about creating one in Google’s own guide.

4. Minify CSS

CSS files are often larger than they need to lớn be, in order to lớn make them easier for humans to read. They might include various carriage returns & spaces that aren’t necessary for computers khổng lồ understvà their contents.

Minifying your CSS is the process of condensing your files by eliminating unnecessary characters, spaces, và duplications. Google recommends this practice because it reduces your CSS file sizes, and therefore can improve loading speed:


*

Minify CSS recommendation


We recommkết thúc using a plugin such as Autoptimize or WP.. Rocket to lớn minify your CSS files.

5. Minify JavaScript

Just as you can reduce CSS tệp tin kích thước through minification, the same applies to your JavaScript files:


*

Minify JavaScript recommendation


Autoptimize or WP Rocket can handle this task for your WordPress site as well.

6. Remove sầu Unused CSS

Any code in your stylesheet is nội dung that has lớn be loaded in order for your page to lớn become visible khổng lồ users. If there’s CSS on your site that isn’t actually useful, it’s putting an unnecessary drain on your performance.


Sign Up For the Newsletter


*

Remove unused CSS recommendation


The solution here is essentially the same as that for eliminating render-blocking CSS. You can inline or defer styles in whatever way makes the most sense for your pages. You can also use a tool such as Chrome DevTools lớn find unused CSS that needs lớn be optimized.

7. Minimize Main-Thread Work

The ‘main thread’ is the primary element of a user’s browser that’s responsible for turning code into lớn a web page that visitors can interact with. It parses & executes HTML, CSS, & JavaScript. Additionally, it’s in charge of handling user interactions.

This means that, when the main thread is working through your site’s code, it cannot also handle user requests. If your site’s main-thread work takes too long, this can result in poor UX and slow page loading times.

Google PageSpeed will flag pages that take longer than four seconds lớn complete main-thread work and present a usable website page:


*

Minimize main-thread work recommendation


Some of the methods used for reducing main-thread work have sầu already been covered in other sections of this post, including:

Minifying your codeRemoving unused codeImplementing caching

However, you may also want khổng lồ consider code splitting. This process involves breaking up your JavaScript inkhổng lồ bundles that exedễ thương when they’re needed, instead of requiring browsers lớn load all of them before the page becomes interactive.

Webpaông xã is often used khổng lồ implement code splitting. lưu ý that this is a fairly advanced technique and beginners should usually undertake alone.

8. Reduce JavaScript Execution Time

JavaScript execution is often the most prominent contributor to lớn main-thread work. PageSpeed Insights has a separate recommendation khổng lồ alert you if this task is having a significant impact on your site’s performance:


*

Reduce JavaScript execution time recommendation


The methods suggested above sầu for reducing main-thread work should also resolve this warning in your PageSpeed results.

9. Reduce Server Response Times (TTFB)

Time lớn First Byte (TTFB) is a measure of how long it takes for a browser lớn receive the first byte of data baông xã from your site’s VPS after making a request. While this isn’t the same as your overall site tốc độ, having a low TTFB is understandably good for your site’s performance.

Therefore, reducing VPS response times is among mỏi Google PageSpeed Insights’ recommendations. If you’re able to achieve sầu a low TTFB, you’ll see this message under Passed audits:


*

Server response times are low message


There are several factors that can influence your TTFB. Some strategies for lowering it include:

Using lightweight themes and pluginsReducing the number of plugins installed on your siteUtilizing a Content Delivery Network (CDN)Implementing browser cachingSelecting a solid Domain Name System (DNS) provider

Our post on TTFB is an excellent resource for more details on optimization in this area.

10. Properly Size Images

Media files such as images can be a real drag on your site’s performance. Properly sizing them is a simple way lớn reduce your loading times:


*

Properly size images recommendation


If your page includes images that are larger than they need khổng lồ be, CSS is used khổng lồ rekích thước them appropriately. This takes longer than simply loading the images at the right size initially, therefore impacting your page’s performance.

To fix this, you can either upload images at the proper sizes, or use ‘responsive sầu images’. This involves creating differently-sized images for various devices.

You can vày this using the srcset attribute, which is added to

*
The srcset attribute specifies the different available files, và the sizes attribute tells browsers which one should be used based on the current screen form size.

11. Defer Offscreen Images

The process of deferring offscreen images is more commonly known as ‘lazy loading’. This means that instead of making the browser load every image on a page before displaying the above-the-fold nội dung, it will only load the ones that are immediately visible.

Less loading before the page becomes visible means better performance, which is why Google recommends this method:


*

Defer offscreen images recommendation


There are several WordPress plugins made specifically for lazy loading, including a3 Lazy Load and Lazy Load by WPhường Rocket. Various image & performance optimization plugins such as Autoptimize also have lazy loading features. Chechồng out our complete guide on Lazy Loading Images and Videos on WordPress.

12. Efficiently Encode Images

As we mentioned earlier in this post, images have a significant impact on your site’s performance. One of the most basic optimization best practices you may want khổng lồ consider is compression, which can help reduce your file sizes so they’ll load faster. It’s also the primary method for following Google’s recommendation lớn Efficiently encode images:


*

Efficiently encode images recommendation


The key is achieving the smallest possible tệp tin sizes, without sacrificing the unique of the images themselves. Plugins such as Imagify và Smush can help with this task. You can learn more about them in our guide lớn image optimization.

Other recommendations that influence whether you ‘pass’ or ‘fail’ the Efficiently encode images audit include:

Serving images at the correct sizeImplementing lazy loading (deferring offscreen images)Converting images khổng lồ next-gene tệp tin formats, such as WebPUsing video formats for animated content, such as GIFs

In addition khổng lồ compressing your images, you can follow the steps for fulfilling these suggestions as described elsewhere in this post.

13. Serve Image in Next-Gen Formats

There are some image file formats that load more quickly than others. Unfortunately, they’re not your commonly-seen PNG or JPEG formats. WebP images are becoming the new standard, and Google PageSpeed will inkhung you if your images aren’t adhering to lớn it:


*

Serve sầu images in next-gene formats recommendation


This may seem lượt thích a hard recommendation to lớn meet, since you likely already have sầu plenty images on your WordPress site. Fortunately, there are plugins that can help. For example, Imagify & Smush both offer a WebP conversion feature.

14. Use Video Formats for Animated Content

GIFs can be an effective sầu khung of visual content in a variety of situations. Tutorial walkthroughs, feature reviews, & even humorous animations can all elevate your posts and make them more enjoyable & valuable to lớn readers.

Xem thêm: Cách Làm Hoa Trang Trí Tường Xinh Xắn, Hướng Dẫn Làm Hoa Giấy Treo Tường

Unfortunately, those benefits come at a cost lớn your performance. GIFs are demanding khổng lồ load, which is why PageSpeed Insights recommends serving video clip nội dung instead:


*

Use video formats for animated nội dung recommendation


Unfortunately, converting GIFs to Clip formats isn’t the most straightforward of processes. First, you’ll have lớn decide which type of đoạn Clip you want to lớn use:

WebM: The most highly-optimized video clip format, although it has limited browser compatibility.

Once you’ve sầu made the choice that makes the most sense for your site, you’ll need lớn convert the file formats. The best way khổng lồ do this is via the commvà line. To get started, install FFmpeg. This is an open-source tool for converting tệp tin formats:


*

FFmpeg file format conversion tool for video clip và audio


Then, open your command line interface and run the following command:

ffmpeg -i input.gif output.mp4This will convert the GIF with the file name input.gif into lớn an MP4 đoạn phim with the tệp tin name output.mp4. Changing the format is just the beginning, however. You now need to lớn embed the resulting video clip on your WordPress site in a way that makes it appear like an animated GIF.

Embedding Video Content for Animations

As you’ve likely noticed if you’ve sầu ever seen a GIF before, they’re slightly different from normal videos. They usually autoplay và run on a loop, & they’re always without sound. Embedding your new MP4 or WebM file on your WordPress site won’t produce these features.

However, you can recreate them with some very simple code. Upload your video clip lớn your truyền thông library, & then add the following khổng lồ the page or post where you want lớn include your GIF:

This will apply the specified attributes khổng lồ your video clip, making it appear more ‘GIF-like’. Simply adapt the file name và type to lớn match that of your resource. For more details on this subject, we suggest reading Google’s guide on converting GIFs to videos.

15. Ensure Text Remains Visible During Webfonts Load

Like images, fonts tover to lớn be large files that take a long time to lớn load. In some cases, browsers may hide your text until the fonts you’re using loads completely, which will result in this recommendation from Google PageSpeed Insights:


*

Ensure text remains visible during webfont load recommendation


Google advises you resolve this issue by applying the Font Display API swap directive sầu in your
font-face
 style. To vị this, access your stylesheet (style.css) and add the following after the src attribute under
font-face
:

font-display: swap

You can learn more about optimizing web fonts in our post “How to Change Fonts In WordPress” & our in-depth guide to lớn hosting local fonts.

16. Enable Text Compression

Google PageSpeed Insights’ Enable text compression recommendation refers khổng lồ the use of GZIP.. compression:


*

Enable text compression recommendation


In some cases (as you can see in the image above) text compression will be enabled on your hệ thống automatically. If this is not the case for your site, you have a couple of options for following this recommendation.

The first is lớn install a plugin with a GZIPhường. compression feature. WPhường Rocket is a viable solution if you’re willing lớn pay for it.

You can also compress your text manually. This involves editing your .htaccess file, which can be risky, so make sure you have sầu a recent backup on h&.

Most WordPress sites run on Apabịt servers. The code for enabling GZIP.. compression looks lượt thích this:

# Compress HTML, CSS, JavaScript, Text, XML and fonts AddOutputFilterByType DEFLATE application/javascript AddOutputFilterByType DEFLATE application/rss+xml AddOutputFilterByType DEFLATE application/vnd.ms-fontobject AddOutputFilterByType DEFLATE application/x-font AddOutputFilterByType DEFLATE application/x-font-opentype AddOutputFilterByType DEFLATE application/x-font-otf AddOutputFilterByType DEFLATE application/x-font-truetype AddOutputFilterByType DEFLATE application/x-font-ttf AddOutputFilterByType DEFLATE application/x-javascript AddOutputFilterByType DEFLATE application/xhtml+xml AddOutputFilterByType DEFLATE application/xml AddOutputFilterByType DEFLATE font/opentype AddOutputFilterByType DEFLATE font/otf AddOutputFilterByType DEFLATE font/ttf AddOutputFilterByType DEFLATE image/svg+xml AddOutputFilterByType DEFLATE image/x-ibé AddOutputFilterByType DEFLATE text/css AddOutputFilterByType DEFLATE text/html AddOutputFilterByType DEFLATE text/javascript AddOutputFilterByType DEFLATE text/plain AddOutputFilterByType DEFLATE text/xml # Remove browser bugs (only needed for really old browsers) BrowserMatch ^Mozilla/4 gzip-only-text/html BrowserMatch ^Mozilla/4.0<678> no-gzip BrowserMatch MSIE !no-gzip !gzip-only-text/html Header append Vary User-AgentYou should add it after #END in your .htaccess file. If you happen to lớn have sầu your WordPress site on an Nginx VPS, you should add the following code to your nginx.conf tệp tin instead:

36 gzip on;37 gzip_disable "MSIE <1-6>.(?!.*SV1)";38 gzip_vary on;39 gzip_types text/plain text/css text/javascript application/javascript application/x-javascript;If you’d like khổng lồ check your site’s text compression, we suggest using a tool such as GiftOfSpeed:


*

GiftOfSpeed GZIP compression check


This will let you know if GZIP compression has been successfully implemented, as well as what type of VPS your site is running on and a few other key details.

17. Preconnect to lớn Required Origins

Chances are high that you probably have sầu at least one third-tiệc ngọt resource on your site – Google Analytics is a common example. It can take time for browsers to establish a connection khổng lồ these resources, slowing down your loading speeds.

Using preconnect attributes can tell browsers right away that there are third-các buổi tiệc nhỏ scripts on your page that need to lớn be loaded. The process of requesting them can then initiate as soon as possible, improving your performance.

If Google feels that your page could benefit from this technique, you’ll see the Preconnect to lớn required origins suggestion:


*

Preconnect khổng lồ required origins recommendation


There are a few ways to lớn go about implementing this optimization strategy. If you’re comfortable with editing your WordPress theme files, you can add a liên kết tag khổng lồ your header.php tệp tin. Here’s an example:

In this case, the tag tells browsers that they need lớn establish a connection lớn example.com as quickly as possible. Google PageSpeed Insights will các mục any relevant resources for which you should add links tags with preconnect attributes.

The other option is to lớn use a plugin to lớn achieve sầu the same effect. Perfmatters includes a preconnect feature (disclaimer: I’m one of the founders of Perfmatters). WPhường Rocket & Pre* Party Resource Hints include similar functionality.

18. Preload Key Requests

Similar to the Preconnect lớn required origins recommendation, following this suggestion enables you lớn minimize the number of requests browsers must make to lớn your site’s hệ thống. Rather than connecting to third-các buổi party resources, however, Preload key requests refers khổng lồ loading critical assets on your own server:


*

Preload key requests recommendation


Implementing this technique is very similar to the previous recommendation as well. You can add link tags specifying the resources listed in PageSpeed Insights to lớn your header.php file:

You can also incorporate this tag using Perfmatters, WPhường Rocket, or Pre* Party Resource Hints.

19. Avoid Multiple Page Redirects

Redirects are used when you want one URL khổng lồ point to lớn another. They’re commonly employed when you move sầu or delete a page on your site. While there’s nothing wrong with using redirects in general, they do cause additional delays in loading time.

If you have too many redirects on your site, you may see this recommendation in Google PageSpeed Insights:


*

Avoid multiple page redirects recommendation


The only thing you can vày in response to this recommendation is to lớn make sure you’re only using redirects when you absolutely have sầu to. You can learn more about the process of creating them in our post, “WordPress Redirect – Best Practices for Better Performance”.

20. Serve sầu Static Assets With an Efficient Cabịt Policy

If you’ve been using Google PageSpeed Insights for a while, you might know this recommendation better as the Leverage browser caching warning. In Version 5, it’s now labeled as Serve sầu Static Assets With an Efficient Cabịt Policy:


This suggestion has a few layers we need lớn piece through. The first is what ‘caching’ means. In short, it’s a process in which browsers save sầu copies of your pages, so they can be loaded faster on future visits.

The most common way WordPress sites implement caching is with plugins. WP. Rocket and W3 Total Cađậy are popular options. However, some hosting providers – including us here at ruby-forum.org – enable caching via their servers. Make sure khổng lồ kiểm tra và see if this is the case for your host before you install a caching plugin.

Sit baông xã, relax, & increase your page speed—we take care of WordPress caching so you don’t have khổng lồ. Try ruby-forum.org for Free.


"}" data-sheets-userformat=""2":6659,"3":"1":0,"4":"1":2,"2":16777215,"12":0,"14":"1":2,"2":0,"15":"Robolớn, RobotoDraft, Helvetica, Arial, sans-serif"">

Sit baông xã, relax, and increase your page speed—we take care of WordPress caching so you don’t have to lớn. Try ruby-forum.org for Free.


Once you’ve enabled caching for your site, you can worry about the second part of this recommendation, which is your cache policy’s ‘efficiency’. Browsers clear their caches periodically khổng lồ refresh them with updated copies.

Ideally, you want this time period khổng lồ be higher rather than lower. If you’re clearing your site from browser caches every couple of hours, that defeats the purpose of using this technique in the first place. You can optimize your cabít expiration period using Cache-Control & Expires headers.

Adding Cache-Control Headers

Use the following code to add Cache-Control headers in Nginx:

location ~* .(js|css|png|jpg|jpeg|gif|svg|ico)$ expires 30d; add_header Cache-Control "public, no-transform";You should add this khổng lồ your server’s configuration tệp tin. In the above example, the specified file types are phối khổng lồ expire after 30 days.

Those with Apache servers should use this snippet in their .htaccess files instead:

Header mix Cache-Control "max-age=84600, public"Add this code before #BEGIN WordPress or after #END WordPress. In this example, the cađậy expiration period is phối to 84,600 seconds.

Adding Expires Headers

Cache-Control headers are pretty much the standard now. However, there are some tools (including GTMetrix) that still kiểm tra for Expires headers.

You can add expires headers to a Nginx hệ thống by incorporating the following inkhổng lồ your server block:

location ~* .(jpg|jpeg|gif|png|svg)$ expires 365d; location ~* .(pdf|css|html|js|swf)$ expires 2d; You should mix different expiration times based on file types. Apabịt servers will produce the same results if you add this code khổng lồ your .htaccess file:

## EXPIRES HEADER CACHING ##ExpiresActive sầu OnExpiresByType image/jpg "access 1 year"ExpiresByType image/jpeg "access 1 year"ExpiresByType image/gif "access 1 year"ExpiresByType image/png "access 1 year"ExpiresByType image/svg "access 1 year"ExpiresByType text/css "access 1 month"ExpiresByType application/pdf "access 1 month"ExpiresByType application/javascript "access 1 month"ExpiresByType application/x-javascript "access 1 month"ExpiresByType application/x-shockwave-flash "access 1 month"ExpiresByType image/x-ibé "access 1 year"ExpiresDefault "access 2 days"## EXPIRES HEADER CACHING ##Once again, you should add this code either before #BEGIN WordPress or after #END WordPress.

Efficient Caching of Google Analytics

Ironically, the Google Analytics script you may have sầu added khổng lồ your pages’ headers in order lớn traông chồng user behavior has a cabít expiration period of just two hours. This is likely so that, if updates are made to lớn the platform, users will have sầu access to lớn the changes quickly.

This script will appear in the danh sách of resources requiring your attention under the Serve sầu static assets with an efficient cabít policy recommendation. Since it belongs lớn a third buổi tiệc nhỏ, you can’t change the expiration period with Cache-Control or Expires headers.

If this is the only script listed under this recommendation, you can still pass the audit:


However, as we’ve sầu noted throughout this post, your PageSpeed score matters less than your actual & perceived performance. In order lớn serve this resource efficiently, you may consider hosting Google Analytics locally.

Plugins like Complete Analytics Optimization Suite (CAOS) and Perfmatters will enable you khổng lồ vày this. You can read more about the process in our complete guide to this PageSpeed suggestion.

21. Reduce the Impact of Third-Party Code

We’ve sầu now mentioned a few different ways in which third-các buổi party scripts can negatively impact your performance, and result in failed audits from PageSpeed Insights. Ideally, it’s best khổng lồ limit your reliance on these tools in order to lớn prevent adverse effects.

However, in some cases the best solution lớn a need your site has is to incorporate a third-tiệc ngọt script. Google Analytics is an excellent example. Others include:

YouTube video clip embedsLibraries for JavaScript, fonts, & other elements

In cases where you deem the use of a third-các buổi tiệc nhỏ script necessary, it’s important to still reduce its impact on your site’s performance, as your PageSpeed analysis results will tell you:


To load third-các buổi tiệc nhỏ code more efficiently, you can consider one of the techniques we’ve sầu already mentioned in this post:

Defer the loading of JavaScriptUse link tags with preconnect attributesSelf-host third-các buổi party scripts (as we described with Google Analytics above)

These methods should minimize the impact on your site’s performance.

22. Avoid Enormous Network Payloads

This recommendation is particularly relevant to your thiết bị di động visitors. Large payloads can require the use of more cellular data, thereby costing your users money. Minimizing the number of network requests needed khổng lồ reach your pages can prevent this:


Google recommends keeping your total byte size to 1,600 KB or less. The methods most commonly used lớn achieve this goal are found throughout this post, including:

Deferring CSS, JavaScript, and images that are below the foldMinifying codeCompressing image filesUsing the WebP format for imagesImplementing caching

Follow the relevant steps for these strategies, và you should pass this audit without any additional effort.

23. User Timing Marks và Measures

This recommendation is only relevant if you’re using the User Timing API. This tool creates timestamps to help you evaluate your JavaScript’s performance. If you’ve phối up the API for your site, you’ll see your marks & measures under this heading in PageSpeed Insights:


As you can see, this is another suggestion from Google that doesn’t result in a ‘pass’ or ‘fail’. PageSpeed Insights simply makes this information easily retrievable, so you can use it to lớn assess areas that may require optimization.

If you’re interested in incorporating the User Timing API into your WordPress site, you can learn more in the Mozilla guide on the topic.

24. Avoid an Excessive sầu Document Object Model (DOM) Size

In simplest terms, the DOM is how browsers turn HTML inkhổng lồ objects. It involves the use of a tree-structure made up of individual nodes that each represent an object. Naturally, the larger your page’s DOM is, the longer it will take to load.

Xem thêm: Phần Mềm Gọi Điện Thoại Miễn Phí Trên Điện Thoại, Talku: Gọi+Nhắn Tin Thỏa Thích

If your page exceeds certain standards regarding DOM form size, it will recommend reducing the number of nodes as well as the complexity of your CSS styling:


A common culprit if you’ve ‘failed’ this audit in PageSpeed Insights is your WordPress theme. Heavy themes often add large volumes of elements lớn the DOM, and may also include convoluted styling that slows your site down. If this is the case, you may need khổng lồ switch themes.

Are you struggling lớn score 100/100 on #Google PageSpeed? Here"s a tip: don"t obsess over your score and focus on what"s truly affecting your page load!
Chuyên mục: SEO