https://habitatcdd.com/
76
Performance
100
Accessibility
100
Best Practices
86
SEO
PWA
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
2.1 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
5.3 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
120 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
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
4.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Diagnostics
Eliminate render-blocking resources Potential savings of 430 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
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
habitatcdd.com
1st party
26.2 KiB
360 ms
13.8 KiB
180 ms
12.4 KiB
180 ms
Google CDN
cdn
30.3 KiB
1,050 ms
…2.2.4/jquery.min.js
(ajax.googleapis.com)
30.3 KiB
1,050 ms
Properly size images Potential savings of 22 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
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
habitatcdd.com
1st party
68.4 KiB
21.8 KiB
div.main > div.inner-wrap > div.img1 > img
<img src="https://habitatcdd.com/wp-content/uploads/2020/02/PicMonkey-Collage4-768x2…" alt="">
…02/PicMonkey….jpg
(habitatcdd.com)
68.4 KiB
21.8 KiB
Reduce unused JavaScript Potential savings of 91 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.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
Google Tag Manager
tag-manager
159.7 KiB
70.7 KiB
86.1 KiB
35.9 KiB
/gtag/js?id=UA-158…-4
(www.googletagmanager.com)
73.7 KiB
34.8 KiB
userway.org
42.5 KiB
20.7 KiB
42.5 KiB
20.7 KiB
Serve images in next-gen formats Potential savings of 116 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.
WordPressConsider using the Performance Lab plugin to automatically convert your uploaded JPEG images into WebP, wherever supported.
URL
Resource Size
Potential Savings
habitatcdd.com
1st party
300.1 KiB
115.6 KiB
body.home > div#panel > div.hero-img
<div class="hero-img" style="background-image: url(&quot;https://habitatcdd.com/wp-content/uploads/2020/03/clo…&quot;);">
231.7 KiB
94.1 KiB
div.main > div.inner-wrap > div.img1 > img
<img src="https://habitatcdd.com/wp-content/uploads/2020/02/PicMonkey-Collage4-768x2…" alt="">
…02/PicMonkey….jpg
(habitatcdd.com)
68.4 KiB
21.5 KiB
Largest Contentful Paint element 5,260 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
body.home > div#panel > div.hero-img
<div class="hero-img" style="background-image: url(&quot;https://habitatcdd.com/wp-content/uploads/2020/03/clo…&quot;);">
Phase
% of LCP
Timing
TTFB
12%
630 ms
Load Delay
63%
3,290 ms
Load Time
18%
940 ms
Render Delay
8%
400 ms
Reduce unused CSS Potential savings of 13 KiB
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
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
Transfer Size
Potential Savings
habitatcdd.com
1st party
13.2 KiB
13.1 KiB
13.2 KiB
13.1 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 9 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 JavaScriptTBT
URL
Potential Savings
userway.org
9.4 KiB
9.4 KiB
Array.prototype.find
habitatcdd.com
1st party
0.1 KiB
0.1 KiB
@babel/plugin-transform-classes
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 about efficient cache policies.
URL
Cache TTL
Transfer Size
habitatcdd.com
1st party
341 KiB
7d
232 KiB
…02/PicMonkey….jpg
(habitatcdd.com)
7d
69 KiB
7d
14 KiB
7d
12 KiB
7d
10 KiB
7d
3 KiB
…build/bundle.css
(habitatcdd.com)
7d
1 KiB
Google Analytics
analytics
21 KiB
/analytics.js
(www.google-analytics.com)
2h
21 KiB
userway.org
2 KiB
/widget.js
(cdn.userway.org)
1h
2 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
habitatcdd.com
1st party
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 how to set image dimensionsCLS
URL
habitatcdd.com
1st party
div.main > div.inner-wrap > div.img1 > img
<img src="https://habitatcdd.com/wp-content/uploads/2020/02/PicMonkey-Collage4-768x2…" alt="">
…02/PicMonkey….jpg
(habitatcdd.com)
Initial server response time was short Root document took 30 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
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
habitatcdd.com
1st party
30 ms
30 ms
Avoids enormous network payloads Total size was 625 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.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
habitatcdd.com
1st party
327.1 KiB
232.0 KiB
…02/PicMonkey….jpg
(habitatcdd.com)
68.9 KiB
13.8 KiB
12.4 KiB
Google Tag Manager
tag-manager
161.1 KiB
86.7 KiB
/gtag/js?id=UA-158…-4
(www.googletagmanager.com)
74.4 KiB
userway.org
56.0 KiB
43.5 KiB
12.5 KiB
Google CDN
cdn
30.3 KiB
…2.2.4/jquery.min.js
(ajax.googleapis.com)
30.3 KiB
Google Analytics
analytics
21.0 KiB
/analytics.js
(www.google-analytics.com)
21.0 KiB
Avoids an excessive DOM size 197 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
197
Maximum DOM Depth
div.bucket-icon-link > a > svg > path
<path d="M26.4 12.2L15.2 23.4l-2.6-2.6L23.8 9.6l2.6 2.6zm.7-.8l1.7-1.7c.4-.4.4-1 0-…">
14
Maximum Child Elements
body.home
<body class="home page-template page-template-templates page-template-home page-templat…">
19
Avoid chaining critical requests 7 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.FCPLCP
Maximum critical path latency: 389.177 ms
Initial Navigation
- 200.783 ms, 12.38 KiB
- 205.518 ms, 13.82 KiB
- 34.6 ms, 2.51 KiB
- 84.63 ms, 10.28 KiB
/widget.js
(cdn.userway.org)
- 19.98 ms, 1.90 KiB
…build/bundle.css
(habitatcdd.com)
- 161.895 ms, 0.98 KiB
…2.2.4/jquery.min.js
(ajax.googleapis.com)
- 5.986 ms, 30.26 KiB
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 how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
Google Tag Manager
tag-manager
272 ms
233 ms
34 ms
150 ms
129 ms
20 ms
/gtag/js?id=UA-158…-4
(www.googletagmanager.com)
123 ms
104 ms
15 ms
Unattributable
237 ms
71 ms
0 ms
Unattributable
237 ms
71 ms
0 ms
habitatcdd.com
1st party
201 ms
5 ms
2 ms
201 ms
5 ms
2 ms
userway.org
151 ms
118 ms
14 ms
151 ms
118 ms
14 ms
Google CDN
cdn
106 ms
81 ms
7 ms
…2.2.4/jquery.min.js
(ajax.googleapis.com)
106 ms
81 ms
7 ms
Google Analytics
analytics
77 ms
69 ms
3 ms
/analytics.js
(www.google-analytics.com)
77 ms
69 ms
3 ms
Minimizes main-thread work 1.1 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
624 ms
Other
235 ms
Style & Layout
114 ms
Script Parsing & Compilation
66 ms
Parse HTML & CSS
37 ms
Rendering
26 ms
Garbage Collection
21 ms
Minimize third-party usage Third-party code blocked the main thread for 100 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
Google Tag Manager
tag-manager
161 KiB
77 ms
87 KiB
72 ms
/gtag/js?id=UA-158…-4
(www.googletagmanager.com)
74 KiB
5 ms
Google Analytics
analytics
21 KiB
15 ms
/analytics.js
(www.google-analytics.com)
21 KiB
15 ms
/j/collect?v=…
(www.google-analytics.com)
0 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
0 KiB
0 ms
Google CDN
cdn
30 KiB
5 ms
…2.2.4/jquery.min.js
(ajax.googleapis.com)
30 KiB
5 ms
userway.org
65 KiB
0 ms
44 KiB
0 ms
12 KiB
0 ms
…images/body_wh.svg
(cdn.userway.org)
3 KiB
0 ms
/widget.js
(cdn.userway.org)
2 KiB
0 ms
…images/spin_wh.svg
(cdn.userway.org)
1 KiB
0 ms
…locales/en-US.json
(cdn.userway.org)
1 KiB
0 ms
…tunings/meyJNWxqzy
(api.userway.org)
1 KiB
0 ms
Avoid long main-thread tasks 8 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
Google Tag Manager
tag-manager
257 ms
4,061 ms
144 ms
/gtag/js?id=UA-158…-4
(www.googletagmanager.com)
2,653 ms
58 ms
/gtag/js?id=UA-158…-4
(www.googletagmanager.com)
2,598 ms
55 ms
Google CDN
cdn
140 ms
…2.2.4/jquery.min.js
(ajax.googleapis.com)
2,130 ms
74 ms
…2.2.4/jquery.min.js
(ajax.googleapis.com)
4,699 ms
66 ms
Unattributable
115 ms
Unattributable
4,205 ms
63 ms
Unattributable
877 ms
52 ms
Google Analytics
analytics
72 ms
/analytics.js
(www.google-analytics.com)
3,762 ms
72 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
Accessibility Menu
<div class="uai userway_dark" id="userwayAccessibilityIcon" aria-label="Accessibility Menu" role="button" tabindex="0" aria-haspopup="dialog" style="background: rgb(95, 60, 57) !important;">
Unsupported CSS Property: background-color
background-color
Unsupported CSS Property: visibility
visibility
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (18)
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.
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 how to minify CSS.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.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.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.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
WordPressConsider using an image optimization WordPress plugin that compresses your images while retaining quality.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.FCPLCP
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 how to preconnect to required origins.FCPLCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.FCPLCP
Preload key requests
Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page load. Learn how to preload key requests.FCPLCP
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 about efficient video formatsLCP
WordPressConsider 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
Preload Largest Contentful Paint image
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
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 about User Timing marks.
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.FCPLCP
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
Element
body.home > div#panel > div.hero-img
<div class="hero-img" style="background-image: url(&quot;https://habitatcdd.com/wp-content/uploads/2020/03/clo…&quot;);">
Avoid large layout shifts
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
Avoids 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().
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 about using the viewport meta tag.TBT
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
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 how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
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 how to avoid focus traps.
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 how to direct focus to new content.
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 about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (24)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[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 about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
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 how to make buttons more accessible.
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 about the alt attribute.
[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 about the viewport meta tag.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
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 about document titles.
[id] attributes on active, focusable elements are unique
All focusable elements must have a unique id to ensure that they're visible to assistive technologies. Learn how to fix duplicate ids.
<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 about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
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 about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
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 about the tabindex attribute.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Values assigned to role="" are valid ARIA roles.
ARIA roles enable assistive technologies to know the role of each element on the web page. If the role values are misspelled, not existing ARIA role values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (37)
Show Hide
[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 about access keys.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
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 about roles and required children elements.
[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 about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
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 about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
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 how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<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 about input image alt text.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
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 about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
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 about the headers attribute.
<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 about table headers.
[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 how to use the lang attribute.
<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 about video captions.
All heading elements contain content.
A heading with no content or inaccessible text prevent screen reader users from accessing information on the page's structure. Learn more about headings.
Document has a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Elements with visible text labels have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Tables use <caption> instead of cells with the [colspan] attribute to indicate a caption.
Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the [colspan] attribute may improve the experience for screen reader users. Learn more about captions.
<td> elements in a large <table> have one or more table headers.
Screen readers have features to make navigating tables easier. Ensuring that <td> elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
2.2.4
WordPress
Passed audits (14)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. 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 about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
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 about the geolocation permission.
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 about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Avoids unload event listeners
The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use pagehide or visibilitychange events instead. Learn more about unload event listeners
No browser errors 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 about this errors in console diagnostic audit
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
habitatcdd.com
1st party
…build/bundle.js.map
(habitatcdd.com)
Error: Timed out fetching resource
Not applicable (1)
Show Hide
Fonts with font-display: optional are preloaded
Preload optional fonts so first-time visitors may use them. Learn more about preloading fonts
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Content Best Practices
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (12)
Show Hide
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 about using the viewport meta tag.TBT
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 about document titles.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
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 about crawler directives.
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 about robots.txt.
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 about the alt attribute.
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 about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Document uses legible font sizes 99.81% legible text
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 about legible font sizes.
Source
Selector
% of Page Text
Font Size
habitatcdd.com
1st party
.header-logo h1 span
0.19%
11.5px
Unattributable
Legible text
99.81%
≥ 12px
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more about avoiding plugins.
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.

As per Chrome’s updated Installability Criteria, Lighthouse will be deprecating the PWA category in a future release. Please refer to the updated PWA documentation for future PWA testing.

    These checks validate the aspects of a Progressive Web App. Learn what makes a good Progressive Web App.
    Installable
    Web app manifest or service worker do not meet the installability requirements 1 reason
    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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.
    Failure reason
    No manifest was fetched
    PWA Optimized
    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 about splash screens.
    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 about theming the address bar.
    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 how to size content for the viewport.
    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 about using the viewport meta tag.TBT
    Manifest doesn't have a maskable icon
    No manifest was fetched
    A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons.
    Additional items to manually check (3)
    Show Hide
    Site works cross-browser
    To reach the most number of users, sites should work across every major browser. Learn about cross-browser compatibility.
    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 about page transitions.
    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 about providing deep links.
    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.