Website review, no card needed
litmus.com website review
Visit site (opens in a new tab)Reviewed 29 October 202634 issues · 85 checks
This review found 34 issues worth fixing on litmus.com, 14 of them high impact, across 85 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 299 ms |
| May 16, 2026 | 271 ms |
| May 23, 2026 | 306 ms |
| May 30, 2026 | 295 ms |
| Jun 6, 2026 | 295 ms |
| Jun 13, 2026 | 306 ms |
| Jun 20, 2026 | 305 ms |
| Jun 27, 2026 | 352 ms |
| Jul 4, 2026 | 343 ms |
| Jul 11, 2026 | 312 ms |
| Jul 18, 2026 | 279 ms |
| Jul 25, 2026 | 277 ms |
| Aug 1, 2026 | 287 ms |
| Aug 8, 2026 | 287 ms |
| Aug 15, 2026 | 320 ms |
| Aug 22, 2026 | 294 ms |
| Aug 29, 2026 | 351 ms |
| Sep 5, 2026 | 348 ms |
| Sep 12, 2026 | 369 ms |
| Sep 19, 2026 | 369 ms |
| Sep 26, 2026 | 320 ms |
| Oct 3, 2026 | 326 ms |
| Oct 10, 2026 | 324 ms |
| Oct 17, 2026 | 340 ms |
| Oct 24, 2026 | 307 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
Speed
Render-blocking requests
1.9 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Reduce unused CSS
1.5 s · 154 KiBAbout 154 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Google Tag Manager adds 1.5 s
1.5 sGoogle Tag Manager costs a phone 1.5 s of main-thread work and 886 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.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Optanon and others), adding 1.6 MB and 2.1 s of main-thread time.
Reduce unused JavaScript
750 ms · 806 KiBAbout 806 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 841 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
503 KiB23 files are served with short cache lifetimes, so returning visitors download them again (503 KiB).
Improve image delivery
234 KiB2 images could be 234 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
29 KiB29 KiB could be saved by minifying JavaScript.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
13 KiB13 KiB JavaScript is shipped twice across bundles.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 22.7 s
22.7 sThe page becomes fully interactive after 22.7 s. Good is under 3.8 s.
Largest Contentful Paint: 7.8 s
7.8 sYour largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LITMUS IS NOW PART OF VALIDITY ENGAGE Your entire email wor…”.
Total Blocking Time: 1.9 s
1.9 sScripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 466 ms
466 msReal visitors wait 466 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.118
0.118The layout shifts by 0.118 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 3.6 s
3.6 sVisually, the page fills in at 3.6 s (Speed Index). Good is under 3.4 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 299 ms to 307 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 3.1 MB in 144 requests
3.1 MBYour homepage downloads 3.1 MB in 144 requests on a phone: scripts 1.9 MB (55), images 451 KiB (24) and other files 277 KiB (48). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
16 KiB1 image is downloaded at several times the size a phone draws it, for example engage-hero-home-08102026.png.webp at 1,200 px wide, shown at 366 px. Resized copies would save about 16 KiB.
1 image in older formats
1 image (160 KiB) is 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 below the first screen load straight away
1 image further down the page (160 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 104.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
37 text elements with low contrast
37 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (37 elements)
All page content should be contained by landmarks: 37 elements on the page fail 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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
87 internal links, 19 external
The homepage links to 87 pages on litmus.com and 19 external pages.
8 checks passed
Meta description: 129 characters
Your meta description is 129 characters: “Litmus is the all-in-one email marketing platform that provides the tools and solutions your team needs to make every s…”.
One H1 headline
Your main headline reads: “Litmus is now part of Validity EngageYour entire email workflow in one AI-native platform”.
Title: 60 characters
Your title is a healthy 60 characters: “All-in-One Email Marketing Platform | Tools to Drive Success”.
Canonical URL set
The canonical URL is https://www.litmus.com/.
Structured data in place
Structured data found: Corporation.
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.litmus.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.litmus.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,316 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 60 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 broken image
1 image failed to load on a phone, for example https://www.litmus.com/.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://p.typekit.net/p.css?s=1&k=evl7uqd&ht=tk&f=139.140.169.175.176.5503.5504.5505.5506.39347.39348.39…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
7 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 882 words of copy
The homepage carries about 882 words of visible text.
5 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Learn more”, “Get started” and “Contact data quality”.
2 short forms
2 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: a star rating, 2 trust badges and “100+ clients”.
Analytics in place
Analytics detected: Hotjar, Segment and Heap.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 litmus.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Fastly
Hiring
- Hiring
- 33 open roles
- Teams
- Customer Success (10), Engineering (9), Sales (5), Product (3)
- Job board
- ashby
- Careers page
- jobs.ashbyhq.com/litmus (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on litmus.com, including 21 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.