Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est 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.png	421.1 KiB	409.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.webp	96.6 KiB	83.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.webp	55.2 KiB	50.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 KiB	23.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 KiB	19.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 KiB	14.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 KiB	13.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 KiB	10.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 KiB	9.9 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.todoist.com/_astro/index.DAfKt5uT.css	1.5 KiB
www.todoist.com/_astro/_slug_.-6Uo_yjt.css	73.0 KiB	750 ms
www.todoist.com/_astro/_slug_.CwMIkVzm.css	1.6 KiB
www.todoist.com/_astro/index.1pp5_YPP.css	2.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
cdn.requestmetrics.com/agent/current/rm.js	1200.0 s	14.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 300 ms 59.4 KiB

URL	Transfer Size	Est Savings
www.todoist.com/_astro/_slug_.-6Uo_yjt.css	72.6 KiB	59.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 900 ms 157.1 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-L1YQDZCTV5&cx=c&gtm=4e6460	168.6 KiB	68.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-KW4J5DNZ	159.5 KiB	63.5 KiB
www.todoist.com/_astro/client.BWFqRWag.js	69.7 KiB	25.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.todoist.com/	1.0 s	41 ms	8.0 ms
Unattributable	935 ms	86 ms	0.0 ms
www.todoist.com/_astro/index.DKtf60Sy.js	726 ms	157 ms	0.4 ms
www.googletagmanager.com/gtag/js?id=G-L1YQDZCTV5&cx=c&gtm=4e6460	347 ms	281 ms	62 ms
www.googletagmanager.com/gtm.js?id=GTM-KW4J5DNZ	297 ms	234 ms	61 ms
www.todoist.com/_astro/ScrollTrigger.h_CMBckj.js	266 ms	64 ms	0.3 ms
www.todoist.com/_astro/client.BWFqRWag.js	260 ms	226 ms	0.6 ms
www.todoist.com/_astro/ScrollTrigger.BWsqEc1I.js	230 ms	117 ms	0.3 ms
tr.capterra.com/static/vcvr.js	69 ms	54 ms	9.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Other	1.4 s
Script Evaluation	1.3 s
Style & Layout	1.2 s
Rendering	184 ms
Script Parsing & Compilation	153 ms
Parse HTML & CSS	84 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.todoist.com/_astro/poster-image.2nEMsGp8.png	422.0 KiB
www.todoist.com/_astro/headerui.en.Cz2t5aii_2dMsRv.webp	223.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=4e6460	168.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-KW4J5DNZ	159.9 KiB
www.todoist.com/_astro/headerui.en.DAyuar6R_Z1JX863.webp	97.1 KiB
/imagist/video/upload/f_auto,q_auto/v1755547677/product-u...	91.1 KiB
www.todoist.com/_astro/fonts/1e49bd114953732c.woff2	83.6 KiB
www.todoist.com/_astro/fonts/5719a40fc9dc4087.woff2	77.8 KiB
www.todoist.com/_astro/_slug_.-6Uo_yjt.css	73.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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Best Practices

User Experience

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect 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.webp	500 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source Description

Source	Description
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)

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