leadpages.com website review

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

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

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

Your mobile performance score is 45 (desktop: 75). 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.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, iubenda and Facebook and others), adding 1,013 KiB and 847 ms of main-thread time.

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

Google Tag Manager costs a phone 312 ms of main-thread work and 515 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.

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

The page has 2,867 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

13 KiB could be saved by minifying CSS.

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

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.

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

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

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

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

Your largest element takes 27.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The AI landing page builder CRO platform.”.

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

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

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

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

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

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

The layout shifts by 0.1 while loading, so content jumps under the reader's thumb. Good is under 0.1.

1 image have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 14.6 MB in 187 requests on a phone: media 8.5 MB (4), images 3.4 MB (57) and scripts 1.8 MB (63). Under 2 MB keeps phones on slow connections fast.

leadpages-icon.png weighs 578 KiB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example leadpages-icon.png at 947 px wide, shown at 13 px. Resized copies would save about 577 KiB.

25 images (1.8 MB) are 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.

1 image further down the page (578 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

10 buttons have no accessible name, so screen readers announce just “button”.

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

Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

The homepage links to 91 pages on leadpages.com and 21 external pages.

Your robots.txt lets Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

/product/ad-studio has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 65 found) 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=5129109&tm=gtm002&Ver=2&mid=ac5005a4-ca77-4997-b1bc-286d85e983db&bo=1&sid=4a782800ce4d11f187629d319c45a7e8&vid=4a783ab0ce4d11f19fb9ed673b03775c&vids=1&msclkid=N&pi=918.

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

Chrome logged issues while loading the page (“Content security policy”).

1 link from your homepage to your own site is broken, for example https://leadpages.com/cdn-cgi/l/email-protection (404).

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

leadpages.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

leadpages.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

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

The homepage carries about 2,025 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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