Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Metrics
First Contentful Paint
6.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
11.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
1,070 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.1
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
8.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
Show audits relevant to:
Diagnostics
Minimize main-thread work 2.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category | Time Spent |
---|---|
Script Evaluation | 1,247 ms |
Other | 936 ms |
Rendering | 302 ms |
Style & Layout | 178 ms |
Parse HTML & CSS | 20 ms |
Script Parsing & Compilation | 17 ms |
Largest Contentful Paint element 10,950 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element |
---|
Do better web tester page <h2 id="toppy" style="background-image:url('');"> |
Phase | % of LCP | Timing |
---|---|---|
TTFB | 0% | 10 ms |
Load Delay | 73% | 7,960 ms |
Load Time | 27% | 2,920 ms |
Render Delay | 1% | 60 ms |
Properly size images Potential savings of 456 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.FCPLCP
Upload images directly through the media library to ensure that the required image sizes are available, and then insert them from the media library or use the image widget to ensure the optimal image sizes are used (including those for the responsive breakpoints). Avoid using
Full Size
images unless the dimensions are adequate for their usage. Learn More.URL | Resource Size | Potential Savings | |
---|---|---|---|
localhost 1st party | 550.3 KiB | 456.2 KiB | |
body > img <img src="lighthouse-1024x680.jpg?iar1" width="120" height="15"> | /dobetterweb/lighthouse-1024x680.jpg?iar1 (localhost) | 110.1 KiB | 109.2 KiB |
body > img <img loading="lazy" src="lighthouse-1024x680.jpg?iar2" width="120" height="80" fetchpriority="low"> | /dobetterweb/lighthouse-1024x680.jpg?iar2 (localhost) | 110.1 KiB | 105.4 KiB |
body > img <img src="lighthouse-1024x680.jpg?isr2" width="120" height="80" style="position: absolute;"> | /dobetterweb/lighthouse-1024x680.jpg?isr2 (localhost) | 110.1 KiB | 105.4 KiB |
body > img <img src="lighthouse-1024x680.jpg?isr3" width="360" height="240" style="image-rendering: pixelated; position: absolute;"> | /dobetterweb/lighthouse-1024x680.jpg?isr3 (localhost) | 110.1 KiB | 68.1 KiB |
body > img <img src="http://localhost:10200/dobetterweb/lighthouse-1024x680.jpg" srcset="lighthouse-1024x680.jpg 2x" width="360" height="240" style="position: absolute;"> | /dobetterweb/lighthouse-1024x680.jpg (localhost) | 110.1 KiB | 68.1 KiB |
Enable text compression Potential savings of 143 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.FCPLCP
You can enable text compression in your web server configuration.
URL | Transfer Size | Potential Savings |
---|---|---|
localhost 1st party | 179.8 KiB | 143.4 KiB |
…third_party/aggressive-promise-polyfill.js (localhost) | 162.4 KiB | 131.7 KiB |
/dobetterweb/dbw_tester.html (localhost) | 17.4 KiB | 11.7 KiB |
Serve images in next-gen formats Potential savings of 312 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.FCPLCP
Consider using the Performance Lab plugin to automatically convert your uploaded JPEG images into WebP, wherever supported.
URL | Resource Size | Potential Savings | |
---|---|---|---|
localhost 1st party | 708.5 KiB | 312.3 KiB | |
body > img <img src="lighthouse-1024x680.jpg?iar1" width="120" height="15"> | /dobetterweb/lighthouse-1024x680.jpg?iar1 (localhost) | 110.1 KiB | 47.8 KiB |
body > img <img src="lighthouse-1024x680.jpg?isr2" width="120" height="80" style="position: absolute;"> | /dobetterweb/lighthouse-1024x680.jpg?isr2 (localhost) | 110.1 KiB | 47.8 KiB |
body > img <img src="lighthouse-1024x680.jpg?isr3" width="360" height="240" style="image-rendering: pixelated; position: absolute;"> | /dobetterweb/lighthouse-1024x680.jpg?isr3 (localhost) | 110.1 KiB | 47.8 KiB |
body > img <img src="http://localhost:10200/dobetterweb/lighthouse-1024x680.jpg" srcset="lighthouse-1024x680.jpg 2x" width="360" height="240" style="position: absolute;"> | /dobetterweb/lighthouse-1024x680.jpg (localhost) | 110.1 KiB | 47.8 KiB |
body > img <img loading="lazy" src="lighthouse-1024x680.jpg?iar2" width="120" height="80" fetchpriority="low"> | /dobetterweb/lighthouse-1024x680.jpg?iar2 (localhost) | 110.1 KiB | 47.8 KiB |
110.1 KiB | 47.8 KiB | ||
body > img <img src="lighthouse-480x318.jpg?isr1" width="400" height="360" style="position: absolute;"> | /dobetterweb/lighthouse-480x318.jpg?isr1 (localhost) | 24.0 KiB | 12.7 KiB |
/dobetterweb/lighthouse-480x318.jpg?async (localhost) | 24.0 KiB | 12.7 KiB |
Minify JavaScript Potential savings of 81 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.FCPLCP
A number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your scripts. You may also want to use a build process to do this minification up front if possible.
URL | Transfer Size | Potential Savings |
---|---|---|
localhost 1st party | 162.4 KiB | 81.5 KiB |
…third_party/aggressive-promise-polyfill.js (localhost) | 162.4 KiB | 81.5 KiB |
Reduce unused JavaScript Potential savings of 92 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.FCPLCP
Consider reducing, or switching, the number of WordPress plugins loading unused JavaScript in your page. To identify plugins that are adding extraneous JS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the script. Look out for plugins that have many scripts in the list which have a lot of red in code coverage. A plugin should only enqueue a script if it is actually used on the page.
URL | Transfer Size | Potential Savings |
---|---|---|
localhost 1st party | 162.4 KiB | 92.0 KiB |
…third_party/aggressive-promise-polyfill.js (localhost) | 162.4 KiB | 92.0 KiB |
Avoid serving legacy JavaScript to modern browsers Potential savings of 26 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptFCPLCP
URL | Potential Savings | |
---|---|---|
localhost 1st party | 26.0 KiB | |
…third_party/aggressive-promise-polyfill.js (localhost) | 26.0 KiB | |
Object.defineProperty | ||
Object.defineProperties |
Page prevented back/forward cache restoration 1 failure reason
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Failure reason | Failure type |
---|---|
The page has an unload handler in the main frame. | Actionable |
/dobetterweb/dbw_tester.html (localhost) |
Preload Largest Contentful Paint image Potential savings of -40 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
URL | Potential Savings | |
---|---|---|
localhost 1st party | -40 ms | |
Do better web tester page <h2 id="toppy" style="background-image:url('');"> | -40 ms |
Image elements do not have explicit width
and height
width
and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
URL | |
---|---|
localhost 1st party | |
body > img <img src="blob:http://localhost:10200/fa49e413-bc80-4876-b31d-38a24f51cff7"> | blob:http://localhost:10200/fa49e413-bc80-4876-b31d-38a24f51cff7 |
body > img <img src="filesystem:http://localhost:10200/temporary/empty-0.9307734889843826.png"> | filesystem:http://localhost:10200/temporary/empty-0.9307734889843826.png |
Use video formats for animated content Potential savings of 666 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsFCPLCP
Consider uploading your GIF to a service which will make it available to embed as an HTML5 video.
URL | Resource Size | Potential Savings |
---|---|---|
localhost 1st party | 912.4 KiB | 666.0 KiB |
/dobetterweb/lighthouse-rotating.gif (localhost) | 912.4 KiB | 666.0 KiB |
Serve static assets with an efficient cache policy 20 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Read about Browser Caching in WordPress.
URL | Cache TTL | Transfer Size |
---|---|---|
localhost 1st party | 1,791 KiB | |
/dobetterweb/lighthouse-rotating.gif (localhost) | None | 913 KiB |
…third_party/aggressive-promise-polyfill.js (localhost) | None | 163 KiB |
/dobetterweb/lighthouse-1024x680.jpg (localhost) | None | 110 KiB |
/dobetterweb/lighthouse-1024x680.jpg?iar1 (localhost) | None | 110 KiB |
/dobetterweb/lighthouse-1024x680.jpg?iar2 (localhost) | None | 110 KiB |
/dobetterweb/lighthouse-1024x680.jpg?isr2 (localhost) | None | 110 KiB |
/dobetterweb/lighthouse-1024x680.jpg?isr3 (localhost) | None | 110 KiB |
None | 110 KiB | |
/dobetterweb/lighthouse-480x318.jpg?async (localhost) | None | 24 KiB |
/dobetterweb/lighthouse-480x318.jpg?isr1 (localhost) | None | 24 KiB |
None | 1 KiB | |
/dobetterweb/dbw_tester.css?delay=100 (localhost) | None | 1 KiB |
None | 1 KiB | |
/dobetterweb/dbw_tester.css?delay=2200 (localhost) | None | 1 KiB |
None | 1 KiB | |
None | 1 KiB | |
None | 1 KiB | |
/dobetterweb/dbw_tester.js (localhost) | None | 0 KiB |
/dobetterweb/empty_module.js?delay=500 (localhost) | None | 0 KiB |
/dobetterweb/empty.css (localhost) | None | 0 KiB |
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as
passive
to improve your page's scroll performance. Learn more about adopting passive event listeners.Source |
---|
localhost 1st party |
/dobetterweb/dbw_tester.html:318:5 (localhost) |
Eliminate render-blocking resources Potential savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.FCPLCP
There are a number of WordPress plugins that can help you inline critical assets or defer less important resources. Beware that optimizations provided by these plugins may break features of your theme or plugins, so you will likely need to make code changes.
URL | Transfer Size | Potential Savings |
---|---|---|
localhost 1st party | 2.9 KiB | 5,140 ms |
/dobetterweb/dbw_tester.css?delay=100 (localhost) | 0.6 KiB | 730 ms |
/dobetterweb/unknown404.css?delay=200 (localhost) | 0.2 KiB | 880 ms |
/dobetterweb/dbw_tester.css?delay=2200 (localhost) | 0.6 KiB | 880 ms |
0.6 KiB | 880 ms | |
/dobetterweb/dbw_tester.js (localhost) | 0.5 KiB | 880 ms |
/dobetterweb/fcp-delayer.js?delay=5000 (localhost) | 0.2 KiB | 880 ms |
Avoid document.write()
document.write()
For users on slow connections, external scripts dynamically injected via
document.write()
can delay page load by tens of seconds. Learn how to avoid document.write().Source |
---|
localhost 1st party |
/dobetterweb/dbw_tester.html:285:11 (localhost) |
/dobetterweb/dbw_tester.html:286:11 (localhost) |
/dobetterweb/dbw_tester.html:287:11 (localhost) |
JavaScript execution time 1.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL | Total CPU Time | Script Evaluation | Script Parse |
---|---|---|---|
localhost 1st party | 2,273 ms | 1,238 ms | 17 ms |
/dobetterweb/dbw_tester.html (localhost) | 2,176 ms | 1,150 ms | 8 ms |
…third_party/aggressive-promise-polyfill.js (localhost) | 96 ms | 88 ms | 9 ms |
Unattributable | 412 ms | 4 ms | 0 ms |
Unattributable | 412 ms | 4 ms | 0 ms |
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL | Start Time | Duration |
---|---|---|
localhost 1st party | 1,290 ms | |
/dobetterweb/dbw_tester.html (localhost) | 6,871 ms | 1,121 ms |
…third_party/aggressive-promise-polyfill.js (localhost) | 7,996 ms | 98 ms |
/dobetterweb/dbw_tester.html (localhost) | 6,800 ms | 71 ms |
Avoid large layout shifts 2 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element | Layout shift score |
---|---|
Do better web tester page
Hi there! <div> | 0.060 |
A late network request adjusted the page layout | |
Do better web tester page
Hi there! <div> | 0.039 |
User Timing marks and measures 41 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
Name | Type | Start Time | Duration |
---|---|---|---|
Zone | Measure | 8,006.37 ms | 1.93 ms |
Zone:ZoneAwarePromise | Measure | 8,009.76 ms | 2.04 ms |
Zone:toString | Measure | 8,011.87 ms | 0.03 ms |
Zone:util | Measure | 8,012.71 ms | 0.89 ms |
Zone:legacy | Measure | 8,013.63 ms | 10.87 ms |
Zone:registerElement | Measure | 8,013.75 ms | 0.75 ms |
Zone:EventTargetLegacy | Measure | 8,014.63 ms | 9.87 ms |
Zone:queueMicrotask | Measure | 8,024.53 ms | 0.47 ms |
Zone:timers | Measure | 8,024.99 ms | 0.81 ms |
Zone:requestAnimationFrame | Measure | 8,025.90 ms | 0.70 ms |
Zone:blocking | Measure | 8,026.93 ms | 0.18 ms |
Zone:EventTarget | Measure | 8,027.15 ms | 0.95 ms |
Zone:MutationObserver | Measure | 8,028.11 ms | 1.19 ms |
Zone:IntersectionObserver | Measure | 8,029.37 ms | 0.73 ms |
Zone:FileReader | Measure | 8,030.24 ms | 0.76 ms |
Zone:on_property | Measure | 8,031.94 ms | 59.06 ms |
Zone:customElements | Measure | 8,091.10 ms | 0.91 ms |
Zone:XHR | Measure | 8,092.04 ms | 0.06 ms |
Zone:geolocation | Measure | 8,092.16 ms | 0.64 ms |
Zone:PromiseRejectionEvent | Measure | 8,092.87 ms | 0.54 ms |
Zone | Mark | 8,006.37 ms | |
Zone:ZoneAwarePromise | Mark | 8,009.76 ms | |
Zone:toString | Mark | 8,011.87 ms | |
Zone:util | Mark | 8,012.71 ms | |
Zone:legacy | Mark | 8,013.63 ms | |
Zone:defineProperty | Mark | 8,013.68 ms | |
Zone:registerElement | Mark | 8,013.75 ms | |
Zone:EventTargetLegacy | Mark | 8,014.63 ms | |
Zone:queueMicrotask | Mark | 8,024.53 ms | |
Zone:timers | Mark | 8,024.99 ms | |
Zone:requestAnimationFrame | Mark | 8,025.90 ms | |
Zone:blocking | Mark | 8,026.93 ms | |
Zone:EventTarget | Mark | 8,027.15 ms | |
Zone:MutationObserver | Mark | 8,028.11 ms | |
Zone:IntersectionObserver | Mark | 8,029.37 ms | |
Zone:FileReader | Mark | 8,030.24 ms | |
Zone:on_property | Mark | 8,031.94 ms | |
Zone:customElements | Mark | 8,091.10 ms | |
Zone:XHR | Mark | 8,092.04 ms | |
Zone:geolocation | Mark | 8,092.16 ms | |
Zone:PromiseRejectionEvent | Mark | 8,092.87 ms |
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element | Name |
---|---|
hi <div id="animated-boi"> | |
Unsupported CSS Properties: margin-left, height | badanim |
Initial server response time was short Root document took 0 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.FCPLCP
Themes, plugins, and server specifications all contribute to server response time. Consider finding a more optimized theme, carefully selecting an optimization plugin, and/or upgrading your server.
URL | Time Spent |
---|---|
localhost 1st party | 0 ms |
/dobetterweb/dbw_tester.html (localhost) | 0 ms |
Avoids enormous network payloads Total size was 1,827 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Consider showing excerpts in your post lists (e.g. via the more tag), reducing the number of posts shown on a given page, breaking your long posts into multiple pages, or using a plugin to lazy-load comments.
URL | Transfer Size |
---|---|
localhost 1st party | 1,785.6 KiB |
/dobetterweb/lighthouse-rotating.gif (localhost) | 912.6 KiB |
…third_party/aggressive-promise-polyfill.js (localhost) | 162.7 KiB |
/dobetterweb/lighthouse-1024x680.jpg (localhost) | 110.3 KiB |
/dobetterweb/lighthouse-1024x680.jpg?iar1 (localhost) | 110.3 KiB |
/dobetterweb/lighthouse-1024x680.jpg?iar2 (localhost) | 110.3 KiB |
/dobetterweb/lighthouse-1024x680.jpg?isr2 (localhost) | 110.3 KiB |
/dobetterweb/lighthouse-1024x680.jpg?isr3 (localhost) | 110.3 KiB |
110.3 KiB | |
/dobetterweb/lighthouse-480x318.jpg?async (localhost) | 24.3 KiB |
/dobetterweb/lighthouse-480x318.jpg?isr1 (localhost) | 24.3 KiB |
Avoids an excessive DOM size 151 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic | Element | Value |
---|---|---|
Total DOM Elements | 151 | |
Maximum DOM Depth | body > div > svg.social-facebook > title#social-facebook-5 <title id="social-facebook-5"> | 4 |
Maximum Child Elements | body > div#shadow-root-container <div id="shadow-root-container"> | 100 |
Avoid chaining critical requests 11 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 7,963.211 ms
Initial Navigation
/dobetterweb/dbw_tester.html
(localhost)
/dobetterweb/dbw_tester.css?delay=100
- 568.125 ms, 0.65 KiB (localhost)
/dobetterweb/unknown404.css?delay=200
- 579.06 ms, 0.23 KiB (localhost)
/dobetterweb/dbw_tester.css?delay=2200
- 2,203.468 ms, 0.65 KiB (localhost)
- 581.839 ms, 0.68 KiB
- 3,022.122 ms, 0.65 KiB
- 3,575.183 ms, 0.65 KiB
…third_party/aggressive-promise-polyfill.js
- 2,337.159 ms, 162.67 KiB (localhost)
- 1,062.336 ms, 0.65 KiB
/dobetterweb/dbw_tester.js
- 1,141.251 ms, 0.47 KiB (localhost)
/dobetterweb/empty_module.js?delay=500
- 1,150.137 ms, 0.24 KiB (localhost)
/dobetterweb/fcp-delayer.js?delay=5000
- 6,157.644 ms, 0.24 KiB (localhost)
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party | Transfer Size | Main-Thread Blocking Time |
---|---|---|
[::1] | 0 KiB | 0 ms |
0 KiB | 0 ms |
Passed audits (12) Show Hide
Passed audits (12)
Show Hide
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.FCPLCP
Install a lazy-load WordPress plugin that provides the ability to defer any offscreen images, or switch to a theme that provides that functionality. Also consider using the AMP plugin.
Minify CSS
A number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your styles. You may also want to use a build process to do this minification up-front if possible.
Reduce unused CSS
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.FCPLCP
Consider reducing, or switching, the number of WordPress plugins loading unused CSS in your page. To identify plugins that are adding extraneous CSS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the stylesheet. Look out for plugins that have many stylesheets in the list which have a lot of red in code coverage. A plugin should only enqueue a stylesheet if it is actually used on the page.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.FCPLCP
Consider using an image optimization WordPress plugin that compresses your images while retaining quality.
Preconnect to required origins
Consider adding
preconnect
or dns-prefetch
resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more about HTTP/2.LCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. FCPLCP
All text remains visible during webfont loads
Leverage the
font-display
CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display
. Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Has a <meta name="viewport">
tag with width
or initial-scale
<meta name="viewport">
tag with width
or initial-scale
A
<meta name="viewport">
not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.