Our Leadpages results
Leadpages makes pages for ads, so we tested real ad pages built on it. Its template gallery shows raw page code, not published pages. So we used 8 of Leadpages' own ad landing pages: 5 from its current builder and 3 from its classic builder. We checked each page's code for Leadpages signatures, then ran it through Google PageSpeed Insights on mobile.
Here is what we found (ClickMend scans, October 2026, 8 pages):
| Measure | Median | Range |
|---|---|---|
| Performance score (0 to 100) | 52 | 28 to 76 |
| Largest Contentful Paint (LCP) | 13.3 seconds | 2.9 to 20.2 seconds |
| Total Blocking Time (TBT) | 678 ms | 314 to 2,263 ms |
| Cumulative Layout Shift (CLS) | 0.005 | 0 to 0.019 |
| Page weight | 3,062 KB | 1,775 to 5,788 KB |
| Script | 1,822 KB | 1,573 to 4,800 KB |
| Tag and pixel script | 1,527 KB | 1,137 to 3,618 KB |
Google's Lighthouse scoring calls 50 to 89 needs improvement and 0 to 49 poor. Five pages landed in the middle band and 3 were below 50. The best page scored 76 with an LCP of 2.9 seconds.
Layout shift was very low on all 8 pages, a good result. The problem was script.
The spread was wide. The fastest page, at 76, had the same builder as the slowest, at 28. The slowest page carried the most script of any page in the group, 4,800 KB, and the most blocking time, 2,263 ms. The fastest had about a third of that script. Same tool, different choices about what to load.
Why care for Google Ads? Google's own Quality Score help page says the speed your page loads can be the difference between someone bouncing or buying. ClickMend does not read your Quality Score, but it checks the speed and tracking parts of the page. Our guide to the landing page part of Quality Score explains more.
What slowed the pages
- Tags and pixels. This was the big one. Of a median 1,822 KB of script per page, a median 1,527 KB came from Google Tag Manager, social media pixels, a CRM script, and similar tools. The Leadpages code itself was a small part.
- Blocking time. Every page was over Google's suggested 200 ms. The median was 678 ms and the worst was 2,263 ms. That is time the phone is too busy to respond to a tap.
- Main-thread work. Flagged on 7 of 8 pages, from 2.1 to 8.6 seconds of browser work.
- Unused JavaScript. Flagged on all 8, a median 704 KB per page. Most came from the tag manager and social scripts.
- Files that block the first paint. Flagged on 7 of 8, with estimated savings of 0.45 to 1.37 seconds.
- Consent tool. All 8 pages loaded a cookie consent script, which adds its own weight.
Fixes for Leadpages pages
The good news: the biggest problem in this data is something you control. Tags are added by the advertiser, not forced by the builder.
- Open your tag manager and list every tag. Keep the Google Ads tag and the tools you check every week. Remove the rest.
- Don't load pixels for networks you don't advertise on. A Google Ads landing page may not need every social pixel.
- Move chat widgets and CRM scripts off the ad page, or load them after the page is ready.
- Compress the hero image and keep the first screen short: headline, form, phone number.
- After you remove tags, confirm the Google Ads conversion still fires. Our conversion tracking guide shows the 5-minute check.
Then run the live page through a free ClickMend scan. It names the slow scripts on the page and checks the Google Ads tag in the same report.
Limits of this test
- We tested 8 pages. A small sample.
- These were Leadpages' own ad pages, with Leadpages' own tags. Your page will carry your tags instead.
- Lab data from one run per page on a simulated mid-tier phone. Scores move a little each run.
- One page had real-user data from Google. Real visitors saw the main content in 4.4 seconds (75th percentile), while the lab showed 11.5 seconds. Lab numbers are for comparing and finding slow parts.
Compare Leadpages with Unbounce and ClickFunnels, or see all 8 builders in the landing page builder speed test.
Frequently asked questions
Is Leadpages good for Google Ads?
It is built for ad landing pages. In our small test, the median mobile score was 52 out of 100, and most of the script weight came from tracking tags, not from Leadpages itself. Keep your tags lean and test the page before you spend.
Why is my Leadpages page slow on mobile?
In our test, blocking time was a median 678 ms, and Lighthouse flagged heavy main-thread work on 7 of 8 pages. Most of that script came from tag manager, social pixels, a CRM script, and a consent tool.
Did the classic and new Leadpages builders score differently?
We tested 3 classic pages and 5 pages from the current builder. Classic pages scored 28, 51, and 63. Current pages scored 41 to 76. That is too few pages to say one is faster.
How do I test my Leadpages page?
Paste the final URL from your Google Ad into the free ClickMend scan. You get 2 scans a week, no card, a 0 to 100 score, and a conversion tracking check.