Good internet does not explain the whole wait.

Is the content slow to appear?

Note whether the whole page is blank, the main image arrives late or text waits for a font. Keep the page address and approximate time. The investigation may need to follow both the server response and the browser’s work to display the page.

Does the page ignore a click?

Try to describe the exact action: opening a menu, selecting a filter or adding a product. Note whether the delay happens immediately after opening the page or also after it has settled.

A recording can help show the timing, but remove private information before sharing it. Do not use real payments or customer messages just to make an example.

Does the page move under your finger?

Say which element shifts and what you were about to press. A later image, banner or embedded section may change the space available. The repair should check the affected interaction, not only whether the page eventually looks correct.

Keep comparisons honest

Record the phone, browser, page and whether it was a first or repeat visit. Those details make it easier to reproduce the example. Do not compare different pages or devices as though they were the same test.

Google’s Core Web Vitals guidance separates loading, responsiveness and visual stability. Controlled tests help investigation; real-visitor measurements describe conditions experienced outside that test.