Funnel check

Loom's mobile homepage is making the free signup work harder

Loom's free offer is clear. On mobile, visitors then wait, meet a sign-in prompt over the pitch, and land on an Atlassian address to create an account. Each handoff adds friction before the first recording.

Owner brief

We found three leaks worth fixing. The biggest is mobile speed: the main offer took 7.6 seconds to appear in this review. The other two sit around the free signup and can make a simple decision feel less simple.

We also checked five current public ads connected with the parent brand. They led to Jira or Confluence, not Loom. Ad-to-page message match was not assessed.

The leaks to fix

1. Mobile visitors can wait 7.6 seconds for the main offer

The Loom homepage moved 12.2 MB through 515 requests on mobile. The main offer did not finish appearing for 7.6 seconds, and the page was too busy to respond for another 1.2 seconds during the load. Desktop was much quicker, so the sharpest problem is the phone experience.

That delay burns the attention you paid or worked to earn. A visitor who only wants to understand Loom and start free should not have to wait on the page's videos, scripts, and integrations first.

Start by holding back the large hero media and nonessential code until the offer and free signup are ready. Keep watching the time to the main offer, page weight, and request count after every homepage release.

Desktop view of the Loom homepage, with the offer and free signup in place.

2. A sign-in panel interrupts the mobile pitch

The first mobile screen shows Loom's free signup button. Directly beneath it, a "Sign in to Atlassian with Google" panel rises over the page and covers what comes next. It appears before the visitor has chosen to sign in.

This creates two competing asks at once: start free with Loom, or continue with Google and Atlassian. On a small screen, that extra choice takes over a large share of the view.

Delay the sign-in panel until the visitor shows account intent, or keep it inside the signup step. Then watch the first screen at common phone widths so it never covers the pitch or the next piece of proof.

Mobile view showing the Google sign-in panel over the lower part of Loom's first screen.

3. "Get Loom for free" changes the domain and the terms

The free Loom button redirects from Loom to an Atlassian identity address. The next page still carries the Loom name, but it asks for an Atlassian account and acceptance of Atlassian's cloud terms.

The signup works, but the change is abrupt. A visitor expecting a Loom account can pause when the address, account owner, and terms all change at once.

Set the expectation before the click. A short line such as "Create your free Loom account with Atlassian" would make the handoff feel intentional. Keep checking the redirect, co-branding, free-offer wording, and account path whenever identity pages change.

The co-branded signup page reached from Loom's free CTA.

Fix these in this order

First Problem Why it deserves attention What to do now
1 Slow mobile offer It spends visitor patience before the pitch lands Load the offer and signup before heavy media and nonessential code
2 Sign-in panel over the page It competes with Loom's main action on a small screen Show it after the visitor chooses to create or access an account
3 Abrupt Atlassian handoff It can make a free Loom signup feel unfamiliar Explain the Atlassian account step before the click

What we checked

We reviewed the Loom homepage on desktop and mobile, checked 15 on-site links, opened the first account-creation page, and stopped before entering an email or submitting the form. No purchase, form submission, logged-in workspace, activation email, or paid plan flow was tested.

No broken links appeared in the checked set. The homepage kept campaign details in its address during the visit. Current ads found in this review did not point to Loom, and no current competitor comparison was strong enough to include.