diff options
Diffstat (limited to 'site/content/docs/5.3/customize/optimize.md')
| -rw-r--r-- | site/content/docs/5.3/customize/optimize.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/site/content/docs/5.3/customize/optimize.md b/site/content/docs/5.3/customize/optimize.md index 2622f88db..fc65628d5 100644 --- a/site/content/docs/5.3/customize/optimize.md +++ b/site/content/docs/5.3/customize/optimize.md @@ -74,7 +74,7 @@ Whenever possible, be sure to compress all the code you serve to your visitors. While minifying and using compression might seem like enough, making your files non-blocking ones is also a big step in making your site well-optimized and fast enough. -If you are using a [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview/) plugin in Google Chrome, you may have stumbled over FCP. [The First Contentful Paint](https://web.dev/fcp/) metric measures the time from when the page starts loading to when any part of the page's content is rendered on the screen. +If you are using a [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview/) plugin in Google Chrome, you may have stumbled over FCP. [The First Contentful Paint](https://web.dev/articles/fcp) metric measures the time from when the page starts loading to when any part of the page's content is rendered on the screen. You can improve FCP by deferring non-critical JavaScript or CSS. What does that mean? Simply, JavaScript or stylesheets that don't need to be present on the first paint of your page should be marked with `async` or `defer` attributes. @@ -82,8 +82,8 @@ This ensures that the less important resources are loaded later and not blocking If you want to learn more about this, there are already a lot of great articles about it: -- <https://web.dev/render-blocking-resources/> -- <https://web.dev/defer-non-critical-css/> +- <https://developer.chrome.com/docs/lighthouse/performance/render-blocking-resources/> +- <https://web.dev/articles/defer-non-critical-css> ## Always use HTTPS |