Benchmark section on homepage from Astro

Developer Markepear testimonials

Your dev tool is faster/more scalable/more X -> show it with benchmarks.

For some tools the entire unique selling point is that they are faster.

You build your messaging around that, put a flavor of "fastest Y for X" in the header and call it a day.

But devs who come to your website cannot just take your word for it. They need to see it, test it.

For some tools it is possible to just see it for themselves, get started.

But you cannot expect devs to really take a database or an observability platform for a spin.

As to test the speed or scalability on realistic use case you need to...

... set up a realistic use case. Which takes a lot of time.

But you can set that use case and test it for them. With benchmarks.

I really like how Astro approached it:

  • they list out known competition by name
  • they hint at technical reasons for why they are faster
  • they shows those benchmarks high on their homepage
  • they link out to the full report and mention the trusted source

If your usp is that you are faster/more scalable/ more whatever. Back it up. This is the nr 1 thing devs on your website need to trust you with to move forward.

  • See website
Browse 100+ examples like this ->
call to action
landing page

Open-source project homepage CTA from Astro

developer experience
docs
hero section

Docs header diagram from Hopsworks

developer experience

Updates modal from Discord

developer experience
github
hero section

GitHub Repository Readme.md design from Prisma

blog
call to action
seo

JTBD blog post from WorkOS

copy
landing page
hero section

Header copy from Supabase

call to action
landing page
developer experience
hero section

Header with benchmarks from Bun

developer experience
landing page
hero section

Algolia developer portal design

developer experience
video
youtube

Hand-drawn tutorial video style from Robusta

developer experience
call to action
blog

Developer-focused blog slide-in CTA from Snyk