mailgun.com website review

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

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

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

Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

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

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

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

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

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

Your largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “Image for Transactional Email Delivery Service & API for De…”.

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

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

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

Scripts block the page for only 0 ms while loading. Good is under 200 ms.

The page is fully interactive after 1.8 s.

Your homepage downloads 146 KiB in 16 requests on a phone: HTML 53 KiB (1), stylesheets 33 KiB (10) and images 29 KiB (2). That is a lean page.

Every sizeable image is WebP, AVIF or SVG.

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

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

All 40 images in the HTML carry an alt attribute.

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

Your meta description is 134 characters: “Powerful Transactional Email APIs that enable you to send, receive, and track emails, built with developers in mind. Le…”.

Your main headline reads: “Transactional Email Delivery Service & API for Developers”.

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

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

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

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

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

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

12 pages of 15 loaded without an error (the rest turned automated requests away).

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

Every page we checked has its own title.

Each page we checked has a main headline.

None of the pages we checked carries a noindex tag.

All 12 pages that loaded have a <title>.

No JavaScript errors were logged while the page loaded on a phone.

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

The page declares a mobile viewport.

The homepage is served over HTTPS (mailgun.com).

The certificate from Let's Encrypt · YE2 verifies for mailgun.com and is valid for another 55 days.

X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

A Content-Security-Policy is set, the main browser-side defence against injected scripts.

Strict-Transport-Security is set, so browsers always use https.

http://mailgun.com redirects to the secure version.

The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

All 56 links checked from your homepage (40 internal, 16 external) answered without errors.

mailgun.com was registered in Dec 2003 through NameCheap, Inc.. An established domain carries more trust with email providers and search engines.

mailgun.com is registered until Dec 2033.

On a phone, the first screen shows a clear next step: “Schedule a demo” and “Get started for free”.

The homepage has 18 calls to action, for example “Contact Support”, “Pricing” and “Start for free”.

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

Social proof on the homepage: 6 testimonial or review blocks and “over 150,000 businesses”.

Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and LinkedIn Insight.

DMARC tells receivers to reject mail that fails authentication, and sends you reports.

An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.mailgun.org include:_spf.eu.mailgun.org include:spf.protection.outlook.com include:aspmx.pardot.com…”.

A DKIM key is published (selector “google”, “selector1” and “k1”), so receivers can verify mail really came from you.

No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).