[PERF] latency detected

Find the slow part. Fix the system.

Most delays have a technical cause that can be removed.

What a Bottleneck Looks Like

A page that takes ten seconds to load. A report that is started before lunch and read after it. A screen that freezes whenever two people use it at once. An import that has to run overnight because it blocks everything else.

People get used to these and plan around them. But they usually have a specific technical cause, and fixing it is often much cheaper than replacing the system.

Where Bottlenecks Come From

  • Slow database queries — asking the database the same question the long way round
  • Blocking file processing — everyone waits while one file is handled
  • Overloaded reports — working out a year’s figures every time someone asks
  • Serial processes — steps done one after another that could happen at once

How We Identify Bottlenecks

  • Profiling
  • Logging
  • Watching real-world use
  • Measurements, not assumptions

Typical Fixes

  • Query optimisation — the same answer, asked properly
  • Caching — work done once and reused
  • Background queues — long jobs moved out of people’s way
  • Indexing and restructuring — data arranged for how it is actually used

Before and after measurements matter. We show what changed and why.

Who It Suits and What It Costs

Businesses with a website or system that has slowed down as it has grown, especially ones built on SQL Server, which we know well. We usually start with a short investigation, quoted on its own, that tells you what is slow and what fixing it would cost. If it is a website on our hosting, the problem may be the plan, and we’ll tell you.

Common Questions

Can you speed up a system someone else built?

Usually, yes, if we can see its code or database. The investigation will tell us.

Is my website slow because of hosting?

Sometimes. More often it is large images or the way the site is built. We’ll find out which.

Tell us what feels slow.

Start a Conversation