loom.com website review

About 25.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 18.1 s faster on a phone.

14 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

About 202 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

Your mobile performance score is 26 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 5.7 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

16 long tasks block the main thread while loading, the longest for 575 ms. During a long task the page ignores taps.

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

6 third-party services load with your homepage (atlassian.com, Optanon and Other Google APIs/SDKs and others), adding 837 KiB and 286 ms of main-thread time.

4 images could be 220 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Desktop scores 58 but mobile only 26. A gap that wide usually means heavy scripts and images that hit phones hardest.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

The first text or image appears after 23.7 s on a phone. Good is under 1.8 s.

Your largest element takes 29.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This site uses cookies to improve your browsing experience …”.

Visually, the page fills in at 37.6 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 148.0 s. Good is under 3.8 s.

Scripts block taps and scrolling for 2.1 s in total while the page loads. Good is under 200 ms.

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 405 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.25 (75th percentile). Good is under 0.1.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 304 ms to 303 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 5.5 s to 6.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 29.5 MB in 152 requests on a phone: scripts 27.0 MB (57), media 1.6 MB (3) and images 325 KiB (32). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 34b82b411513ae1538a4d09332a95e6dfd11f1fb-1200x1200.jpg at 1,200 px wide, shown at 326 px. Resized copies would save about 37 KiB.

1 image (110 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 8.35 g of CO₂e: 1002.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

Some lists contain elements other than list items, which screen readers announce wrongly.

6 visible links have no text or label, so screen readers cannot say where they go.

2 tap targets are too small or too close together to hit reliably with a finger.

Structured data found (Corporation) but with 1 problem, for example “Corporation: missing name”.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

The homepage links to 20 pages on loom.com and 3 external pages.

robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

/download, /desktop and /looms/videos use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /products/ios-screen-recorder, whose canonical is /products/iphone-screen-recorder. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/download, /desktop and /looms/videos have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

3 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 12 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,032 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 14 cookies (measured from a US location before any click).

Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.