Why is your website or web app slow? Find the cause before rebuilding
The home page may load quickly while customers wait on search or checkout. Measure those actions and find where the delay occurs before choosing changes to images, code or the database.

The workflow illustrates a possible design and is not a client case study.
- Measure real journeys
- Locate bottleneck
- Compare before and after
Which customer action is actually slow?
Search, checkout and administration can be slow even with a fast home page. An action that works well on a developer's computer may take much longer on a phone or with more records. Assess performance through the way people use the app and the conditions in which the delay occurs. A single test score is too little evidence for replacing the framework.
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 an action whose delay affects daily work. Record its current timing along with the device, connection and data volume. Change one type of bottleneck at a time, then compare speed and errors under the same conditions. Keep a way to return to the previous version if the change causes problems.
Try an older phone and slower network
Try older phones and slower connections, then test first visits, large datasets and busy periods. If caching is involved, check for stale or restricted data and make sure transactions still complete correctly. Review lab results separately from real-visitor measurements to see whether the improvement carries through to actual use.
Bring steps to reproduce the slowdown
Describe the slow actions, when they happen, the devices used and the steps needed to reproduce them.