0–49 50–89 90–100
Lab DataLighthouse analysis of the current page on an emulated mobile network. Values are estimated and may vary.
First Contentful Paint
6.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index
8.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint
6.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Time to Interactive
8.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time
1,220 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.136
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.
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
OpportunitiesThese suggestions can help your page load faster. They don't directly affect the Performance score.
Opportunity
Estimated Savings
Use video formats for animated content
3.3 s
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
WordPressConsider uploading your GIF to a service which will make it available to embed as an HTML5 video.
URL
Resource Size
Potential Savings
912.4 KiB
666.0 KiB
Enable text compression
1.8 s
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.FCPLCP
WordPressYou can enable text compression in your web server configuration.
URL
Transfer Size
Potential Savings
162.4 KiB
131.7 KiB
17.0 KiB
11.4 KiB
Minify JavaScript
0.9 s
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.FCPLCP
WordPressA 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
162.6 KiB
81.6 KiB
Reduce unused JavaScript
0.6 s
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.LCP
WordPressConsider 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
162.6 KiB
42.5 KiB
…2.1.1/jquery.min.js
(ajax.googleapis.com)
29.6 KiB
21.0 KiB
Serve images in next-gen formats
0.45 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.
WordPressConsider using a plugin or service that will automatically convert your uploaded images to the optimal formats.
URL
Resource Size
Potential Savings
24.0 KiB
12.7 KiB
24.0 KiB
12.7 KiB
24.0 KiB
12.7 KiB
24.0 KiB
12.7 KiB
24.0 KiB
12.7 KiB
24.0 KiB
12.7 KiB
Properly size images
0.3 s
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
WordPressUpload 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
24.0 KiB
22.1 KiB
24.0 KiB
13.6 KiB
24.0 KiB
13.6 KiB
Avoid serving legacy JavaScript to modern browsers
0.15 s
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
20.7 KiB
Object.defineProperty
Object.defineProperties
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
Avoid 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
Image elements do not have explicit 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/3f2bc9df-684b-4541-837c-1590152ef65d
body > img
<img src="blob:http://localhost:10200/3f2bc9df-684b-4541-837c-1590152ef65d">
filesystem:http://localhost:10200/temporary/empty-0.43448333410631723.png
body > img
<img src="filesystem:http://localhost:10200/temporary/empty-0.43448333410631723.png">
Serve static assets with an efficient cache policy 18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
URL
Cache TTL
Transfer Size
None
913 KiB
None
163 KiB
None
24 KiB
None
24 KiB
None
24 KiB
None
24 KiB
None
24 KiB
None
24 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
0 KiB
None
0 KiB
Minimize main-thread work 2.2 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,343 ms
Rendering
327 ms
Other
323 ms
Style & Layout
201 ms
Parse HTML & CSS
31 ms
Script Parsing & Compilation
17 ms
Reduce 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 more.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
1,946 ms
1,196 ms
6 ms
Unattributable
147 ms
22 ms
1 ms
100 ms
94 ms
6 ms
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: 7,690 ms
Initial Navigation
- 570 ms, 0.88 KiB
- 580 ms, 0.20 KiB
- 2,210 ms, 0.88 KiB
- 580 ms, 1.16 KiB
- 3,010 ms, 0.88 KiB
- 3,570 ms, 0.88 KiB
- 6,100 ms, 0.22 KiB
- 1,450 ms, 162.65 KiB
…2.1.1/jquery.min.js
(ajax.googleapis.com)
- 740 ms, 29.63 KiB
- 1,140 ms, 1.03 KiB
- 1,150 ms, 0.22 KiB
User Timing marks and measures 42 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.
Name
Type
Start Time
Duration
Zone
Measure
8,054.63 ms
2.07 ms
Zone:ZoneAwarePromise
Measure
8,057.15 ms
1.55 ms
Zone:toString
Measure
8,059.54 ms
0.16 ms
Zone:util
Measure
8,060.21 ms
0.09 ms
Zone:legacy
Measure
8,060.34 ms
11.16 ms
Zone:defineProperty
Measure
8,061 ms
0.4 ms
Zone:registerElement
Measure
8,061.4 ms
0.1 ms
Zone:EventTargetLegacy
Measure
8,061.5 ms
10 ms
Zone:queueMicrotask
Measure
8,071.48 ms
0.42 ms
Zone:timers
Measure
8,071.97 ms
0.43 ms
Zone:requestAnimationFrame
Measure
8,072.43 ms
0.07 ms
Zone:blocking
Measure
8,073.06 ms
0.14 ms
Zone:EventTarget
Measure
8,073.15 ms
0.75 ms
Zone:MutationObserver
Measure
8,073.85 ms
0.75 ms
Zone:IntersectionObserver
Measure
8,074.66 ms
0.94 ms
Zone:FileReader
Measure
8,075.61 ms
0.79 ms
Zone:on_property
Measure
8,076.6 ms
58.49 ms
Zone:customElements
Measure
8,135.11 ms
0.79 ms
Zone:XHR
Measure
8,135.85 ms
0.85 ms
Zone:geolocation
Measure
8,136.73 ms
0.47 ms
Zone:PromiseRejectionEvent
Measure
8,137.22 ms
0.48 ms
Zone
Mark
8,055.21 ms
Zone:ZoneAwarePromise
Mark
8,057.15 ms
Zone:toString
Mark
8,059.55 ms
Zone:util
Mark
8,060.23 ms
Zone:legacy
Mark
8,060.35 ms
Zone:defineProperty
Mark
8,061 ms
Zone:registerElement
Mark
8,061.4 ms
Zone:EventTargetLegacy
Mark
8,061.5 ms
Zone:queueMicrotask
Mark
8,071.48 ms
Zone:timers
Mark
8,071.97 ms
Zone:requestAnimationFrame
Mark
8,072.44 ms
Zone:blocking
Mark
8,073.07 ms
Zone:EventTarget
Mark
8,073.15 ms
Zone:MutationObserver
Mark
8,073.85 ms
Zone:IntersectionObserver
Mark
8,075.07 ms
Zone:FileReader
Mark
8,075.61 ms
Zone:on_property
Mark
8,076.61 ms
Zone:customElements
Mark
8,135.11 ms
Zone:XHR
Mark
8,135.86 ms
Zone:geolocation
Mark
8,136.74 ms
Zone:PromiseRejectionEvent
Mark
8,137.23 ms
Keep request counts low and transfer sizes small 23 requests • 1,293 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
23
1,293.0 KiB
Image
7
1,058.0 KiB
Script
5
193.7 KiB
Document
1
17.2 KiB
Other
1
17.2 KiB
Stylesheet
9
6.9 KiB
Media
0
0.0 KiB
Font
0
0.0 KiB
Third-party
1
29.6 KiB
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn MoreLCP
Element
Do better web tester page
<h2>
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.CLS
Element
CLS Contribution
Do better web tester page Hi there!
<div>
0.054
body > object#5934a
<object id="5934a">
0.035
body > object#5934b
<object id="5934b">
0.035
touchmove section
<section id="touchmove-section">
0.007
body > img
<img loading="lazy" src="lighthouse-480x318.jpg?iar2" width="120" height="80">
0.004
Avoid long main-thread tasks 2 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
6,849 ms
1,175 ms
8,048 ms
146 ms
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS. Learn moreCLS
Element
Name
hi
<div id="animated-boi">
Unsupported CSS Properties: margin-left, height
badanim
Passed audits (19)
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 more.FCPLCP
WordPressThere 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
0.9 KiB
730 ms
0.2 KiB
880 ms
0.9 KiB
880 ms
0.9 KiB
880 ms
1.0 KiB
880 ms
0.2 KiB
880 ms
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
WordPressInstall 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
Minifying CSS files can reduce network payload sizes. Learn more.FCPLCP
WordPressA 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
WordPressConsider 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 more.
WordPressConsider 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
WordPressThemes, 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
570 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.FCPLCP
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.
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. TBT
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 1,293 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.LCP
WordPressConsider 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
912.6 KiB
162.6 KiB
…2.1.1/jquery.min.js
(ajax.googleapis.com)
29.6 KiB
24.2 KiB
24.2 KiB
24.2 KiB
24.2 KiB
24.2 KiB
24.2 KiB
17.2 KiB
Avoids an excessive DOM size 153 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
153
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
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 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 more.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
30 KiB
0 ms
…2.1.1/jquery.min.js
(ajax.googleapis.com)
30 KiB
0 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.
Has a <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
0–49 50–89 90–100
Lab DataLighthouse analysis of the current page on an emulated mobile network. Values are estimated and may vary.
First Contentful Paint
6.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index
8.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint
6.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Time to Interactive
8.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time
1,220 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.136
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.
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
OpportunitiesThese suggestions can help your page load faster. They don't directly affect the Performance score.
Opportunity
Estimated Savings
Use video formats for animated content
3.3 s
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
WordPressConsider uploading your GIF to a service which will make it available to embed as an HTML5 video.
URL
Resource Size
Potential Savings
912.4 KiB
666.0 KiB
Enable text compression
1.8 s
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.FCPLCP
WordPressYou can enable text compression in your web server configuration.
URL
Transfer Size
Potential Savings
162.4 KiB
131.7 KiB
17.0 KiB
11.4 KiB
Minify JavaScript
0.9 s
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.FCPLCP
WordPressA 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
162.6 KiB
81.6 KiB
Reduce unused JavaScript
0.6 s
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.LCP
WordPressConsider 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
162.6 KiB
42.5 KiB
…2.1.1/jquery.min.js
(ajax.googleapis.com)
29.6 KiB
21.0 KiB
Serve images in next-gen formats
0.45 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.
WordPressConsider using a plugin or service that will automatically convert your uploaded images to the optimal formats.
URL
Resource Size
Potential Savings
24.0 KiB
12.7 KiB
24.0 KiB
12.7 KiB
24.0 KiB
12.7 KiB
24.0 KiB
12.7 KiB
24.0 KiB
12.7 KiB
24.0 KiB
12.7 KiB
Properly size images
0.3 s
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
WordPressUpload 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
24.0 KiB
22.1 KiB
24.0 KiB
13.6 KiB
24.0 KiB
13.6 KiB
Avoid serving legacy JavaScript to modern browsers
0.15 s
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
20.7 KiB
Object.defineProperty
Object.defineProperties
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
Avoid 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
Image elements do not have explicit 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/3f2bc9df-684b-4541-837c-1590152ef65d
body > img
<img src="blob:http://localhost:10200/3f2bc9df-684b-4541-837c-1590152ef65d">
filesystem:http://localhost:10200/temporary/empty-0.43448333410631723.png
body > img
<img src="filesystem:http://localhost:10200/temporary/empty-0.43448333410631723.png">
Serve static assets with an efficient cache policy 18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
URL
Cache TTL
Transfer Size
None
913 KiB
None
163 KiB
None
24 KiB
None
24 KiB
None
24 KiB
None
24 KiB
None
24 KiB
None
24 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
0 KiB
None
0 KiB
Minimize main-thread work 2.2 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,343 ms
Rendering
327 ms
Other
323 ms
Style & Layout
201 ms
Parse HTML & CSS
31 ms
Script Parsing & Compilation
17 ms
Reduce 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 more.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
1,946 ms
1,196 ms
6 ms
Unattributable
147 ms
22 ms
1 ms
100 ms
94 ms
6 ms
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: 7,690 ms
Initial Navigation
- 570 ms, 0.88 KiB
- 580 ms, 0.20 KiB
- 2,210 ms, 0.88 KiB
- 580 ms, 1.16 KiB
- 3,010 ms, 0.88 KiB
- 3,570 ms, 0.88 KiB
- 6,100 ms, 0.22 KiB
- 1,450 ms, 162.65 KiB
…2.1.1/jquery.min.js
(ajax.googleapis.com)
- 740 ms, 29.63 KiB
- 1,140 ms, 1.03 KiB
- 1,150 ms, 0.22 KiB
User Timing marks and measures 42 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.
Name
Type
Start Time
Duration
Zone
Measure
8,054.63 ms
2.07 ms
Zone:ZoneAwarePromise
Measure
8,057.15 ms
1.55 ms
Zone:toString
Measure
8,059.54 ms
0.16 ms
Zone:util
Measure
8,060.21 ms
0.09 ms
Zone:legacy
Measure
8,060.34 ms
11.16 ms
Zone:defineProperty
Measure
8,061 ms
0.4 ms
Zone:registerElement
Measure
8,061.4 ms
0.1 ms
Zone:EventTargetLegacy
Measure
8,061.5 ms
10 ms
Zone:queueMicrotask
Measure
8,071.48 ms
0.42 ms
Zone:timers
Measure
8,071.97 ms
0.43 ms
Zone:requestAnimationFrame
Measure
8,072.43 ms
0.07 ms
Zone:blocking
Measure
8,073.06 ms
0.14 ms
Zone:EventTarget
Measure
8,073.15 ms
0.75 ms
Zone:MutationObserver
Measure
8,073.85 ms
0.75 ms
Zone:IntersectionObserver
Measure
8,074.66 ms
0.94 ms
Zone:FileReader
Measure
8,075.61 ms
0.79 ms
Zone:on_property
Measure
8,076.6 ms
58.49 ms
Zone:customElements
Measure
8,135.11 ms
0.79 ms
Zone:XHR
Measure
8,135.85 ms
0.85 ms
Zone:geolocation
Measure
8,136.73 ms
0.47 ms
Zone:PromiseRejectionEvent
Measure
8,137.22 ms
0.48 ms
Zone
Mark
8,055.21 ms
Zone:ZoneAwarePromise
Mark
8,057.15 ms
Zone:toString
Mark
8,059.55 ms
Zone:util
Mark
8,060.23 ms
Zone:legacy
Mark
8,060.35 ms
Zone:defineProperty
Mark
8,061 ms
Zone:registerElement
Mark
8,061.4 ms
Zone:EventTargetLegacy
Mark
8,061.5 ms
Zone:queueMicrotask
Mark
8,071.48 ms
Zone:timers
Mark
8,071.97 ms
Zone:requestAnimationFrame
Mark
8,072.44 ms
Zone:blocking
Mark
8,073.07 ms
Zone:EventTarget
Mark
8,073.15 ms
Zone:MutationObserver
Mark
8,073.85 ms
Zone:IntersectionObserver
Mark
8,075.07 ms
Zone:FileReader
Mark
8,075.61 ms
Zone:on_property
Mark
8,076.61 ms
Zone:customElements
Mark
8,135.11 ms
Zone:XHR
Mark
8,135.86 ms
Zone:geolocation
Mark
8,136.74 ms
Zone:PromiseRejectionEvent
Mark
8,137.23 ms
Keep request counts low and transfer sizes small 23 requests • 1,293 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
23
1,293.0 KiB
Image
7
1,058.0 KiB
Script
5
193.7 KiB
Document
1
17.2 KiB
Other
1
17.2 KiB
Stylesheet
9
6.9 KiB
Media
0
0.0 KiB
Font
0
0.0 KiB
Third-party
1
29.6 KiB
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn MoreLCP
Element
Do better web tester page
<h2>
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.CLS
Element
CLS Contribution
Do better web tester page Hi there!
<div>
0.054
body > object#5934a
<object id="5934a">
0.035
body > object#5934b
<object id="5934b">
0.035
touchmove section
<section id="touchmove-section">
0.007
body > img
<img loading="lazy" src="lighthouse-480x318.jpg?iar2" width="120" height="80">
0.004
Avoid long main-thread tasks 2 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
6,849 ms
1,175 ms
8,048 ms
146 ms
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS. Learn moreCLS
Element
Name
hi
<div id="animated-boi">
Unsupported CSS Properties: margin-left, height
badanim
Passed audits (19)
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 more.FCPLCP
WordPressThere 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
0.9 KiB
730 ms
0.2 KiB
880 ms
0.9 KiB
880 ms
0.9 KiB
880 ms
1.0 KiB
880 ms
0.2 KiB
880 ms
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
WordPressInstall 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
Minifying CSS files can reduce network payload sizes. Learn more.FCPLCP
WordPressA 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
WordPressConsider 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 more.
WordPressConsider 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
WordPressThemes, 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
570 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.FCPLCP
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.
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. TBT
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 1,293 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.LCP
WordPressConsider 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
912.6 KiB
162.6 KiB
…2.1.1/jquery.min.js
(ajax.googleapis.com)
29.6 KiB
24.2 KiB
24.2 KiB
24.2 KiB
24.2 KiB
24.2 KiB
24.2 KiB
17.2 KiB
Avoids an excessive DOM size 153 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
153
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
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 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 more.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
30 KiB
0 ms
…2.1.1/jquery.min.js
(ajax.googleapis.com)
30 KiB
0 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.
Has a <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