Skip to article content

Your website is slow on some pages: what to check first

The homepage loads normally, but product pages, search or a form take longer to respond. Learn how to find where the delay happens and what information can help resolve it.

Start with a delay you can describe

The homepage opens normally. You visit the catalogue, choose a filter and wait. Saying “the website is slow” captures your experience, but leaves an important question unanswered: which step is slow, and under what conditions?

When only some pages are affected, compare specific pages and actions. The pattern may point towards a type of content, a feature or a recurring situation. That helps direct the investigation; it does not establish whether the cause is the server, images or code.

A useful first note might be: “On my phone, searching for a reference and opening its product page takes a while; the homepage responds normally.” That describes a journey someone else can reproduce.

Compare pages that do different jobs

Choose a few representative pages. A homepage, listing and product page can share a design while doing different work. Include actions after the page appears, such as opening a menu, searching, filtering or using a form.

Pages and actions to check on your website
AreaWhat to checkWhat to record
HomepageOpen it and use the menu.When content appears and when the menu responds.
Listing or catalogueOpen it and change a filter.Whether the wait occurs on arrival or when results update.
Product or serviceOpen several examples and use their options.Which pages behave differently and what they share.
SearchRepeat a specific query.The query, results and point where the delay occurs.
Contact or checkoutAgree a test journey with the team.The affected step, without creating unplanned orders or messages.

Note when the wait begins: before any content appears, while a page finishes loading or after pressing a button. If a loading message appears immediately but results take longer, record that too. These are different situations and help your team choose what to measure.

Save complete addresses and the steps needed to reach the affected point. A page that opens normally provides a useful comparison, but does not represent the whole website.

Record the conditions before comparing

Note the date and time, device, browser, connection and whether you were signed in. Repeat the same journey and record occasions when it works normally too. Intermittent issues need that context.

A phone and a desktop computer represent different situations. An administrator may also experience the site differently from a customer. Keep these observations separate rather than treating them as equivalent tests.

If you use a testing tool, keep the report and tested URL. PageSpeed Insights provides lab data and real-user experience data where available; these describe different conditions. The official PageSpeed documentation explains their scope. Our article on a green PageSpeed score on a slow-feeling website explains how to interpret the difference.

An example: the catalogue waits, the homepage does not

Fictional example illustrating the method. These are not client measurements.

Imagine a shop whose homepage and product pages open normally, while filtering the catalogue takes longer. The same search is repeated on two devices and the delay follows the choice of a brand.

The useful observation is: “The delay can be reproduced when filtering this listing by brand.” The team will review what happens when that filter is used: where the information comes from and what the website needs to display the results. Until that is checked, the cause of the delay remains unknown.

Moving hosting or compressing every image before investigating this step might leave the delay untouched. If the site uses WordPress, a component inventory can help. See what to review before removing a plugin.

What to send to the team maintaining your website

Prepare a message that makes the situation reproducible: page, steps, conditions and expected behaviour. If you record your screen, keep personal details, credentials and order information out of view.

  • Journey: open the catalogue, select a brand and open a product.
  • Observation: the delay occurs when the listing updates, not when opening the product.
  • Context: date, device, connection and sign-in status.
  • Repetition: when it happens and when you cannot reproduce it.

This gives your team a clearer starting point for agreeing what to review and which access is needed. You do not need to diagnose the technical cause before asking for help.

Turn a general impression into a focused review

Showing where the delay happens gives your team a starting point for investigation. A localised problem may need a focused change; several affected journeys may justify a broader review. Slowness alone is not a reason to rebuild your entire website.

Nodo91 can help you assess your website’s performance, connect observations with evidence and decide what to investigate next. If other improvements are competing for attention, use our guide to prioritising website improvements to bring them together.