Metrics
First Contentful Paint
1.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index
2.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Time to Interactive
3.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Meaningful Paint
1.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
First CPU Idle
2.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
Max Potential First Input Delay
180 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Values are estimated and may vary. The performance score is based only on these metrics.
OpportunitiesThese suggestions can help your page load faster. They don't directly affect the Performance score.
Opportunity
Estimated Savings
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
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.Image formats like JPEG 2000, JPEG XR, and WebP 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 | Size | Potential Savings | |
|---|---|---|---|
 | …06/Customize….png (wpastra.com) | 162 KB | 138 KB |
 | …07/sites-section.png (wpastra.com) | 248 KB | 104 KB |
 | …07/syed-balkhi.png (wpastra.com) | 86 KB | 72 KB |
 | …11/astra-templates.png (wpastra.com) | 133 KB | 66 KB |
 | …07/chris-lema-1.png (wpastra.com) | 76 KB | 63 KB |
 | …07/justin-photo.png (wpastra.com) | 70 KB | 59 KB |
 | …07/ben-pines-cmo-elementor.png (wpastra.com) | 63 KB | 54 KB |
 | …07/troy-dean-photo.png (wpastra.com) | 64 KB | 54 KB |
 | …07/adam-preiser-photo.png (wpastra.com) | 56 KB | 49 KB |
 | …07/dave-foy-photo.png (wpastra.com) | 56 KB | 47 KB |
 | …07/team-2.jpg (wpastra.com) | 58 KB | 19 KB |
 | …05/part-01.jpg (wpastra.com) | 14 KB | 11 KB |
 | …05/part-02.jpg (wpastra.com) | 14 KB | 10 KB |
 | …05/part-03-2.jpg (wpastra.com) | 11 KB | 9 KB |
Time To First Byte identifies the time at which your server sends a response. Learn more.
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.Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
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.URL | Size | Potential Savings |
|---|---|---|
…min-css/uael-frontend.min.css?ver=1.20.1 (wpastra.com) | 38 KB | 38 KB |
…css/frontend.min.css?ver=2.8.1 (wpastra.com) | 22 KB | 21 KB |
…minified/style.min.css?ver=2.1.4 (wpastra.com) | 14 KB | 13 KB |
…css/frontend.min.css?ver=2.8.2 (wpastra.com) | 14 KB | 13 KB |
…css/all.min.css?ver=2.8.2 (wpastra.com) | 12 KB | 12 KB |
…css/fontawesome.min.css?ver=5.9.0 (wpastra.com) | 12 KB | 12 KB |
DiagnosticsMore information about the performance of your application. These numbers don't directly affect the Performance score.
A long cache lifetime can speed up repeat visits to your page. Learn more.
Read about Browser Caching in WordPress.URL | Cache TTL | Size |
|---|---|---|
…webfonts/fa-solid-900.woff2 (wpastra.com) | None | 74 KB |
…webfonts/fa-brands-400.woff2 (wpastra.com) | None | 73 KB |
…fonts/eicons.woff2?5.5.0 (wpastra.com) | None | 71 KB |
…06/398675_5_0-1.woff2 (wpastra.com) | None | 54 KB |
…06/398675_8_0.woff2 (wpastra.com) | None | 54 KB |
…webfonts/fa-regular-400.woff2 (wpastra.com) | None | 14 KB |
…config/152…?v=2.9.15&r=stable (connect.facebook.net) | 20 m | 114 KB |
/en_US/fbevents.js (connect.facebook.net) | 20 m | 31 KB |
/analytics.js (www.google-analytics.com) | 2 h | 18 KB |
Passed audits
(14)
Passed audits
(14)
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.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.URL | Size | Potential Savings | |
|---|---|---|---|
| …06/Customize….png (wpastra.com) | 162 KB | 162 KB |
Minifying CSS files can reduce network payload sizes. Learn more.
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.Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
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.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.URL | Size | Potential Savings | |
|---|---|---|---|
| …05/part-01.jpg (wpastra.com) | 14 KB | 7 KB |
| …05/part-02.jpg (wpastra.com) | 14 KB | 7 KB |
| …05/part-03-2.jpg (wpastra.com) | 11 KB | 6 KB |
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
You can enable text compression in your web server configuration.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
Consider uploading your GIF to a service which will make it available to embed as an HTML5 video.Large network payloads cost users real money and are highly correlated with long load times. Learn more.
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 | Size |
|---|---|
…07/sites-section.png (wpastra.com) | 249 KB |
…06/Customize….png (wpastra.com) | 163 KB |
…11/astra-templates.png (wpastra.com) | 133 KB |
…config/152…?v=2.9.15&r=stable (connect.facebook.net) | 114 KB |
…07/syed-balkhi.png (wpastra.com) | 86 KB |
…07/chris-lema-1.png (wpastra.com) | 76 KB |
…webfonts/fa-solid-900.woff2 (wpastra.com) | 74 KB |
…webfonts/fa-brands-400.woff2 (wpastra.com) | 73 KB |
…fonts/eicons.woff2?5.5.0 (wpastra.com) | 71 KB |
…07/justin-photo.png (wpastra.com) | 70 KB |
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.
ContrastThese are opportunities to improve the legibility of your content.
Names and labelsThese are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Additional items to manually check
(11)
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Additional items to manually check
(11)
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits
(18)
Passed audits
(18)
Not applicable
(15)
Not applicable
(15)
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more.
Additional items to manually check
(1)
Run these additional validators on your site to check additional SEO best practices.
Additional items to manually check
(1)
Run these additional validators on your site to check additional SEO best practices.
Passed audits
(11)
Passed audits
(11)
Not applicable
(2)
Not applicable
(2)
These checks validate the aspects of a Progressive Web App. Learn more.
Fast and reliable
Installable
PWA Optimized
Additional items to manually check
(3)
These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Additional items to manually check
(3)
These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.