Website review, no card needed

lemlist logo

lemlist.com website review

Visit site (opens in a new tab)Reviewed 14 November 202628 issues · 78 checks

This review found 28 issues worth fixing on lemlist.com, 7 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for lemlist

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.5 s1.4 sMay 23Nov 71.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.0 s
May 30, 20263.1 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.3 s
Jun 27, 20263.3 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20263.0 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20262.9 s
Oct 3, 20262.7 s
Oct 10, 20262.3 s
Oct 17, 20262.0 s
Oct 24, 20261.8 s
Oct 31, 20261.7 s
Nov 7, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
362 ms215 msMay 23Nov 7255 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026232 ms
May 30, 2026250 ms
Jun 6, 2026248 ms
Jun 13, 2026253 ms
Jun 20, 2026266 ms
Jun 27, 2026277 ms
Jul 4, 2026303 ms
Jul 11, 2026318 ms
Jul 18, 2026316 ms
Jul 25, 2026327 ms
Aug 1, 2026319 ms
Aug 8, 2026335 ms
Aug 15, 2026345 ms
Aug 22, 2026343 ms
Aug 29, 2026337 ms
Sep 5, 2026315 ms
Sep 12, 2026301 ms
Sep 19, 2026319 ms
Sep 26, 2026327 ms
Oct 3, 2026344 ms
Oct 10, 2026342 ms
Oct 17, 2026328 ms
Oct 24, 2026305 ms
Oct 31, 2026278 ms
Nov 7, 2026255 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of lemlist.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lemlist.com at 0.4 s0.4 s
  2. lemlist.com at 0.8 s0.8 s
  3. lemlist.com at 1.1 s1.1 s
  4. lemlist.com at 1.5 s1.5 s
  5. lemlist.com at 1.9 s1.9 s
  6. lemlist.com at 2.3 s2.3 s
  7. lemlist.com at 2.6 s2.6 s
  8. lemlist.com at 3.0 s3.0 s

Speed

7 to fix62
  • Reduce unused JavaScript

    2.5 s · 458 KiB

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

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    450 ms · 293 KiB

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

  • Improve image delivery

    400 ms · 234 KiB

    5 images could be 234 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.

  • 7 third-party services on the page

    7 third-party services load with your homepage (posthog.com, Google Tag Manager and rudderlabs.com and others), adding 522 KiB and 570 ms of main-thread time.

  • Render-blocking requests

    550 ms

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

  • posthog.com adds 381 ms

    381 ms

    posthog.com costs a phone 381 ms of main-thread work and 268 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.

  • Legacy JavaScript

    200 ms · 34 KiB

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

  • Duplicated JavaScript

    150 ms · 19 KiB

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

  • 8 long tasks on the main thread

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

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 1.2 s of it running JavaScript. That is comfortably low.

  • Server response: 18 ms

    18 ms

    Your server sent the HTML in 18 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 10.7 s

    10.7 s

    Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 10.7 s

    10.7 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • Real-user INP: 225 ms

    225 ms

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Total Blocking Time: 250 ms

    250 ms

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

  • 3 images without width and height

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

  • Tap response (INP) got 11% slower for real visitors

    +11%

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

6 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 698 ms

    698 ms

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

  • Largest content (LCP) got 46% faster for real visitors

    -46%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix75
  • Page weight: 2.5 MB in 109 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 109 requests on a phone: scripts 1,016 KiB (45), media 727 KiB (1) and images 549 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    40 KiB

    1 image is downloaded at several times the size a phone draws it, for example 63e96d25198196d9069022f57e7cbdfb at 1,704 px wide, shown at 326 px. Resized copies would save about 40 KiB.

  • About 0.7 g of CO₂ per visit

    0.70 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

6 to fixGoogle 9691
  • 3 text elements with low contrast

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

  • Interactive controls must not be nested (3 elements)

    Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Alternative text of images should not be repeated as text (8 elements)

    Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 62 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 121 internal links, 31 external

    The homepage links to 121 pages on lemlist.com and 31 external pages.

8 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Know who to target and why now, find verified contacts, and engage across every channel from lemlist, your CRM, or your…”.

  • One H1 headline

    Your main headline reads: “The only platform you need to make Outbound work.”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “The only platform you need for outbound | lemlist”.

  • Canonical URL set

    The canonical URL is https://www.lemlist.com/.

  • Structured data in place

    Structured data found: FAQPage, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.lemlist.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.lemlist.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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,658 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    8 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

  • No form on the homepage

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

  • No risk reducer

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

  • About 927 words of copy

    The homepage carries about 927 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start free trial” and “Get a demo”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Pricing”, “Get a demo” and “Start free trial”.

  • Social proof on the page

    Social proof on the homepage: a star rating and 4 trust badges.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 9 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at lemlist.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Vercel

Hiring

Hiring
18 open roles
Teams
Business (5), Tech (5), Marketing (4), Finance (2)
Job board
ashby

Company

Founded
2018
Headquarters
Paris

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on lemlist.com, including 15 speed issues, 1 SEO issue and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25