When a potential customer lands on your site and waits seconds for it to load, they’re not thinking about your product. They’re thinking about whether a company that can’t serve a web page efficiently can be trusted to handle anything else. The same goes for investors doing due diligence, or that senior engineer you’re trying to recruit who just watched your homepage layout shift three times on their phone. Your website is your first technical interview, and you didn’t even know you were being evaluated.
Performance is a proxy for discipline
This isn’t about aesthetics. A beautifully designed site that takes five seconds to render is arguably worse than an ugly fast one - it signals that your team optimises for surface-level polish while ignoring what’s happening underneath. Core Web Vitals - Largest Contentful Paint, Cumulative Layout Shift, Interaction to Next Paint - sound like Google SEO jargon, but they’re really a proxy for engineering discipline. A team that measures these things is a team that measures things in general. A team that doesn’t is telling you something about how they operate.
The identity gap
I’ve lost count of the number of startups who describe themselves as technology companies while running a WordPress site with forty plugins, a 2MB uncompressed hero image, and no CDN. There’s a gap between the identity and the evidence, and technically literate visitors notice it immediately. Your site doesn’t need to be a technical marvel. It needs to not contradict the story you’re telling about who you are.
The fix is infrastructure, not design
The good news is that the fixes are straightforward and they’re not frontend problems - they’re infrastructure fundamentals. Put your assets behind a CDN. Serve properly sized and compressed images. Set sensible caching headers. Consider whether you actually need a dynamic CMS or whether a static site generator would do the job faster, cheaper, and more securely. These are the same principles that underpin good infrastructure everywhere: measure, automate, eliminate waste. A team with solid CI/CD pipelines, monitoring, and performance budgets produces fast websites almost as a side effect. The site isn’t the point - the discipline behind it is.
If you’re not sure where your site stands, or you suspect the answer might be uncomfortable, get in touch. No pitch, just an honest assessment of where you are and what’s worth fixing first.