Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Every release makes our app a little slower

Short answer

Software rarely gets slow in one step. Each release adds a little: another query, another image, another library, and no one measures. Pick two or three actions customers care about, time them before every release and record the numbers. A change that makes one of them slower is fixed or reconsidered before it ships.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Pages and screens load slower than a few months ago.
  • Customers say the app used to be faster.
  • Nobody can say which release caused the slowdown.
  • The server has been upgraded, and it did not help for long.
  • Complaints start after updates and then fade, then return.

Why does this happen?

  1. Nobody is measuring

    Without numbers, small slowdowns look like noise. After twenty releases the total is large and no single change is to blame.

  2. Data grows while the code stays the same

    A query that was fast with a thousand rows can be slow with a million. The app may not have changed in that area, but the data did.

  3. Each addition is small, the sum is not

    A tracking script, a larger image or an extra database call hardly matters alone. Together they add seconds.

  4. Test data is small and the network is fast

    Developers test on fast computers with little data. Real customers use older phones and slower connections, so problems appear only there.

What can I do about it today?

  1. Pick the actions that matterChoose two or three, such as opening the home screen, searching or paying. These are what you measure.
  2. Time them todayUse a phone and a stopwatch if you must, on a normal connection, and write the numbers with the date. This becomes your starting line.
  3. Ask which releases came before the slowdownAsk your developer for the release dates, and compare them with when customers began to complain.
  4. Ask for a check before every releaseAsk that the timing be repeated before each release and that the numbers be shared with you.
  5. Do not simply buy a bigger serverMore hardware may hide the problem for a while and make the cost permanent. Find out which part is slow first.

When should I bring someone in?

  • You have been told the app is slow but no one can say why.
  • The slowdown has reached customers and they are leaving.
  • A bigger server did not help.

How do I handle it?

  1. Take a baselineI measure the key actions on the live system and on realistic devices, and store the numbers.
  2. Find where the time goesProfiling and query logs show whether time is lost in the app, the database, the network or the page itself.
  3. Fix the largest cause firstOne or two fixes usually give most of the gain. Each one is checked against the baseline.
  4. Add a gate to the release processA release that makes a key action slower than agreed is stopped and reviewed before it goes out.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

How slow is too slow?

There is no single number. Compare with your own earlier numbers and with what your customers accept, and treat a steady upward trend as a warning.

Can this be fixed without rewriting the app?

Usually, yes. Most slowdowns come from a few specific causes that can be fixed one by one.

Does a new release always have to be slower?

No. Features can be added while keeping speed, if the key actions are measured and protected.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.