https://wpastra.com/
61
Performance
95
Accessibility
69
Best Practices
100
SEO
Progressive Web App
0–49 50–89 90–100
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.
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
OpportunitiesThese suggestions can help your page load faster. They don't directly affect the Performance score.
Opportunity
Estimated Savings
Eliminate render-blocking resources
1.53 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.
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
Size
Potential Savings
14 KB
150 ms
6 KB
190 ms
3 KB
150 ms
2 KB
150 ms
1 KB
150 ms
1 KB
150 ms
0 KB
70 ms
1 KB
70 ms
3 KB
70 ms
1 KB
70 ms
3 KB
70 ms
3 KB
70 ms
14 KB
150 ms
22 KB
190 ms
38 KB
270 ms
12 KB
110 ms
4 KB
70 ms
0 KB
70 ms
12 KB
110 ms
1 KB
70 ms
1 KB
70 ms
33 KB
150 ms
4 KB
70 ms
4 KB
70 ms
Serve images in next-gen formats
0.72 s
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.
WordPressConsider using a plugin or service that will automatically convert your uploaded images to the optimal formats.
URL
Size
Potential Savings
162 KB
138 KB
248 KB
104 KB
86 KB
72 KB
133 KB
66 KB
76 KB
63 KB
70 KB
59 KB
63 KB
54 KB
64 KB
54 KB
56 KB
49 KB
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
Reduce server response times (TTFB)
0.41 s
Time To First Byte identifies the time at which your server sends a response. Learn more.
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.
Remove unused CSS
0.16 s
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.
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.
URL
Size
Potential Savings
38 KB
38 KB
22 KB
21 KB
14 KB
13 KB
14 KB
13 KB
12 KB
12 KB
12 KB
12 KB
DiagnosticsMore information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
URL
Potential Savings
930 ms
910 ms
930 ms
160 ms
Serve static assets with an efficient cache policy 9 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
URL
Cache TTL
Size
None
74 KB
None
73 KB
None
71 KB
None
54 KB
None
54 KB
None
14 KB
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
Avoid an excessive DOM size 1,731 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Statistic
Element
Value
Total DOM Elements
1,731
Maximum DOM Depth
<div class="elementor-testimonial-name">
42
Maximum Child Elements
<body itemtype="https://schema.org/WebPage" itemscope="itemscope" class="home page-template-default page page-id-17257 wp-custom-logo ast-page-builder-template ast-no-sidebar astra-2.1.4 ast-header-custom-item-inside group-blog ast-single-post ast-mobile-inherit-site-logo ast-inherit-site-logo-transparent ast-theme-transparent-header above-header-nav-padding-support ast-above-header-hide-on-mobile ast-above-mobile-menu-align-stack ast-flyout-menu-enable ast-default-above-menu-enable ast-flyout-right-side ast-default-below-menu-enable elementor-default elementor-page elementor-page-17257 astra-addon-2.1.4 ast-desktop   dialog-body dialog-lightbox-body dialog-container dialog-lightbox-container" data-elementor-device-mode="desktop">
40
Minimize main-thread work 2.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Category
Time Spent
Style & Layout
1,108 ms
Script Evaluation
760 ms
Other
247 ms
Rendering
155 ms
Parse HTML & CSS
102 ms
Script Parsing & Compilation
65 ms
Garbage Collection
32 ms
Avoid chaining critical requests 55 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.
Maximum critical path latency: 2,970 ms
Initial Navigation
- 330 ms, 22.53 KB
- 910 ms, 71.29 KB
…fonts/astra.woff
(wpastra.com)
- 620 ms, 3.57 KB
- 640 ms, 2.69 KB
- 630 ms, 0.67 KB
- 930 ms, 53.81 KB
- 170 ms, 1.11 KB
- 170 ms, 6.39 KB
- 620 ms, 0.67 KB
- 170 ms, 10.58 KB
- 630 ms, 12.29 KB
- 160 ms, 1.79 KB
- 640 ms, 1.75 KB
- 610 ms, 3.44 KB
- 800 ms, 38.32 KB
- 630 ms, 0.48 KB
- 790 ms, 32.42 KB
- 640 ms, 2.98 KB
- 780 ms, 33.4 KB
- 170 ms, 3.78 KB
- 160 ms, 13.54 KB
- 170 ms, 7.38 KB
- 320 ms, 19.75 KB
- 650 ms, 2.88 KB
- 630 ms, 12.01 KB
- 930 ms, 73.95 KB
- 330 ms, 24.15 KB
- 620 ms, 3.31 KB
- 930 ms, 53.98 KB
- 170 ms, 9.76 KB
- 170 ms, 1.27 KB
- 800 ms, 21.55 KB
- 790 ms, 14.42 KB
- 150 ms, 1.12 KB
- 610 ms, 0.48 KB
- 930 ms, 73.04 KB
- 640 ms, 2.84 KB
- 650 ms, 0.64 KB
- 170 ms, 3.06 KB
- 620 ms, 2.91 KB
- 170 ms, 0.76 KB
- 640 ms, 0.83 KB
- 170 ms, 6.8 KB
- 170 ms, 1.26 KB
- 620 ms, 4.31 KB
- 330 ms, 17.02 KB
- 800 ms, 14.04 KB
- 630 ms, 4.49 KB
- 170 ms, 2.24 KB
- 610 ms, 4.48 KB
- 160 ms, 2.93 KB
- 640 ms, 1.23 KB
Keep request counts low and transfer sizes small 110 requests • 2,282 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Resource Type
Requests
Transfer Size
Total
110
2,282 KB
Image
40
1,298 KB
Script
33
441 KB
Font
7
343 KB
Stylesheet
21
143 KB
Document
1
51 KB
Other
8
5 KB
Media
0
0 KB
Third-party
17
219 KB
Passed audits (14)
Properly size images
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.
Defer offscreen images Potential savings of 162 KB
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.
URL
Size
Potential Savings
162 KB
162 KB
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.
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.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
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.
Efficiently encode images Potential savings of 21 KB
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.
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
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
WordPressYou can enable text compression in your web server configuration.
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.
Preload key requests
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. 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 more
WordPressConsider uploading your GIF to a service which will make it available to embed as an HTML5 video.
Avoids enormous network payloads Total size was 2,282 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
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
Size
249 KB
163 KB
133 KB
114 KB
86 KB
76 KB
74 KB
73 KB
71 KB
70 KB
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 0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
URL
Total CPU Time
Script Evaluation
Script Parse
Other
981 ms
8 ms
1 ms
970 ms
418 ms
2 ms
111 ms
8 ms
1 ms
66 ms
62 ms
4 ms
63 ms
49 ms
11 ms
53 ms
46 ms
4 ms
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.
Third-Party
Size
Main-Thread Blocking Time
145 KB
0 ms
43 KB
0 ms
27 KB
0 ms
3 KB
0 ms
2 KB
0 ms
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.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Failing Elements
Days
<span class="elementor-countdown-label">Days</span>
Hours
<span class="elementor-countdown-label">Hours</span>
Minutes
<span class="elementor-countdown-label">Minutes</span>
Seconds
<span class="elementor-countdown-label">Seconds</span>
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.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn more.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.
Headings don't skip levels
Headings are used to create an outline for the page and heading levels are not skipped. Learn more.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.
Passed audits (18)
[aria-*] attributes match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
[id] attributes on the page are unique
The value of an id attribute must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
List items (<li>) are contained within <ul> or <ol> parent elements
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.
Not applicable (15)
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.
<audio> elements contain a <track> element with [kind="captions"]
Captions make audio elements usable for deaf or hearing-impaired users, providing critical information such as who is talking, what they're saying, and other non-speech information. Learn more.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script> or <template> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Definition list items are wrapped in <dl> elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
<input type="image"> elements have [alt] text
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Presentational <table> elements avoid using <th>, <caption> or the [summary] attribute.
A table being used for layout purposes should not include data elements, such as the th or caption elements or the summary attribute, because this can create a confusing experience for screen reader users. Learn more.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.
<object> elements have [alt] text
Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey meaning to users. Learn more.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
<video> elements contain a <track> element with [kind="description"]
Audio descriptions provide relevant information for videos that dialogue cannot, such as facial expressions and scenes. Learn more.
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.
URL
Location
line: 2
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
URL
Target
Rel
/wpastra/
(www.facebook.com)
_blank
/AstraWP
(twitter.com)
_blank
/brainstormforce
(github.com)
_blank
_blank
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Library Version
Vulnerability Count
Highest Severity
2
Medium
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
URL
Description
/tr/
(www.facebook.com)
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector
Passed audits (10)
Avoids Application Cache
Application Cache is deprecated. Learn more.
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name
Version
jQuery
1.12.4
jQuery (Fast path)
jQuery UI
Isotope
WordPress
5.3.2
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more.
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
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.
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Passed audits (11)
Has a <meta name="viewport"> tag with width or initial-scale
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more.
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
Not applicable (2)
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more.
Tap targets are sized appropriately
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
These checks validate the aspects of a Progressive Web App. Learn more.
Fast and reliable
Page load is not fast enough on mobile networks
Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
Interactive on simulated mobile network at 12.0 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
start_url does not respond with a 200 when offline
No usable web app manifest found on page.
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more.
Installable
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Does not register a service worker that controls page and start_url
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Web app manifest does not meet the installability requirements
Failures: No manifest was fetched.
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
PWA Optimized
Redirects HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Is not configured for a custom splash screen
Failures: No manifest was fetched.
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more.
Does not set a theme color for the address bar.
Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
The browser address bar can be themed to match your site. Learn more.
Content is sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more.
Has a <meta name="viewport"> tag with width or initial-scale
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more.
Contains some content when JavaScript is not available
Your app should display some content when JavaScript is disabled, even if it's just a warning to the user that JavaScript is required to use the app. Learn more.
Provides a valid apple-touch-icon
Warnings: `apple-touch-icon-precomposed` is out of date; `apple-touch-icon` is preferred.
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
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.
Site works cross-browser
To reach the most number of users, sites should work across every major browser. Learn more.
Page transitions don't feel like they block on the network
Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more.
Each page has a URL
Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more.