C — https://www.ifttt.com | BeaverCheck Audit

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

13 link(s) with no accessible text

Accessibility › Link & Button Quality

24 image(s) missing alt attribute

Accessibility › Alt Text Quality

24 image-in-link without alt text

Accessibility › Alt Text Quality

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Cross-Origin-Opener-Policy header is missing

Security › Security Headers

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.ifttt.com)](https://beavercheck.com/results/91a2e13c-2567-8ca9-8b66-2cd18b35c3c6)

HTML

<a href="https://beavercheck.com/results/91a2e13c-2567-8ca9-8b66-2cd18b35c3c6"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.ifttt.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.ifttt.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.95 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

8.05 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

318 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.30 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

8.09 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
ifttt.com/lib.min.js	600.0 s	32.3 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 964 ms

URL	Time Spent
www.ifttt.com/	964 ms
ifttt.com/	0.0 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

Diagnostics

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.

Estimated savings: 150 ms 21.7 KiB

URL	Transfer Size	Est Savings
web-assets.ifttt.com/builds/assets/customer-CKfQr7xQ.css	25.5 KiB	21.7 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.

Estimated savings: 1.2 s 200.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-NNB6HCT	145.9 KiB	81.7 KiB
www.googletagmanager.com/gtag/js?id=G-LW9TEDF6M2&cx=c&gtm=4e6460	174.8 KiB	71.1 KiB
web-assets.ifttt.com/builds/assets/header-BL1JXuXM.js	98.1 KiB	47.6 KiB

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 work

Category	Time Spent
Script Evaluation	1.1 s
Other	1.0 s
Style & Layout	562 ms
Script Parsing & Compilation	124 ms
Rendering	107 ms
Parse HTML & CSS	68 ms

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,517 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 1.1 s

●Avoid long main-thread tasks 11 long tasks found

●Avoid non-composited animations 6 animated elements found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 170 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 40 ms

○INP breakdown

○LCP request discovery

○Avoid large layout shifts

Accessibility

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Save new Spotify Discover Weekly songs to an archive `a.applet-card-body > div.content > div.title > span`
Spotify `a.applet-card-body > div.content > div.owner > span.author`
124K `a.applet-card-body > div.meta > span.installs > span.number`
Google `a.applet-card-body > div.content > div.owner > span.author`
132K `a.applet-card-body > div.meta > span.installs > span.number`
div.content > div.owner > span > span.by `div.content > div.owner > span > span.by`
div.content > div.owner > span > span.author `div.content > div.owner > span > span.author`
a.applet-card-body > div.meta > span.installs > span.number `a.applet-card-body > div.meta > span.installs > span.number`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.user-testimonial-card-wrapper > div.user-testimonial-card > div.user-testimonial-card__quote > p.user-testimonial-card__quote-text `div.user-testimonial-card-wrapper > div.user-testimonial-card > div.user-testimonial-card__quote > p.user-testimonial-card__quote-text`
div.user-testimonial-card > div.user-testimonial-card__person > div.user-testimonial-card__profile > p.user-testimonial-card__profile-name `div.user-testimonial-card > div.user-testimonial-card__person > div.user-testimonial-card__profile > p.user-testimonial-card__profile-name`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
main.bg--white > section.how-it-works > div.how-it-works-container > a.how-it-works-animation `main.bg--white > section.how-it-works > div.how-it-works-container > a.how-it-works-animation`

These 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.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]`s are contained by their required parent element

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Loading-dots icon `section.recent-searches > ul.universal-search-helper-list > li.loading-dots > img`	web-assets.ifttt.com/builds/assets/loading-dots-DNfj1gr9.gif	32 x 32 (1.00)	150 x 343 (0.44)
Loading-dots icon `section.search-preview > ul.universal-search-helper-list > li.loading-dots > img`	web-assets.ifttt.com/builds/assets/loading-dots-DNfj1gr9.gif	32 x 32 (1.00)	150 x 343 (0.44)

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

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.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.41 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.41 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

12 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.020

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.43 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.95 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
ifttt.com/lib.min.js	600.0 s	32.3 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 0.0 ms 200.4 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-NNB6HCT	145.9 KiB	81.7 KiB
www.googletagmanager.com/gtag/js?id=G-LW9TEDF6M2&cx=c&gtm=4e6460	174.8 KiB	71.1 KiB
web-assets.ifttt.com/builds/assets/header-BL1JXuXM.js	98.1 KiB	47.6 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.

Estimated savings: 0.0 ms 21.8 KiB

URL	Transfer Size	Est Savings
web-assets.ifttt.com/builds/assets/customer-CKfQr7xQ.css	25.5 KiB	21.8 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 393 ms

URL	Time Spent
www.ifttt.com/	393 ms
ifttt.com/	0.0 ms

●Time to Interactive 2.0 s

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,526 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 2 long tasks found

●Avoid non-composited animations 6 animated elements found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 40 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

Accessibility

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Save new Spotify Discover Weekly songs to an archive `a.applet-card-body > div.content > div.title > span`
Spotify `a.applet-card-body > div.content > div.owner > span.author`
124K `a.applet-card-body > div.meta > span.installs > span.number`
Google `a.applet-card-body > div.content > div.owner > span.author`
132K `a.applet-card-body > div.meta > span.installs > span.number`
by `div.content > div.owner > span > span.by`
IFTTT `div.content > div.owner > span > span.author`
16.6K `a.applet-card-body > div.meta > span.installs > span.number`
Todoist `a.applet-card-body > div.content > div.owner > span.author`
19K `a.applet-card-body > div.meta > span.installs > span.number`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`

These are opportunities to improve the legibility of your content.

Names and labels

Failing Elements
main.bg--white > section.how-it-works > div.how-it-works-container > a.how-it-works-animation `main.bg--white > section.how-it-works > div.how-it-works-container > a.how-it-works-animation`

These 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.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]`s are contained by their required parent element

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Loading-dots icon `section.recent-searches > ul.universal-search-helper-list > li.loading-dots > img`	web-assets.ifttt.com/builds/assets/loading-dots-DNfj1gr9.gif	32 x 32 (1.00)	150 x 343 (0.44)
Loading-dots icon `section.search-preview > ul.universal-search-helper-list > li.loading-dots > img`	web-assets.ifttt.com/builds/assets/loading-dots-DNfj1gr9.gif	32 x 32 (1.00)	150 x 343 (0.44)

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.ifttt.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

User Experience

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

User Experience

SEO

Keyboard Shortcuts