Skip to content
https://www.loom.com

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.

16

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.236966] map[node:map[boundingRect:map[bottom:14832 height:14651 left:0 right:412 top:181 width:412] lhId:page-1-MAIN nodeLabel:One video is worth a thousand words Easily record and share AI-powered video m… path:1,HTML,1,BODY,0,DIV,0,DIV,3,MAIN selector:body.font-body > div#__next > div > main#skip-to-content snippet:<main id="skip-to-content"> type:node] score:0.236966 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2048 height:348 left:32 right:380 top:1700 width:348] lhId:page-15-IMG nodeLabel:section.lg:px-fluid-base > div.bg-thd-color-blue-70 > picture > img.thd-rounded-int path:1,HTML,1,BODY,0,DIV,0,DIV,3,MAIN,2,SECTION,0,DIV,0,PICTURE,9,IMG selector:section.lg:px-fluid-base > div.bg-thd-color-blue-70 > picture > img.thd-rounded-int snippet:<img alt="" class="thd-rounded-int" height="800" loading="lazy" src="https://cdn.sanity.io/images/pvn35iyy/production/d2a6a742f70d37f11d6cca6bf…" width="800"> type:node]] map[cause:Web font extra:map[type:url value:https://ds-cdn.prod-east.frontend.public.atl-paas.net/assets/fonts/atlassian-sans/v3/AtlassianSans-latin.woff2]]] type:subitems]]]
headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.000241] map[node:map[boundingRect:map[bottom:205 height:23 left:0 right:364 top:182 width:364] lhId:page-0-DIV nodeLabel:Stuck Teams and Challenges path:1,HTML,1,BODY,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV selector:div.video-container > div.LayersContainer > div.controls-layer_wrapper_RAp > div.transportSection snippet:<div class="transportSection css-xyqb2v"> type:node] score:0.00016] map[node:map[boundingRect:map[bottom:209 height:11 left:0 right:11 top:198 width:11] lhId:page-1-DIV nodeLabel:div.transportSection > section.alwaysVisible > div.css-1uofusf > div.css-k6eqbt path:1,HTML,1,BODY,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,SECTION,0,DIV,1,DIV selector:div.transportSection > section.alwaysVisible > div.css-1uofusf > div.css-k6eqbt snippet:<div data-name="ProgressThumb" class="css-k6eqbt"> type:node] score:8.1e-05]]

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:65.337 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
section.lg:px-fluid-base > div.bg-thd-color-blue-70 > picture > img.thd-rounded-int section.lg:px-fluid-base > div.bg-thd-color-blue-70 > picture > img.thd-rounded-int
/images/pvn35iyy/production/d2a6a742f70d37f11d6cca6bfdb1e...263.6 KiB203.2 KiB
div.video-container > div.LayersContainer > div.components_wrapper_cKT > video.components_animatedPreviewVideo_Miy div.video-container > div.LayersContainer > div.components_wrapper_cKT > video.components_animatedPreviewVideo_Miy
/sessions/thumbnails/09b1aa507cb846138847bf8e98b56a71-b52...107.9 KiB81.1 KiB
Jai div.CommentsConversationAnimation_timeline__pGI4g > span.CommentsConversationAnimation_timelineComment__OVE6D > span.CommentsConversationAnimation_timelineAvatarWrapper__jExAG > img.h-full
cdn.loom.com/assets/marketing/bubbs/jai-sm.jpg13.9 KiB13.8 KiB
LaunchDarkly div.rfm-child > ul.grid > li > img.thd-filter
/images/pvn35iyy/production/b74a41f0614f6c513da65947ffcd5...7.4 KiB6.8 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.

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
One video is worth a thousand words Easily record and share AI-powered video m… body.font-body > div#__next > div > main#skip-to-content
0.237
Stuck Teams and Challenges div.video-container > div.LayersContainer > div.controls-layer_wrapper_RAp > div.transportSection
0.000
div.transportSection > section.alwaysVisible > div.css-1uofusf > div.css-k6eqbt div.transportSection > section.alwaysVisible > div.css-1uofusf > div.css-k6eqbt
0.000

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.

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: 2.5 s 1.5 MiB
URLTransfer SizeEst Savings
cdn.loom.com/assets/js/embed-video-8f4922ebfad0a2f0.js744.1 KiB334.3 KiB
cdn.loom.com/assets/js/vendor-518a401a-31c9c6e7b244dacd.js177.8 KiB156.9 KiB
www.loom.com/_next/static/chunks/pages/_app-67a2568e1fd2dd38.js228.4 KiB147.6 KiB
cdn.loom.com/assets/js/vendor-1-24b8eadc1c473dfb.js58.4 KiB58.2 KiB
cdn.loom.com/assets/js/vendor-39-358b691d007642eb.js57.8 KiB54.3 KiB
cdn.loom.com/assets/js/vendor-26-3a9300c9ffbe37d4.js52.9 KiB52.1 KiB
cdn.loom.com/assets/js/vendor-15-dde030cc82ef5af8.js47.4 KiB43.5 KiB
cdn.loom.com/assets/js/vendor-41-b27b1cc1f2cf4533.js53.4 KiB42.4 KiB
cdn.loom.com/assets/js/vendor-36-c035baa3c8715172.js68.0 KiB42.2 KiB
cdn.loom.com/assets/js/vendor-35-dfffd377479ad1e6.js45.1 KiB40.8 KiB
cdn.loom.com/assets/js/vendor-49-1d55568bb0a07e35.js49.4 KiB40.1 KiB
cdn.loom.com/assets/js/vendor-0-6631d38877f33710.js37.3 KiB37.2 KiB
cdn.loom.com/assets/js/vendor-20-264c5c62e6a4b421.js52.3 KiB35.3 KiB
cdn.loom.com/assets/js/vendor-38-5adfe845d23faa89.js53.6 KiB34.7 KiB
cdn.loom.com/assets/js/vendor-47-7fb397e04f5c9048.js44.0 KiB33.8 KiB
cdn.loom.com/assets/js/vendor-50-6f53dc94af196915.js55.3 KiB33.1 KiB
cdn.loom.com/assets/js/vendor-9-9e7574b35d46c5f0.js37.6 KiB32.0 KiB
cdn.loom.com/assets/js/vendor-33-74a0c550fe14886c.js40.2 KiB31.7 KiB
cdn.loom.com/assets/js/vendor-34-c321891089278909.js49.3 KiB30.6 KiB
cdn.loom.com/assets/js/vendor-31-16af2a25483ff41f.js31.9 KiB29.5 KiB
cdn.loom.com/assets/js/vendor-32-ef9c22e9c1bb03e0.js31.9 KiB28.9 KiB
cdn.loom.com/assets/js/vendor-37-01389623e8cf0b27.js29.4 KiB27.4 KiB
www.loom.com/_next/static/chunks/3914-c8cbc6a343dbf705.js49.2 KiB27.2 KiB
cdn.loom.com/assets/js/vendor-43-99457c65238ba7ad.js33.0 KiB24.8 KiB
cdn.loom.com/assets/js/vendor-46-06a56d68ec3594df.js25.8 KiB23.3 KiB
cdn.loom.com/assets/js/vendor-19-3ccde004b6cbcc76.js70.6 KiB22.7 KiB
www.loom.com/_next/static/chunks/4582-a2b5ac0573dba7dc.js26.6 KiB20.8 KiB
cdn.loom.com/assets/js/vendor-24-5a216a028d69c52d.js24.5 KiB20.1 KiB

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation5.4 s
Other2.2 s
Style & Layout1.3 s
Script Parsing & Compilation1.3 s
Rendering627 ms
Garbage Collection184 ms
Parse HTML & CSS150 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in a sub frame.Actionable
Pages with WebSocket cannot enter back/forward cache.Pending browser support

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

Document request latency
Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Network dependency tree
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 16 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 9 animated elements found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 130 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 70 ms
INP breakdown
LCP request discovery
88

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.bg-thd-color-blue-70 > div.thd-container-max > div.absolute > button.css-1vfng2u div.bg-thd-color-blue-70 > div.thd-container-max > div.absolute > button.css-1vfng2u

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.

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
Sales Personalize your pitch with video outreach to close more deals. Enginee… main#skip-to-content > section.mb-fluid-md > section.thd-container-max > ul.mx-auto

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Pause recording in animation div.RecordScreenAnimation_controls__QF857 > div.RecordScreenAnimation_controlsButtonWrapper__xVVXl > div.css-nez7wg > button.RecordScreenAnimation_controlsButton__tRpOw
Cancel recording in animation div.RecordScreenAnimation_controls__QF857 > div.RecordScreenAnimation_controlsButtonWrapper__xVVXl > div.css-nez7wg > button.RecordScreenAnimation_controlsButton__tRpOw

These items highlight common accessibility best practices.

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
`[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
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<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
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"]`
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with 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
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
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
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

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 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 browser errors logged to the console
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
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
92

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.loom.com/securityLearn more
www.loom.com/enterpriseLearn more

Format your HTML in a way that enables crawlers to better understand your app’s content.

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 are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback