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 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
consent.cookiebot.com/uc.js	229.0 s	27.0 KiB

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:34.026 source:map[type:text value:[unattributed]]]]

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
consent.cookiebot.com/uc.js	27.0 KiB	1.0 s

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
Screenshot of integrations that Toggl Track can connect with `div.css-6f3rui-TrackEaseOfUseTabMobileImage > div.gatsby-image-wrapper > picture > img`	/b/static/c39fa7596c3ecc68b76cd8c8f37f25d0/50892/track-ti...	50.2 KiB	38.2 KiB
Toggl Track reports with illustrations showing desktop and mobile apps, and 100… `div.css-1o1qd6v-HeroImage > div.gatsby-image-wrapper > picture > img`	/b/static/55f8e7a61ed2f30bfc7a3da96da1d3d9/796cf/hero-ima...	30.1 KiB	27.7 KiB
Screenshot of Toggl Track's mobile app and browser extension `div.css-6f3rui-TrackEaseOfUseTabMobileImage > div.gatsby-image-wrapper > picture > img`	/b/static/ccdb5543fa9670a1b98cfc173d81bf9a/526bc/track-ti...	32.1 KiB	26.3 KiB
Screenshot of Toggl Track's automated time tracking feature `div.css-6f3rui-TrackEaseOfUseTabMobileImage > div.gatsby-image-wrapper > picture > img`	/b/static/c6a1141fdb6ef3b893ca827b07e3c4ea/d60b6/track-ti...	24.7 KiB	20.2 KiB
Screenshot of Toggl Track's calendar view `div.css-6f3rui-TrackEaseOfUseTabMobileImage > div.gatsby-image-wrapper > picture > img`	/b/static/56a7029a5ec109530d15c3b054d466e2/8c918/track-ti...	18.4 KiB	13.8 KiB
Companies that use Toggl Track: Amazon, Square, LinkedIn, SAP, Danfoss, Wise, p… `div.css-lnhwn5-Mobile > div.gatsby-image-wrapper > picture > img`	/b/static/fc3155159f83fc4b28f6fbb89592dcc1/49ba6/brands-m...	15.1 KiB	13.6 KiB

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

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.

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.7 s 352.5 KiB

URL	Transfer Size	Est Savings
public-assets.toggl.com/b/app-1be2bda75656c70631d1.js	214.3 KiB	102.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-P9FVGMK	165.7 KiB	77.6 KiB
www.googletagmanager.com/gtag/js?id=G-MP93489PR6&cx=c&gtm=4e64m0h2	163.4 KiB	67.9 KiB
web-assets.track.toggl.com/auth/assets/scripts/main.e11100bbccc6a93e.js	76.7 KiB	52.0 KiB
public-assets.toggl.com/b/framework-57bc66ac07dc918e2458.js	65.1 KiB	31.0 KiB
/cdbd3bbf-7c98-4d02-a856-95a4c6a34ffb/cc.js?renew=false&r...	95.2 KiB	21.2 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
Unattributable	1.2 s	41 ms	0.0 ms
toggl.com/	1.1 s	242 ms	31 ms
/cdbd3bbf-7c98-4d02-a856-95a4c6a34ffb/cc.js?renew=false&r...	916 ms	371 ms	67 ms
public-assets.toggl.com/b/framework-57bc66ac07dc918e2458.js	579 ms	510 ms	31 ms
www.googletagmanager.com/gtm.js?id=GTM-P9FVGMK	467 ms	366 ms	83 ms
www.googletagmanager.com/gtag/js?id=G-MP93489PR6&cx=c&gtm=4e64m0h2	423 ms	334 ms	85 ms
public-assets.toggl.com/b/webpack-runtime-51e6e9abc82c158bbf33.js	305 ms	300 ms	2.3 ms
web-assets.track.toggl.com/auth/assets/scripts/main.e11100bbccc6a93e.js	254 ms	196 ms	47 ms
consent.cookiebot.com/uc.js	251 ms	220 ms	19 ms
public-assets.toggl.com/b/app-1be2bda75656c70631d1.js	212 ms	29 ms	106 ms
/b/81df7b2c1db273d4c9f51bf2ea019b058726c206-a7bf9fd6245eb...	53 ms	35 ms	17 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
Script Evaluation	2.7 s
Other	1.3 s
Parse HTML & CSS	529 ms
Style & Layout	521 ms
Script Parsing & Compilation	506 ms
Garbage Collection	237 ms
Rendering	86 ms

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: 0.0 ms 10.8 KiB

URL	Transfer Size	Est Savings
	13.5 KiB	10.8 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.


Checkmark icon `div.css-131lgiy-CTABox > ul.css-yqm8gx-BulletList > li.css-15octmu-BulletListItem > img`
Checkmark icon `div.css-131lgiy-CTABox > ul.css-yqm8gx-BulletList > li.css-15octmu-BulletListItem > img`
Checkmark icon `div.css-131lgiy-CTABox > ul.css-yqm8gx-BulletList > li.css-15octmu-BulletListItem > img`
Checkmark icon `div.css-131lgiy-CTABox > ul.css-yqm8gx-BulletList > li.css-15octmu-BulletListItem > img`

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

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

●User Timing marks and measures 6 user timings

●Avoid long main-thread tasks 19 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 110 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 110 ms

○INP breakdown

○LCP request discovery

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

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
Privacy Policies `div#CybotCookiebotDialogBodyContentText > p > a > span`
Show details `div#CybotCookiebotDialogBody > div.CybotCookiebotDialogBodyBottomWrapper > div#CybotCookiebotDialogBodyEdgeMoreDetails > a#CybotCookiebotDialogBodyEdgeMoreDetailsLink`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Calendar View `div.css-zoazy8-Wrapper > div.css-lnhwn5-Mobile > div.css-jeyonm-TrackEaseOfUseTabMobile > h4.css-dq1bfg-H4`
For small teams with low budgets `div.css-yimyu5-DoubleCTAContainer > div.css-490dub-CTABoxWrapper > div.css-131lgiy-CTABox > h5.css-3c6rwi-H5`
Time tracking without the micromanagement `div.css-vn9xtc-WhyTrackGrid > div.css-1dzocis-WhyTrackBox > div > h4.css-dq1bfg-H4`
Product `div.css-j3goz1-ProductOnly > div.css-2l6ewq-Lists > div.css-nx96wp-RootList > h5.css-10o1c5y-Title`

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Legal Center Status `section.css-1fefyqh-GlobalFooter > div.css-132zuqc-SizeWrapper > div.css-1s8ykbz-LegalBit > ul.css-dp1dc1-GlobalLinks`

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.

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

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

●`[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

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

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

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

○Identical links have the same purpose.

○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

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
accounts.toggl.com/api/sessions	`Failed to load resource: the server responded with a status of 401 ()`
track.toggl.com/auth	`Invalid 'X-Frame-Options' header encountered when loading 'https://track.toggl.com/': 'ALLOW-FROM *' is not a recognized directive. The header will be ignored.`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
public-assets.toggl.com/b/app-1be2bda75656c70631d1.js

●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

●Displays images with correct aspect ratio

●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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
All Toggl Products `header.css-1fi8uyx-Header > div.css-lktpwj-MiniBar > div.css-1atc77n-MiniBarLinksSection > a.css-1p1skfv-MiniBarAnchor`
Log in `header.css-1fi8uyx-Header > div.css-lktpwj-MiniBar > div.css-1atc77n-MiniBarLinksSection > a.css-1p1skfv-MiniBarAnchor`

To appear in search results, crawlers need access to your app.

○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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`