Website review, no card needed

mailshake.com logo

mailshake.com website review

Visit site (opens in a new tab)Reviewed 14 November 202621 issues · 77 checks

This review found 21 issues worth fixing on mailshake.com, 4 of them high impact, across 77 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  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
2.4 s2.0 sMay 23Nov 72.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.2 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Oct 24, 20262.3 s
Oct 31, 20262.2 s
Nov 7, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
160 ms108 msMay 23Nov 7140 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026129 ms
May 30, 2026134 ms
Jun 6, 2026131 ms
Jun 13, 2026127 ms
Jun 20, 2026114 ms
Jun 27, 2026119 ms
Jul 4, 2026114 ms
Jul 11, 2026118 ms
Jul 18, 2026121 ms
Jul 25, 2026121 ms
Aug 1, 2026135 ms
Aug 8, 2026133 ms
Aug 15, 2026131 ms
Aug 22, 2026131 ms
Aug 29, 2026122 ms
Sep 5, 2026125 ms
Sep 12, 2026136 ms
Sep 19, 2026140 ms
Sep 26, 2026151 ms
Oct 3, 2026148 ms
Oct 10, 2026150 ms
Oct 17, 2026148 ms
Oct 24, 2026142 ms
Oct 31, 2026154 ms
Nov 7, 2026140 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 mailshake.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix95
  • Render-blocking requests

    800 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Crazy Egg and Amplitude Mobile Analytics and others), adding 654 KiB and 560 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 335 KiB

    About 335 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Google Tag Manager adds 369 ms

    369 ms

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

  • 7 long tasks on the main thread

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

  • Reduce unused CSS

    56 KiB

    About 56 KiB of CSS is downloaded but never applied on this page.

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    37 KiB

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

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

  • Improve image delivery

    10 KiB

    1 image could be 10 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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.

3 checks passed
  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.1 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix100
  • 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: 9.4 s

    9.4 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Total Blocking Time: 251 ms

    251 ms

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

  • 1 image without width and height

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

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

    +12%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

7 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 146 ms

    146 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.004

    0.004

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Email Automation That Lands in Inboxes, Gets Replies, and B…”.

  • Speed Index: 1.9 s

    1.9 s

    Visually, the page fills in at 1.9 s (Speed Index), inside the 3.4 s “good” threshold.

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.36 g

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

4 checks passed
  • Page weight: 1.3 MB in 54 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 54 requests on a phone: scripts 703 KiB (17), fonts 297 KiB (4) and images 220 KiB (18). That is a lean page.

  • 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.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8791
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 29 images without alt text

    29 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (7 elements)

    All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 32 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 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

1 to fixGoogle 8598
  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 62 internal links, 9 external

    The homepage links to 62 pages on mailshake.com and 9 external pages.

8 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Build sales outreach cadences with email, phone, and social in as little as 5 minutes with Mailshake's sales engagement…”.

  • One H1 headline

    Your main headline reads: “Email Automation That Lands in Inboxes, Gets Replies, and Books Meetings.”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “AI Powered Sales Engagement & B2B Lead Platform - Mailshake”.

  • Canonical URL set

    The canonical URL is https://mailshake.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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://mailshake.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

2 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.

Other pages

1 to fix95
  • 1 page without a meta description

    https://mailshake.com/data-finder has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://mailshake.com/sales-demo has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

6 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.

  • 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 9692
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'add')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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.

  • Only about 34 words

    The homepage has only about 34 words of visible text; thin pages give Google and first-time buyers little to go on.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get Started”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Pricing”, “Get Started” and “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 7 testimonial or review blocks, 3 trust badges and “100,000+ companies”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and HubSpot.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Amplitude, Google Tag Manager and LinkedIn Insight (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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies, 1 of them by other companies (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.

  • 13 other companies contacted

    Loading the homepage contacts 13 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 mailshake.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
CloudFront

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on mailshake.com, including 10 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