resend.com

A generous free tier anchors the funnel — read by the rubric as a softer monetization signal.

Fix: Frame the free tier as a developer trial, not a permanent free plan.

The brand is minimal black/white, but 23 colors were detected — mostly code-syntax highlighting inflating the count.

Fix: Nothing visually wrong; the count is a side effect of the code blocks.

'Start sending in minutes' is the rare number; the page is mostly qualitative DX claims.

Fix: Add a deliverability stat ('99.x% inbox placement') to make the core promise measurable.

The footer fits the clean, considered brand and likely carries some personality.

Fix: Add a memorable developer-in-joke line to make it worth screenshotting.

Has an og:image and the clean 'Email for developers' OG title earns a dev's click.

Fix: None major.

Sections each own one idea — integrate, test mode, webhooks, React email — clean and scannable.

Fix: None.

'Email for developers' is as fifth-grade-simple as a headline gets.

Funnel is signup-first; the dev can't send a real email before creating an account.

Fix: Add a no-auth rate-limited sandbox send.

'Reach humans instead of spam folders' is specific and on-brand; some feature copy is more standard.

Fix: Quote a real migration story ('we moved 4M emails off SendGrid in a weekend').

A working code sample sits in the hero and video supports it — show before explain, done.

One product, one job: an email API for developers. No scope creep.

Pricing wasn't on this view, but Resend runs a tight set of tiers within the popcorn range.

Fix: Surface the three-tier pricing higher.

Rides the React-email / modern-DX wave developers are actively discussing.

Fix: None.

'Email for developers', 'reach humans instead of spam folders' is exactly how the buyer talks.

No founder face or voice on the page despite a strongly founder-led brand.

Fix: Add a signed founder line near the trust logos.

'Pricing' sits plainly in the nav — easy to find.

'Email for developers' is clear and category-defining, if not wildly distinctive.

Fix: None needed.

The H1 is flat; the emotion lives in the subhead's 'spam folders' line.

Fix: Borrow the subhead's bite for the H1.

Email APIs predate Resend; the differentiator is DX polish, not novelty.

Fix: Spotlight the one feature (React email) that genuinely felt new.

H1 + subhead + code sample + 'Get started' tell a dev what it is, who it's for, and why.

'Spam folders' names the deliverability pain, lightly, before pitching.

Fix: Dwell one beat longer on the pain of a launch email landing in spam.

'Get started' is primary with 'Documentation' as a clear secondary — mostly one action.

Fix: Make the docs link plainly secondary in weight.

'Resend' is a simple, known word that says what it does.

Deliverability is the desire ('reach humans'), though much copy still lists capabilities.

Fix: Frame every feature as 'more emails delivered'.

The hero code sample lets you see real output without trying it live.

Fix: Make the sample runnable inline.

Just one weak word detected — claims are crisp.

Subscription pricing, as expected for an email API.

Fix: Not realistically changeable; lean on usage-based fairness instead.

'Get started' is the page's one generic CTA.

Fix: 'Send your first email'.

40 testimonial blockquotes and 'companies of all sizes trust Resend' — proof is abundant.

'Email for developers' describes the product in three words, on the page.

Positioned as the better-built option, not explicitly the premium-priced one.

Fix: Signal premium with a 'built for teams who can't afford to land in spam' line.