Menu

Why I picked Astro over Next.js for a calculator site (and shipped 12 of them)
πŸ“°
0

Why I picked Astro over Next.js for a calculator site (and shipped 12 of them)

DEV CommunityΒ·Shahzeb KhanΒ·about 1 month ago
#6wYfEFWU
#seo#webdev#next#astro#calculator#inputs
Reading 0:00
15s threshold

I just shipped blueprintcalc.com β€” 12 home improvement calculators (paint, concrete, drywall, deck, mulch, tile, etc.) that compute material quantities AND output a full shopping list with prices and retailer links. I'd defaulted to Next.js for static-ish sites for years. This time I went with Astro and don't regret it. Here's the framework comparison and what actually mattered. The constraints Before picking a framework, I wrote down what the site had to do: ~95% of traffic will come from Google long-tail search. ("how much paint for 12x14 room", "concrete bag calculator 4 inch slab" β€” that kind of query.) SEO is everything. Lighthouse 95+ on mobile or I lose ranking. Google's Core Web Vitals are not optional for a content site competing with established players (Calculator.net, OmniCalculator). Calculator UI must be interactive β€” change inputs, see results update β€” without round-tripping to a server. No backend. No database. No auth. Every calculation is pure math on numeric inputs.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More