Why is your website or web app slow? Find the cause before rebuilding
Measure the actions people actually struggle with, then decide whether images, network requests, code or database queries need attention.
The workflow illustrates a possible design and is not a client case study.
- Measure real journeys
- Locate bottleneck
- Compare outcomes
Which customer action is actually slow?
A fast home page can hide slow search, checkout or administration. An app that runs well on a developer’s computer may struggle on a phone or with more records. A single test score cannot tell you whether the framework needs replacing.
Measure where the time goes
Use Web Vitals alongside browser and server measurements. Separate time spent rendering, transferring data and processing requests. Include database queries and business actions, then choose changes that address the measured cause.
Choose one important customer action
Choose one action that has a clear effect on daily work. Record the device, connection, data volume and current performance. Fix one type of bottleneck at a time and compare under the same conditions. Track errors as well as speed and keep a way to reverse the change.
Try an older phone and slower network
Try less powerful phones, slower connections, a first visit, larger datasets and busy periods. Check that caching does not reveal restricted or outdated data, and that transactions still work correctly. Keep lab results separate from measurements of real visitors.
Bring steps to reproduce the slowdown
Describe the slow actions, when they happen, the devices used and the steps needed to reproduce them.