Mobile 375 × 812

Desktop 1440 × 900

Score: 73 / 100
Based on 8 categories, 0 sections
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
No Content-Security-Policy header found
Page weighs 14.8 MB (5.6 MB transferred)
2 button(s) with no accessible text
4 image-only link(s) without alt text
[](https://beavercheck.com/results/f6d78266-6daf-f7e1-5b1b-9850e8e17f76)<a href="https://beavercheck.com/results/f6d78266-6daf-f7e1-5b1b-9850e8e17f76"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.loom.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.loom.comThis badge auto-updates with your latest scan result.
Thanks for your feedback!
Industry-standard audits powered by Google Lighthouse.
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.
5.71 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
13.22 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.19 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.237
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
11.05 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.
27.75 s
Audit breakdown by category with detailed findings.
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 long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| /sessions/thumbnails/09b1aa507cb846138847bf8e98b56a71-b52... | 0.0 ms | 1.3 MiB |
| /sessions/thumbnails/09b1aa507cb846138847bf8e98b56a71-b52... | 0.0 ms | 108.5 KiB |
| cdn.loom.com/assets/marketing/fonts/Charlie_Display-Bold.woff2 | 0.0 ms | 27.2 KiB |
| cdn.loom.com/assets/marketing/fonts/Charlie_Text-Bold.woff2 | 0.0 ms | 26.3 KiB |
| cdn.loom.com/assets/marketing/fonts/Charlie_Text-Semibold.woff2 | 0.0 ms | 25.7 KiB |
| cdn.loom.com/assets/marketing/fonts/Charlie_Text-Regular.woff2 | 0.0 ms | 25.3 KiB |
| cdn.loom.com/assets/marketing/bubbs/jai-sm.jpg | 0.0 ms | 14.5 KiB |
| atl-onetrust-wrapper.atlassian.com/assets/atl-onetrust-wrapper.min.js | 86400.0 s | 32.4 KiB |
| /sessions/transcoded/09b1aa507cb846138847bf8e98b56a71.mp4... | 0.0 ms | 0 B |
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.
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.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| URL | Resource Size | Est 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 KiB | 203.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 KiB | 81.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.jpg | 13.9 KiB | 13.8 KiB |
LaunchDarkly div.rfm-child > ul.grid > li > img.thd-filter | /images/pvn35iyy/production/b74a41f0614f6c513da65947ffcd5... | 7.4 KiB | 6.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.
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.
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
| Element | Layout 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 |
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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.loom.com/assets/css/embed-video-c3c92b9d7c6acbe9.css | 27.4 KiB | 26.4 KiB |
| :root { font-size: 100%; } … | 31.2 KiB | 25.8 KiB |
| www.loom.com/_next/static/css/2436c60547503a0d.css | 24.8 KiB | 20.7 KiB |
| cdn.loom.com/assets/css/vendor-5-5f9b14b45a97d659.css | 14.3 KiB | 14.1 KiB |
| cdn.loom.com/assets/css/vendor-49-e137c3491705ae7a.css | 12.3 KiB | 12.2 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.
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.
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
| Category | Time Spent |
|---|---|
| Script Evaluation | 5.4 s |
| Other | 2.2 s |
| Style & Layout | 1.3 s |
| Script Parsing & Compilation | 1.3 s |
| Rendering | 627 ms |
| Garbage Collection | 184 ms |
| Parse HTML & CSS | 150 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
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in a sub frame. | Actionable |
| Pages with WebSocket cannot enter back/forward cache. | Pending browser support |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
| 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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
| 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.
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.
| 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.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | cdn.loom.com/assets/js/vendor-41-b27b1cc1f2cf4533.js line 329, col 45241 |
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.
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
| Link destination | Link Text |
|---|---|
| www.loom.com/security | Learn more |
| www.loom.com/enterprise | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.
668 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.01 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
456 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.051
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.79 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.
5.74 s
Audit breakdown by category with detailed findings.
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 long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| /sessions/thumbnails/09b1aa507cb846138847bf8e98b56a71-b52... | 0.0 ms | 1.3 MiB |
| /sessions/thumbnails/09b1aa507cb846138847bf8e98b56a71-b52... | 0.0 ms | 108.5 KiB |
| cdn.loom.com/assets/marketing/fonts/Charlie_Display-Bold.woff2 | 0.0 ms | 27.2 KiB |
| cdn.loom.com/assets/marketing/fonts/Charlie_Text-Bold.woff2 | 0.0 ms | 26.2 KiB |
| cdn.loom.com/assets/marketing/fonts/Charlie_Text-Semibold.woff2 | 0.0 ms | 25.7 KiB |
| cdn.loom.com/assets/marketing/fonts/Charlie_Text-Regular.woff2 | 0.0 ms | 25.3 KiB |
| cdn.loom.com/assets/marketing/bubbs/jai-sm.jpg | 0.0 ms | 14.5 KiB |
| atl-onetrust-wrapper.atlassian.com/assets/atl-onetrust-wrapper.min.js | 86400.0 s | 32.4 KiB |
| /sessions/transcoded/09b1aa507cb846138847bf8e98b56a71.mp4... | 0.0 ms | 0 B |
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.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| URL | Resource Size | Est 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 KiB | 222.0 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 KiB | 7.9 KiB |
LaunchDarkly div.rfm-child > ul.grid > li > img.thd-filter | /images/pvn35iyy/production/b74a41f0614f6c513da65947ffcd5... | 7.4 KiB | 7.0 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.
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.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
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.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| cdn.loom.com/assets/js/vendor-40-6abb717ab3231a67.js | 760 ms | 638 ms | 2.6 ms |
| cdn.loom.com/assets/js/embed-video-8f4922ebfad0a2f0.js | 566 ms | 480 ms | 73 ms |
| www.loom.com/ | 460 ms | 8.3 ms | 1.3 ms |
| Unattributable | 330 ms | 32 ms | 0.0 ms |
| cdn.loom.com/assets/js/vendor-42-d0df3fb71ad4abfd.js | 279 ms | 29 ms | 3.3 ms |
| www.loom.com/_next/static/chunks/framework-94bcf14506ace93a.js | 267 ms | 222 ms | 6.5 ms |
| cdn.loom.com/assets/js/vendor-41-b27b1cc1f2cf4533.js | 161 ms | 92 ms | 4.4 ms |
| cdn.loom.com/assets/js/vendor-36-c035baa3c8715172.js | 131 ms | 119 ms | 4.8 ms |
| /embed/09b1aa507cb846138847bf8e98b56a71?hide_owner=true&h... | 119 ms | 0.5 ms | 0.6 ms |
| www.loom.com/_next/static/chunks/pages/_app-67a2568e1fd2dd38.js | 110 ms | 64 ms | 27 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
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.8 s |
| Other | 664 ms |
| Style & Layout | 487 ms |
| Script Parsing & Compilation | 309 ms |
| Rendering | 160 ms |
| Garbage Collection | 60 ms |
| Parse HTML & CSS | 40 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
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in a sub frame. | Actionable |
| Pages with WebSocket cannot enter back/forward cache. | Pending browser support |
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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.loom.com/assets/css/embed-video-c3c92b9d7c6acbe9.css | 27.4 KiB | 26.0 KiB |
| :root { font-size: 100%; } … | 31.2 KiB | 25.8 KiB |
| www.loom.com/_next/static/css/2436c60547503a0d.css | 24.7 KiB | 18.7 KiB |
| cdn.loom.com/assets/css/vendor-5-5f9b14b45a97d659.css | 14.3 KiB | 14.1 KiB |
| cdn.loom.com/assets/css/vendor-49-e137c3491705ae7a.css | 12.3 KiB | 12.2 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
| 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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
| 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.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | cdn.loom.com/assets/js/vendor-41-b27b1cc1f2cf4533.js line 329, col 45241 |
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
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.
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
| Link destination | Link Text |
|---|---|
| www.loom.com/security | Learn more |
| www.loom.com/enterprise | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback