QuietBench: A Free Developer Utility Suite I Built Solo (No Ads, No Sign-Up, No BS)

What I Built

QuietBench (quietbench.dev) is a free suite of everyday developer utilities — the kind of tools you Google at 2am when you're stuck on something small but annoying:

JSON Formatter — format, validate, and minify JSON instantly

Regex Tester — test patterns with live match highlighting

Cron Builder — build and understand cron expressions without memorizing syntax

WCAG Contrast Checker — check color contrast ratios for accessibility compliance

API Request Tester — send requests and inspect responses without opening Postman

No accounts. No paywalls. No cookie-consent maze. Just open the tab, do the thing, close the tab.

Why I Built It

I kept bouncing between five different single-purpose tool sites every time I needed to format JSON or test a regex — each with its own ad-heavy layout, weird UX, and a sign-up wall for "advanced" features I didn't need. I wanted one clean, fast place for the tools I reach for constantly. So I built it.

Tech Stack

React + Vite + TypeScript for the frontend

Tailwind CSS for styling

Cloudflare Pages for hosting

Porkbun for the domain

The whole thing is a static SPA, deployed with a single command:

npm run deploy

which runs the Vite build, prerenders every route, and pushes to Cloudflare via Wrangler.

Challenges I Ran Into

1. A CSP regression that tanked my LCP score
   
   I tightened my Content Security Policy for safety and accidentally forgot to allowlist Google Fonts. Page load time (LCP) spiked overnight. Lesson: every CSP change needs a Lighthouse re-check, not just a "looks fine" glance.




2. SPAs and crawlers don't get along
   
   Since QuietBench is a client-rendered SPA, non-JS crawlers (and some bots) were seeing an empty shell instead of actual content. I fixed this with build-time prerendering using Playwright — every one of the 11 routes now gets a fully-rendered HTML snapshot generated at build time, so crawlers see real content without needing to execute JS.




3. Getting indexed without SEO gimmicks
   
   Rather than chasing broad, competitive keywords, I focused on long-tail, exact-match queries — specific error messages, exact syntax terms, the kind of thing someone pastes directly into Google when they're stuck. I also set up IndexNow for instant Bing submission on every deploy, so new content doesn't sit around waiting to be crawled.




4. The little things that break silently
   
   A www/non-www redirect inconsistency was quietly splitting my traffic and confusing search engines — fixed with a Cloudflare Redirect Rule. Small, boring, but it matters for SEO hygiene.

What's Next

Two more long-tail content pages, currently paused while I read Search Console data to make sure I'm building the right pages, not just more pages

Continued distribution — dev.to has been the most genuinely engaged channel so far

More utilities based on what I personally keep needing

Try It

👉 quietbench.dev

It's free, it's fast, and it doesn't ask you for your email. Would genuinely love feedback from other devs — especially if a tool is missing something you'd expect, or if you spot a bug.

Building this solo, learning SEO and infra as I go. If you're into indie dev tools or want to swap notes on prerendering/IndexNow setups, drop a comment — happy to share specifics.