Skip to content
Audit Complete

Results for https://www.todoist.com

Visit site
Spain Spain · Madrid Completed: Apr 7, 2026 20:41 UTC
Share card preview
Share on X Share on LinkedIn Share on Reddit Share on Hacker News Share via Email Download share image
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C76

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)

1

Content-Security-Policy header is missing

Security › Security Headers
2

Cookie 'NEXT_LOCALE' is missing the Secure flag

Security › Cookie Security
3

No Content-Security-Policy header found

Security › Content Security Policy
4

No <main> landmark found

Accessibility › Landmark Structure
5

129 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.todoist.com)](https://beavercheck.com/results/7589216c-55d6-71d1-554f-778429f30de6)
<a href="https://beavercheck.com/results/7589216c-55d6-71d1-554f-778429f30de6"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.todoist.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.todoist.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

53
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
90
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

6.17 s

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

15.01 s

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

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

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

15.42 s

Detailed Report

Audit breakdown by category with detailed findings.

53

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 forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:158.255 source:map[column:383 line:0 type:source-location url: urlProvider:network]] map[reflowTime:35.568 source:map[column:24981 line:14 type:source-location url:https://www.todoist.com/_astro/ScrollTrigger.h_CMBckj.js urlProvider:network]] map[reflowTime:0.318 source:map[column:6057 line:14 type:source-location url:https://www.todoist.com/_astro/ScrollTrigger.h_CMBckj.js urlProvider:network]] map[reflowTime:0.309 source:map[column:5088 line:14 type:source-location url:https://www.todoist.com/_astro/ScrollTrigger.h_CMBckj.js urlProvider:network]] map[reflowTime:12.116 source:map[column:2302 line:14 type:source-location url:https://www.todoist.com/_astro/ScrollTrigger.h_CMBckj.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
div.mbe-96 > video-player.video-container > div.thumbnail > img div.mbe-96 > video-player.video-container > div.thumbnail > img
www.todoist.com/_astro/poster-image.2nEMsGp8.png421.1 KiB409.1 KiB
Todoist app interface showing daily tasks, projects, and team sections with a m… div.hero > div.illustration > div.image-container > img.foreground-image
www.todoist.com/_astro/headerui.en.DAyuar6R_Z1JX863.webp96.6 KiB83.9 KiB
div.image-column > video-player.video-container > div.thumbnail > img div.image-column > video-player.video-container > div.thumbnail > img
www.todoist.com/_astro/ai-video-thumbnail.CZxmLcd8_Z2mIDIL.webp55.2 KiB50.8 KiB
div.mbs-32 > div.video-container > astro-island > video div.mbs-32 > div.video-container > astro-island > video
/imagist/video/upload/f_auto,so_0.1/f_auto,q_auto/v175554...26.3 KiB23.8 KiB
li > div.mobile-template-card > div.mobile-template-image > img li > div.mobile-template-card > div.mobile-template-image > img
/dm4oa8qtogq0/1la3hgXN3C6hvQI6IulAKV/14b9e9e3675dea1a0d8b...20.3 KiB19.1 KiB
li > div.mobile-template-card > div.mobile-template-image > img li > div.mobile-template-card > div.mobile-template-image > img
/dm4oa8qtogq0/15OVPgnxNOQKhBmfbiju8D/6237caafe7e2eb3efd98...15.2 KiB14.0 KiB
div.mbs-32 > div.video-container > astro-island > video div.mbs-32 > div.video-container > astro-island > video
/imagist/video/upload/f_auto,so_0.1/f_auto,q_auto/v175554...14.5 KiB13.1 KiB
div.mbs-32 > div.video-container > astro-island > video div.mbs-32 > div.video-container > astro-island > video
/imagist/video/upload/f_auto,so_0.1/f_auto,q_auto/v175554...11.6 KiB10.5 KiB
div.mbs-32 > div.video-container > astro-island > video div.mbs-32 > div.video-container > astro-island > video
/imagist/video/upload/f_auto,so_0.1/f_auto,q_auto/v176828...11.0 KiB9.9 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-1-IMG
nodeLabel: Todoist app interface showing daily tasks, projects, and team sections with a m…
path: 1,HTML,1,BODY,0,DIV,7,DIV,1,DIV,0,DIV,2,IMG
selector: div.hero > div.illustration > div.image-container > img.foreground-image
snippet: <img src="/_astro/headerui.en.DAyuar6R_Z1JX863.webp" alt="Todoist app interface showing daily tasks, projects, and team sections wit…" loading="eager" data-astro-cid-e7pltk5b="true" decoding="async" fetchpriority="auto" width="1000" height="933" class="foreground-image foreground-image-narrow">

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

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URLTransfer SizeDuration
www.todoist.com/_astro/index.DAfKt5uT.css1.5 KiB
www.todoist.com/_astro/_slug_.-6Uo_yjt.css73.0 KiB750 ms
www.todoist.com/_astro/_slug_.CwMIkVzm.css1.6 KiB
www.todoist.com/_astro/index.1pp5_YPP.css2.2 KiB

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

RequestCache TTLTransfer Size
cdn.requestmetrics.com/agent/current/rm.js1200.0 s14.7 KiB

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

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

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.

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: 300 ms 59.4 KiB
URLTransfer SizeEst Savings
www.todoist.com/_astro/_slug_.-6Uo_yjt.css72.6 KiB59.4 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: 900 ms 157.1 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-L1YQDZCTV5&cx=c&gtm=4e6460168.6 KiB68.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-KW4J5DNZ159.5 KiB63.5 KiB
www.todoist.com/_astro/client.BWFqRWag.js69.7 KiB25.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 reduce Javascript execution time.

URLTotal CPU TimeScript EvaluationScript Parse
www.todoist.com/1.0 s41 ms8.0 ms
Unattributable935 ms86 ms0.0 ms
www.todoist.com/_astro/index.DKtf60Sy.js726 ms157 ms0.4 ms
www.googletagmanager.com/gtag/js?id=G-L1YQDZCTV5&cx=c&gtm=4e6460347 ms281 ms62 ms
www.googletagmanager.com/gtm.js?id=GTM-KW4J5DNZ297 ms234 ms61 ms
www.todoist.com/_astro/ScrollTrigger.h_CMBckj.js266 ms64 ms0.3 ms
www.todoist.com/_astro/client.BWFqRWag.js260 ms226 ms0.6 ms
www.todoist.com/_astro/ScrollTrigger.BWsqEc1I.js230 ms117 ms0.3 ms
tr.capterra.com/static/vcvr.js69 ms54 ms9.8 ms

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

CategoryTime Spent
Other1.4 s
Script Evaluation1.3 s
Style & Layout1.2 s
Rendering184 ms
Script Parsing & Compilation153 ms
Parse HTML & CSS84 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URLTransfer Size
www.todoist.com/_astro/poster-image.2nEMsGp8.png422.0 KiB
www.todoist.com/_astro/headerui.en.Cz2t5aii_2dMsRv.webp223.6 KiB
/imagist/video/upload/f_auto,q_auto/v1755547706/product-u...192.9 KiB
www.googletagmanager.com/gtag/js?id=G-L1YQDZCTV5&cx=c&gtm=4e6460168.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-KW4J5DNZ159.9 KiB
www.todoist.com/_astro/headerui.en.DAyuar6R_Z1JX863.webp97.1 KiB
/imagist/video/upload/f_auto,q_auto/v1755547677/product-u...91.1 KiB
www.todoist.com/_astro/fonts/1e49bd114953732c.woff283.6 KiB
www.todoist.com/_astro/fonts/5719a40fc9dc4087.woff277.8 KiB
www.todoist.com/_astro/_slug_.-6Uo_yjt.css73.0 KiB

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 10 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 80 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 40 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
90

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.

ARIA

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.

Failing Elements
body.todoistTheme > div.appContainer > astro-island > div._overlay_1d1qk_6 body.todoistTheme > div.appContainer > astro-island > div._overlay_1d1qk_6

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

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

Failing Elements
Start for free li._mobileRegisterItem_1v9k5_27 > span._navbarItem_53i31_1 > a._text_qx30j_1 > span._textWrapper_1yend_73
Clear your mind div > div.text-lock-up > div.text-container > p._text_qx30j_1
Plan with confidence div > div.text-lock-up > div.text-container > p._text_qx30j_1

These are opportunities to improve the legibility of your content.

Tables and lists

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.

Failing Elements
Work Accounting Tasks Business Travel Packing div._hidden_snh3y_1 > feature-radio-tile-group.mbe-24 > ul > li
Personal div._hidden_snh3y_1 > feature-radio-tile-group.mbe-24 > ul > li
Education div._hidden_snh3y_1 > feature-radio-tile-group.mbe-24 > ul > li
Management div._hidden_snh3y_1 > feature-radio-tile-group.mbe-24 > ul > li
Marketing & Sales div._hidden_snh3y_1 > feature-radio-tile-group.mbe-24 > ul > li
Customer Support div._hidden_snh3y_1 > feature-radio-tile-group.mbe-24 > ul > li

These are opportunities to improve the experience of reading tabular or list data using 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
●`[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.
●Select elements have associated label elements.
●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
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○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.
○Identical links have the same purpose.
○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.
92

Best Practices

User Experience

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

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div.hero > div.illustration > div.image-container > img.background-image div.hero > div.illustration > div.image-container > img.background-image
www.todoist.com/_astro/background.BbIjsenq_13uyaQ.webp500 x 590 (0.85)590 x 332 (1.78)

General

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

SourceDescription
www.todoist.com/_astro/client.BWFqRWag.js line 23, col 24704
Error: Minified React error #418; visit https://react.dev/errors/418?args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at da (https://www.todoist.com/_astro/client.BWFqRWag.js:24:24705) at A1 (https://www.todoist.com/_astro/client.BWFqRWag.js:24:73925) at w1 (https://www.todoist.com/_astro/client.BWFqRWag.js:24:106263) at _h (https://www.todoist.com/_astro/client.BWFqRWag.js:24:106236) at Nh (https://www.todoist.com/_astro/client.BWFqRWag.js:24:106097) at C1 (https://www.todoist.com/_astro/client.BWFqRWag.js:24:101993) at fv (https://www.todoist.com/_astro/client.BWFqRWag.js:24:113630) at MessagePort.Ea (https://www.todoist.com/_astro/client.BWFqRWag.js:9:1650)
●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 issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

87
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
90
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
88
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

895 ms

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

2.25 s

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

0 ms

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

0.040

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

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

2.26 s

Detailed Report

Audit breakdown by category with detailed findings.

87

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 forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:125.405 source:map[type:text value:[unattributed]]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
div.mbe-96 > video-player.video-container > div.thumbnail > img div.mbe-96 > video-player.video-container > div.thumbnail > img
www.todoist.com/_astro/poster-image.2nEMsGp8.png421.1 KiB312.5 KiB
Todoist app interface showing daily tasks, projects, and team sections with a m… div.hero > div.illustration > div.image-container > img.foreground-image
www.todoist.com/_astro/headerui.en.Cz2t5aii_2dMsRv.webp222.9 KiB205.9 KiB
li > div.icon-card > div.image-container > img li > div.icon-card > div.image-container > img
/dm4oa8qtogq0/6TiTWjSetzQYlfaCmDNDLc/9a3e60cc7022ba15b340...40.1 KiB38.5 KiB
li > div.icon-card > div.image-container > img li > div.icon-card > div.image-container > img
/dm4oa8qtogq0/1la3hgXN3C6hvQI6IulAKV/14b9e9e3675dea1a0d8b...27.0 KiB25.4 KiB
li > div.icon-card > div.image-container > img li > div.icon-card > div.image-container > img
/dm4oa8qtogq0/4jRfVdAdXfu3MfxWkN4Mct/d10e07e3fb8476bc0eb9...23.2 KiB21.5 KiB
li > div.icon-card > div.image-container > img li > div.icon-card > div.image-container > img
/dm4oa8qtogq0/1BRIRjqHOIp5yftZ1FIskk/c1100be22568f4ed2a92...21.6 KiB20.0 KiB
div > div.video-container > astro-island > video div > div.video-container > astro-island > video
/imagist/video/upload/f_auto,so_0.1/f_auto,q_auto/v175554...26.3 KiB19.7 KiB
li > div.icon-card > div.image-container > img li > div.icon-card > div.image-container > img
/dm4oa8qtogq0/15OVPgnxNOQKhBmfbiju8D/6237caafe7e2eb3efd98...20.4 KiB18.8 KiB
div._hidden_snh3y_1 > div.soc-banner-container > div.soc-banner > img div._hidden_snh3y_1 > div.soc-banner-container > div.soc-banner > img
www.todoist.com/static/soc-badge.png15.6 KiB13.6 KiB
div > div.video-container > astro-island > video div > div.video-container > astro-island > video
/imagist/video/upload/f_auto,so_0.1/f_auto,q_auto/v175554...14.5 KiB10.9 KiB
div > div.video-container > astro-island > video div > div.video-container > astro-island > video
/imagist/video/upload/f_auto,so_0.1/f_auto,q_auto/v175554...11.6 KiB8.7 KiB
div > div.video-container > astro-island > video div > div.video-container > astro-island > video
/imagist/video/upload/f_auto,so_0.1/f_auto,q_auto/v176828...11.0 KiB8.2 KiB
techradar customer logo div.grid > div.publication-quote > div.logo-container > img
/imagist/image/upload/h_114,e_colorize,o_48,co_rgb:17150f...4.1 KiB4.0 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-13-IMG
nodeLabel: body.todoistTheme > div.appContainer > div.customer-logos-container > img.background-image
path: 1,HTML,1,BODY,0,DIV,8,DIV,0,IMG
selector: body.todoistTheme > div.appContainer > div.customer-logos-container > img.background-image
snippet: <img src="/_astro/customer-logos-bg@2x.D5n6rzYt_Z1SnH15.webp" alt="" data-astro-cid-qbu6glj3="true" loading="lazy" decoding="async" fetchpriority="auto" width="1512" height="332" class="background-image">

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
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URLTransfer SizeDuration
www.todoist.com/_astro/_slug_.-6Uo_yjt.css72.9 KiB467 ms
www.todoist.com/_astro/index.DAfKt5uT.css1.4 KiB231 ms
www.todoist.com/_astro/index.1pp5_YPP.css2.1 KiB231 ms
www.todoist.com/_astro/_slug_.CwMIkVzm.css1.5 KiB231 ms

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

RequestCache TTLTransfer Size
cdn.requestmetrics.com/agent/current/rm.js1200.0 s14.7 KiB

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

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: 60 ms 58.0 KiB
URLTransfer SizeEst Savings
www.todoist.com/_astro/_slug_.-6Uo_yjt.css72.5 KiB58.0 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: 60 ms 156.5 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-L1YQDZCTV5&cx=c&gtm=4e6460h1168.6 KiB68.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-KW4J5DNZ159.5 KiB63.0 KiB
www.todoist.com/_astro/client.BWFqRWag.js69.8 KiB25.2 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URLTransfer Size
www.todoist.com/_astro/poster-image.2nEMsGp8.png421.5 KiB
www.todoist.com/_astro/headerui.en.Cz2t5aii_2dMsRv.webp223.3 KiB
www.googletagmanager.com/gtag/js?id=G-L1YQDZCTV5&cx=c&gtm=4e6460h1168.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-KW4J5DNZ159.8 KiB
www.todoist.com/_astro/headerui.en.DAyuar6R_Z1JX863.webp96.9 KiB
/imagist/video/upload/f_auto,q_auto/v1755547632/product-u...92.3 KiB
www.todoist.com/_astro/fonts/1e49bd114953732c.woff283.6 KiB
www.todoist.com/_astro/fonts/5719a40fc9dc4087.woff277.8 KiB
www.todoist.com/_astro/_slug_.-6Uo_yjt.css72.9 KiB
www.todoist.com/_astro/client.BWFqRWag.js70.1 KiB

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

●Time to Interactive 2.3 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 50 ms
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 5 user timings
●JavaScript execution time 0.3 s
●Minimizes main-thread work 1.2 s
●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 90 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 100 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○Avoid long main-thread tasks
○Avoid non-composited animations
90

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.

ARIA

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.

Failing Elements
body.todoistTheme > div.appContainer > astro-island > div._overlay_1d1qk_6 body.todoistTheme > div.appContainer > astro-island > div._overlay_1d1qk_6

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

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

Failing Elements
Start for free ul._navbarItemGroup_ue8ah_1 > li._navbarItem_53i31_1 > a._text_qx30j_1 > span._textWrapper_1yend_73
Clear your mind div > div.text-lock-up > div.text-container > p._text_qx30j_1
Plan with confidence div > div.text-lock-up > div.text-container > p._text_qx30j_1

These are opportunities to improve the legibility of your content.

Tables and lists

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.

Failing Elements
Work div._hidden_snh3y_1 > div.mbe-24 > ul > li
Personal div._hidden_snh3y_1 > div.mbe-24 > ul > li
Education div._hidden_snh3y_1 > div.mbe-24 > ul > li
Management div._hidden_snh3y_1 > div.mbe-24 > ul > li
Marketing & Sales div._hidden_snh3y_1 > div.mbe-24 > ul > li
Customer Support div._hidden_snh3y_1 > div.mbe-24 > ul > li

These are opportunities to improve the experience of reading tabular or list data using 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
●`[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.
●Select elements have associated label elements.
●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
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○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.
○Identical links have the same purpose.
○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.
88

Best Practices

User Experience

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

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div.hero > div.illustration > div.image-container > img.background-image div.hero > div.illustration > div.image-container > img.background-image
www.todoist.com/_astro/background.BbIjsenq_13uyaQ.webp728 x 590 (1.23)590 x 332 (1.78)

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

URLDisplayed sizeActual sizeExpected size
div.hero > div.illustration > div.image-container > img.background-image div.hero > div.illustration > div.image-container > img.background-image
www.todoist.com/_astro/background.BbIjsenq_13uyaQ.webp728 x 590590 x 332728 x 590

General

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

SourceDescription
www.todoist.com/_astro/client.BWFqRWag.js line 23, col 24704
Error: Minified React error #418; visit https://react.dev/errors/418?args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at da (https://www.todoist.com/_astro/client.BWFqRWag.js:24:24705) at A1 (https://www.todoist.com/_astro/client.BWFqRWag.js:24:73925) at w1 (https://www.todoist.com/_astro/client.BWFqRWag.js:24:106263) at _h (https://www.todoist.com/_astro/client.BWFqRWag.js:24:106236) at Nh (https://www.todoist.com/_astro/client.BWFqRWag.js:24:106097) at C1 (https://www.todoist.com/_astro/client.BWFqRWag.js:24:101993) at fv (https://www.todoist.com/_astro/client.BWFqRWag.js:24:113630) at MessagePort.Ea (https://www.todoist.com/_astro/client.BWFqRWag.js:9:1650)
●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
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback