Metrics
First Contentful Paint
4.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index
4.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint
4.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Time to Interactive
4.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time
120 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift
0.42
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
Show audits relevant to:
OpportunitiesThese suggestions can help your page load faster. They don't directly affect the Performance score.
Opportunity
Estimated Savings
Eliminate render-blocking resources 0.98 s
Eliminate render-blocking resources
0.98 s
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.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 |
---|---|---|
/dobetterweb/dbw_tester.css?delay=100 (localhost) | 0.9 KiB | 870 ms |
/dobetterweb/unknown404.css?delay=200 (localhost) | 0.2 KiB | 870 ms |
/dobetterweb/dbw_tester.css?delay=2200 (localhost) | 0.9 KiB | 870 ms |
/dobetterweb/dbw_tester.js (localhost) | 1.0 KiB | 720 ms |
Minify JavaScript 0.15 s
Minify JavaScript
0.15 s
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 |
---|---|---|
/zone.js (localhost) | 70.0 KiB | 29.8 KiB |
Serve images in next-gen formats 0.15 s
Serve images in next-gen formats
0.15 s
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Consider using a plugin or service that will automatically convert your uploaded images to the optimal formats.
URL | Resource Size | Potential Savings | |
---|---|---|---|
/dobetterweb/lighthouse-480x318.jpg (localhost) | 24.0 KiB | 12.7 KiB |
Enable text compression 0.15 s
Enable text compression
0.15 s
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.FCPLCP
You can enable text compression in your web server configuration.
URL | Transfer Size | Potential Savings |
---|---|---|
…third_party/aggressive-promise-polyfill.js (localhost) | 69.8 KiB | 54.9 KiB |
/dobetterweb/dbw_tester.html (localhost) | 12.2 KiB | 8.2 KiB |
DiagnosticsMore information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Source |
---|
/dobetterweb/dbw_tester.html:303:5 (localhost) |
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 more.
Source |
---|
/dobetterweb/dbw_tester.html:270:11 (localhost) |
/dobetterweb/dbw_tester.html:271:11 (localhost) |
/dobetterweb/dbw_tester.html:272:11 (localhost) |
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 moreCLS
URL | Failing Elements | |
---|---|---|
blob:http://localhost:10200/822c70a0-b912-41c7-9a21-56c3d309e75b | img <img src="blob:http://localhost:10200/822c70a0-b912-41c7-9a21-56c3d309e75b"> | |
filesystem:http://localhost:10200/temporary/empty-0.8423185960902964.png | img <img src="filesystem:http://localhost:10200/temporary/empty-0.8423185960902964.png"> |
Serve static assets with an efficient cache policy 10 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Read about Browser Caching in WordPress.
URL | Cache TTL | Transfer Size |
---|---|---|
/zone.js (localhost) | None | 70 KiB |
/dobetterweb/lighthouse-480x318.jpg (localhost) | None | 24 KiB |
/dobetterweb/dbw_tester.js (localhost) | None | 2 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 | |
/dobetterweb/empty_module.js?delay=500 (localhost) | None | 0 KiB |
Avoid chaining critical requests 12 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 more.FCPLCP
Maximum critical path latency: 4,800 ms
Initial Navigation
/dobetterweb/dbw_tester.html
(localhost)
/dobetterweb/dbw_tester.css?delay=100
- 570 ms, 0.80 KiB (localhost)
/dobetterweb/unknown404.css?delay=200
- 580 ms, 0.14 KiB (localhost)
/dobetterweb/dbw_tester.css?delay=2200
- 2,210 ms, 0.80 KiB (localhost)
- 580 ms, 1.08 KiB
/dobetterweb/dbw_partial_a.html?delay=200
- 590 ms, 0.72 KiB (localhost)
- 1,140 ms, 0.72 KiB
- 3,570 ms, 0.80 KiB
/zone.js
- 1,110 ms, 69.97 KiB (localhost)
…2.1.1/jquery.min.js
- 920 ms, 29.47 KiB (ajax.googleapis.com)
- 1,040 ms, 0.80 KiB
/dobetterweb/dbw_tester.js
- 1,150 ms, 1.66 KiB (localhost)
/dobetterweb/empty_module.js?delay=500
- 590 ms, 0.14 KiB (localhost)
Keep request counts low and transfer sizes small 16 requests • 157 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Resource Type | Requests | Transfer Size |
---|---|---|
Total | 16 | 156.8 KiB |
Script | 4 | 101.2 KiB |
Image | 1 | 24.2 KiB |
Document | 3 | 13.8 KiB |
Other | 1 | 12.3 KiB |
Stylesheet | 7 | 5.2 KiB |
Media | 0 | 0.0 KiB |
Font | 0 | 0.0 KiB |
Third-party | 1 | 29.5 KiB |
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn MoreLCP
Element |
---|
img <img src="lighthouse-480x318.jpg?iar2" width="120" height="80"> |
Avoid large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page.CLS
Element | CLS Contribution |
---|---|
Debugging Node.js with Chrome DevTools <h5> | |
The canonical guide to using the Chrome DevTools UI for debugging Node.js. It d… <p> | |
hr <hr> | |
Aside from that, I’ve been busy working on Lighthouse, performance metrics, too… <p> |
Avoid long main-thread tasks 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn moreTBT
URL | Start Time | Duration |
---|---|---|
/dobetterweb/dbw_tester.js (localhost) | 2,854 ms | 983 ms |
…2.1.1/jquery.min.js (ajax.googleapis.com) | 4,809 ms | 127 ms |
Unattributable | 3,840 ms | 124 ms |
/zone.js (localhost) | 3,996 ms | 96 ms |
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS. Learn moreCLS
Element | Name |
---|---|
div <div id="animated-boi"> | |
Unsupported CSS Property: width | |
Unsupported CSS Properties: height, left | alpha |
Unsupported CSS Property: background-color | beta |
Passed audits (25)
Passed audits (25)
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
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.
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
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 more.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.
Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.LCP
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.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.
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 more.FCPLCP
Initial server response time was short Root document took 570 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.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 |
---|---|
/dobetterweb/dbw_tester.html (localhost) | 570 ms |
Avoid multiple page redirects
Preload key requests
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.FCPLCP
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
Use video formats for animated content
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 moreLCP
Consider uploading your GIF to a service which will make it available to embed as an HTML5 video.
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. TBT
Avoid serving legacy JavaScript to modern browsers Potential savings of 21 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 MoreTBT
URL | Potential Savings | |
---|---|---|
/zone.js (localhost) | 20.7 KiB | |
/zone.js:1291:4 (localhost) | Object.defineProperty | |
/zone.js:1301:4 (localhost) | Object.defineProperties |
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time. Learn more.LCP
Avoids enormous network payloads Total size was 157 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.LCP
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 |
---|---|
/zone.js (localhost) | 70.0 KiB |
…2.1.1/jquery.min.js (ajax.googleapis.com) | 29.5 KiB |
/dobetterweb/lighthouse-480x318.jpg (localhost) | 24.2 KiB |
/dobetterweb/dbw_tester.html (localhost) | 12.3 KiB |
/dobetterweb/dbw_tester.html (localhost) | 12.3 KiB |
/dobetterweb/dbw_tester.js (localhost) | 1.7 KiB |
1.1 KiB | |
/dobetterweb/dbw_tester.css?delay=100 (localhost) | 0.8 KiB |
0.8 KiB | |
/dobetterweb/dbw_tester.css?delay=2200 (localhost) | 0.8 KiB |
Avoids an excessive DOM size 148 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.TBT
Statistic | Element | Value |
---|---|---|
Total DOM Elements | 148 | |
Maximum DOM Depth | title <title id="social-facebook-5"> | 4 |
Maximum Child Elements | div <div id="shadow-root-container"> | 100 |
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
JavaScript execution time 1.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.TBT
URL | Total CPU Time | Script Evaluation | Script Parse |
---|---|---|---|
/dobetterweb/dbw_tester.html (localhost) | 1,044 ms | 964 ms | 3 ms |
Unattributable | 280 ms | 10 ms | 0 ms |
/zone.js (localhost) | 107 ms | 91 ms | 2 ms |
…2.1.1/jquery.min.js (ajax.googleapis.com) | 90 ms | 81 ms | 1 ms |
Minimizes main-thread work 1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn moreTBT
Category | Time Spent |
---|---|
Script Evaluation | 1,149 ms |
Other | 177 ms |
Style & Layout | 122 ms |
Parse HTML & CSS | 54 ms |
Garbage Collection | 26 ms |
Rendering | 13 ms |
Script Parsing & Compilation | 8 ms |
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.FCPLCP
Minimize third-party usage Third-party code blocked the main thread for 20 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 more.TBT
Third-Party | Transfer Size | Main-Thread Blocking Time |
---|---|---|
Google CDN | 29 KiB | 23 ms |
…2.1.1/jquery.min.js (ajax.googleapis.com) | 29 KiB | 23 ms |
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 more.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.
Element |
---|
img <img src="lighthouse-480x318.jpg?iar2" width="120" height="80"> |
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.TBT