5 posts
#performance
Performance posts here cover the web, the database and mobile apps. How to measure Core Web Vitals without a fancy dashboard, what a performance budget is and why bundles grow without one, which Postgres settings matter for a small SaaS, and how app size affects installs. One post looks at WordPress reliability through sites that have kept running for a decade.
Front-end developers should start with Core Web Vitals and the budget post. If the bottleneck is the database, go straight to Postgres tuning and skip the rest for now.
Related service: Website audit
(01)
Postgres tuning for small SaaS — settings that matter
Default Postgres configuration is conservative — designed to run on any machine without falling over. For a small SaaS on dedicated hardware, defaults leave 50-200% performance on the table. A small set of well-chosen settings makes a big difference.
→
(02)
WordPress reliability — what real-world data shows
There's no clean public dataset on how long sites survive by CMS. But the factors that keep a WordPress site running for years, and the ones that break it, are well known.
→
(03)
Performance budget — what it is and why care
A performance budget sets hard limits on page weight and speed metrics. Without one, pages tend to get heavier with every release, and nobody notices until it hurts.
→
(04)
How to measure Core Web Vitals in 2026
LCP, INP and CLS: the three metrics Google uses to judge page experience. How to measure them on your own site with free tools, and what to fix first.
→
(05)
App size and bundle in 2026
Bigger app = fewer installs. Especially in regions with slow internet or expensive data. What to cut.
→