Skip to content
https://linear.app

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

28

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:151.99 source:map[column:26854 line:15 type:source-location url:https://static.linear.app/web/_next/static/chunks/98618-7606bacba6fa6ef6.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:81.596 source:map[type:text value:[unattributed]]] map[reflowTime:33.135 source:map[column:12621 line:0 type:source-location url:https://static.linear.app/web/_next/static/chunks/21768-fa1cbad521fa3364.js urlProvider:network]] map[reflowTime:70.047 source:map[column:9563 line:3 type:source-location url:https://static.linear.app/web/_next/static/chunks/82097-874e2b764ae01e5f.js urlProvider:network]] map[reflowTime:56.66 source:map[column:41459 line:0 type:source-location url:https://static.linear.app/web/_next/static/chunks/99471-2b0617a052684255.js urlProvider:network]] map[reflowTime:0.615 source:map[column:18077 line:642 type:source-location url:https://static.linear.app/web/_next/static/chunks/22954-2868e106038b9620.js urlProvider:network]] map[reflowTime:24.668 source:map[column:152079 line:0 type:source-location url:https://static.linear.app/web/_next/static/chunks/789a407a-bdda2a4b63247546.js urlProvider:network]] map[reflowTime:78.806 source:map[column:78230 line:0 type:source-location url:https://static.linear.app/web/_next/static/chunks/51755-016265cfbc2f37f5.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.

URLResource SizeEst Savings
div.Bleed_root__EzNZN > div.Frame_wrapper___hKDg > div.Frame_background__iLZh4 > img.Image_root__UkRqc div.Bleed_root__EzNZN > div.Frame_wrapper___hKDg > div.Frame_background__iLZh4 > img.Image_root__UkRqc
/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c7b144b7-4e...308.7 KiB226.5 KiB
div.PageSection_illustration__P1Yb9 > div.show-mobile > div.Bleed_root__EzNZN > img.Image_root__UkRqc div.PageSection_illustration__P1Yb9 > div.show-mobile > div.Bleed_root__EzNZN > img.Image_root__UkRqc
/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c16152f3-a3...107.0 KiB84.2 KiB
div.PageSection_illustration__P1Yb9 > div.show-mobile > div.Bleed_root__EzNZN > img.Image_root__UkRqc div.PageSection_illustration__P1Yb9 > div.show-mobile > div.Bleed_root__EzNZN > img.Image_root__UkRqc
/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/7d7115d9-a0...101.5 KiB79.8 KiB
didier div.SlackIssue_slackBox__GIILV > div.SlackIssue_chatMessages__M7WOf > div.SlackIssue_chatMessage__HOXiM > img.SlackIssue_avatar__SvVIa
/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c8aeedda-77...76.3 KiB75.6 KiB
div.PageSection_illustration__P1Yb9 > div.show-mobile > div.Bleed_root__EzNZN > img.Image_root__UkRqc div.PageSection_illustration__P1Yb9 > div.show-mobile > div.Bleed_root__EzNZN > img.Image_root__UkRqc
/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/584d7dbd-ff...83.1 KiB65.4 KiB
andreas div.SlackIssue_slackBox__GIILV > div.SlackIssue_chatMessages__M7WOf > div.SlackIssue_chatMessage__HOXiM > img.SlackIssue_avatar__SvVIa
/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/22210a73-58...11.3 KiB10.6 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:370.8720000004768 label:Time to first byte subpart:timeToFirstByte] map[duration:412.34499999952317 label:Resource load delay subpart:resourceLoadDelay] map[duration:192.92 label:Resource load duration subpart:resourceLoadDuration] map[duration:4768.617 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: div.Bleed_root__EzNZN > div.Frame_wrapper___hKDg > div.Frame_background__iLZh4 > img.Image_root__UkRqc
path: 1,HTML,1,BODY,1,DIV,3,DIV,1,MAIN,1,DIV,0,DIV,8,DIV,0,DIV,0,DIV,0,IMG
selector: div.Bleed_root__EzNZN > div.Frame_wrapper___hKDg > div.Frame_background__iLZh4 > img.Image_root__UkRqc
snippet: <img data-grain="true" alt="" data-nosnippet="true" data-loaded="true" loading="lazy" width="1920" height="1080" decoding="async" data-nimg="1" class="Image_root__UkRqc" style="color:transparent;opacity:0.08;height:100%" src="https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c7b144b7-4…">

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-0-IMG
nodeLabel: div.Bleed_root__EzNZN > div.Frame_wrapper___hKDg > div.Frame_background__iLZh4 > img.Image_root__UkRqc
path: 1,HTML,1,BODY,1,DIV,3,DIV,1,MAIN,1,DIV,0,DIV,8,DIV,0,DIV,0,DIV,0,IMG
selector: div.Bleed_root__EzNZN > div.Frame_wrapper___hKDg > div.Frame_background__iLZh4 > img.Image_root__UkRqc
snippet: <img data-grain="true" alt="" data-nosnippet="true" data-loaded="true" loading="lazy" width="1920" height="1080" decoding="async" data-nimg="1" class="Image_root__UkRqc" style="color:transparent;opacity:0.08;height:100%" src="https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c7b144b7-4…">

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

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

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.

CategoryTime Spent
Script Evaluation8.1 s
Other5.1 s
Style & Layout3.3 s
Script Parsing & Compilation1.2 s
Parse HTML & CSS704 ms
Rendering530 ms
Garbage Collection284 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 8.6 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
Modern HTTP
Optimize viewport for mobile
Minify JavaScript
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 8 animated elements found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 320 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 350 ms
INP breakdown
User Timing marks and measures
Avoid large layout shifts
79

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > ul.Header_list__gT80u > li.Header_mobileItem__Prlve > button.Header_mobileMenuTrigger__ignIg div > ul.Header_list__gT80u > li.Header_mobileItem__Prlve > button.Header_mobileMenuTrigger__ignIg
div > header.IssueView_header__sldQv > div.Flex_root__DOQCW > button.SharedViewStyles_buttonBase__MNsrT div > header.IssueView_header__sldQv > div.Flex_root__DOQCW > button.SharedViewStyles_buttonBase__MNsrT
div.IssueView_chatBox__mNYgF > div.IssueView_commentBoxContainer__EA6vv > div.IssueView_commentActions__ximTU > button.IssueView_commentButton__vzh05 div.IssueView_chatBox__mNYgF > div.IssueView_commentBoxContainer__EA6vv > div.IssueView_commentActions__ximTU > button.IssueView_commentButton__vzh05
div.IssueView_chatBox__mNYgF > div.IssueView_commentBoxContainer__EA6vv > div.IssueView_commentActions__ximTU > button.IssueView_commentButton__vzh05 div.IssueView_chatBox__mNYgF > div.IssueView_commentBoxContainer__EA6vv > div.IssueView_commentActions__ximTU > button.IssueView_commentButton__vzh05
div.SlackIssue_slackBoxContainer__e8FUr > div.SlackIssue_slackBox__GIILV > header.SlackIssue_header__NtjDx > button.IconButton_root__vP_d_ div.SlackIssue_slackBoxContainer__e8FUr > div.SlackIssue_slackBox__GIILV > header.SlackIssue_header__NtjDx > button.IconButton_root__vP_d_

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.Layout_container__BVtmP > main.Layout_content__PrPCk > div.LayoutContent_root__ZBUya > a.Logos_logosLink__k61eG div.Layout_container__BVtmP > main.Layout_content__PrPCk > div.LayoutContent_root__ZBUya > a.Logos_logosLink__k61eG

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.

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
1.0 div.PageSection_actionWrapper__SpZEC > a.Link_root__cNtak > div.PageSection_action__7OSHK > span.sc-d5151d0-0
2.0 div.PageSection_actionWrapper__SpZEC > a.Link_root__cNtak > div.PageSection_action__7OSHK > span.sc-d5151d0-0
3.0 div.PageSection_actionWrapper__SpZEC > a.Link_root__cNtak > div.PageSection_action__7OSHK > span.sc-d5151d0-0
4.0 div.PageSection_actionWrapper__SpZEC > a.Link_root__cNtak > div.PageSection_action__7OSHK > span.sc-d5151d0-0
5.0 div.PageSection_actionWrapper__SpZEC > a.Link_root__cNtak > div.PageSection_action__7OSHK > span.sc-d5151d0-0

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
Faster app launch div.SharedViewStyles_wrapperWithSidebar__mgB8H > div > div.IssueView_body___grLQ > h3.sc-d5151d0-0

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
Log in Sign up nav.Header_menuRoot__tJRFd > div.Header_innerWrapper__jlvRl > div > ul.Header_list__gT80u

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
Log in ul.Header_list__gT80u > div.Header_rightSideWrapper__v4fej > div.Header_buttons__qwTPf > li.Header_buttonItem__crtcc
Sign up ul.Header_list__gT80u > div.Header_rightSideWrapper__v4fej > div.Header_buttons__qwTPf > li.Header_buttonItem__crtcc

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
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
`[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 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
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.
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.
92

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.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div.Bleed_root__EzNZN > div.Frame_wrapper___hKDg > div.Frame_background__iLZh4 > img.Image_root__UkRqc div.Bleed_root__EzNZN > div.Frame_wrapper___hKDg > div.Frame_background__iLZh4 > img.Image_root__UkRqc
/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c7b144b7-4e...412 x 400 (1.03)1062 x 493 (2.15)

General

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

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.

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

Send Feedback