moosend.com website review

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

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

About 419 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

8 images could be 345 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

A phone's processor spends 7.8 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Clarity and others), adding 1.9 MB and 1.2 s of main-thread time.

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

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

Google CDN costs a phone 302 ms of main-thread work and 736 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.

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

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

Sumo costs a phone 117 ms of main-thread work and 471 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.

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

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

16 KiB JavaScript is shipped twice across bundles.

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 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your largest element takes 28.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Email marketing and marketing automation platform Send, Con…”.

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

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

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

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

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

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

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

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

Your homepage downloads 5.9 MB in 240 requests on a phone: scripts 2.0 MB (59), other files 1.9 MB (59) and images 905 KiB (80). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example constantcontact-hero.webp at 1,570 px wide, shown at 256 px. Resized copies would save about 212 KiB.

1 image further down the page (149 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 1.66 g of CO₂e: 199.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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.

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

1 link inside paragraphs relies on colour alone to stand out.

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

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

There are 5 <h1> headlines (“Send, Convert, Repeat: Delight your audience in e…”, “Go beyond the inbox with Constant Contact” and “Ready to get started?”). One clear main headline is easier for people and search engines.

The homepage links to 171 pages on moosend.com and 38 external pages.

Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

/privacy-policy, /terms and /affiliate-program-terms are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/privacy-policy, /terms and /affiliate-program-terms have no meta description, so Google writes the search snippet from whatever text it finds.

/acceptable-use-policy, /privacy-policy and /terms have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 link to other sites is dead, for example https://ctct.social/?utm_source=site&utm_medium=mn&utm_campaign=social (502).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

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

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

The homepage carries about 1,198 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, Meta Pixel and Microsoft Clarity (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 18 cookies (measured from a US location before any click).

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