unlock.com website review

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

33 files are served with short cache lifetimes, so returning visitors download them again (691 KiB).

About 689 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

Segment costs a phone 1.5 s of main-thread work and 197 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

anura.io costs a phone 1.1 s of main-thread work and 79 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Segment, anura.io and Google Tag Manager and others), adding 1.5 MB and 3.2 s of main-thread time.

About 178 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 740 ms faster on a phone.

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

2 images could be 81 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

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

54 KiB could be saved by minifying JavaScript.

Google Tag Manager costs a phone 299 ms of main-thread work and 533 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

14 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 12.9 s on a phone. Good is under 1.8 s.

Your largest element takes 26.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “An Unlock Home Equity Agreement (HEA) gives you up to $500K…”.

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

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

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

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

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

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

Real visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 4.3 MB in 189 requests on a phone: scripts 2.2 MB (82), fonts 1.6 MB (10) and stylesheets 199 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h5, h3 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

<td> elements in a large <table> do not have table headers. (1 element).

There are 2 <h1> headlines (“Unlock your home equity with no monthly payments.” and “How do HEAs Work?”). One clear main headline is easier for people and search engines.

The homepage links to 25 pages on unlock.com and 18 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.unlock.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.unlock.com/product-guide has no <title>, so Google invents the link text in results.

https://www.unlock.com/customer-stories and https://www.unlock.com/homeowner-stories all use the title “Unlock Reviews | Real Home Equity Success Stories | Unlock”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.unlock.com/disaster-resources and https://www.unlock.com/product-guide have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.unlock.com/customer-stories and https://www.unlock.com/homeowner-stories use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.unlock.com/customer-stories, whose canonical is https://www.unlock.com/homeowner-stories. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.unlock.com/product-guide has 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.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17557667&tm=gtm002&Ver=2&mid=36a6c1f9-92cd-433b-96b9-b2d7d38c671b&bo=1&sid=d7e039d0cc5611f1b80d5373723a05cf&vid=d7e05c10cc5611f1b3d881d3e2306122&vids=1&msclkid=N&pi=91.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“`StorageType.persistent` is deprecated. Please use standardized `navigator.storage` instead.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 2,150 words of visible text.

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

Opening the homepage sets 33 cookies, 1 of them by other companies (measured from a US location before any click).

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