Chrome and Firefox desktop developer tools · Research guidance. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Establish the intended baseline
If developer tools were opened during support, inspect their current network controls before comparing the page with normal browsing. A tool used to observe a fault can also change the conditions. Write down what is enabled so the result is tied to a known setup instead of an assumption that opening a panel is always passive.
Review throttling and offline simulation
Chrome documents network throttling presets and an Offline option; Firefox’s Network Monitor also exposes a throttling menu. Read the actual selected state. A simulated slow or disconnected condition is a deliberate diagnostic tool, not a measurement of the household’s broadband connection or the service’s normal delivery capacity.
Inspect cache and blocking choices
The publisher documentation describes disabling cache and request-blocking controls. Keep these separate from clearing stored account data. A browser with cache deliberately disabled can request resources differently from a later ordinary visit, while an enabled blocking pattern can prevent a request from being sent as normal.
Restore the intended environment
After an agreed comparison, return temporary diagnostic controls to the intended baseline and repeat the same harmless action. Record both states if the difference matters. Do not describe an improvement as a universal repair unless the actual cause is established; the useful evidence is that a named setting changed a reproducible result in one browser environment.
Questions, answered
Does an Offline simulation prove the real network disconnected?
No. It changes the browser’s diagnostic conditions.
Are Disable cache and delete account data the same action?
No. Keep those controls and consequences distinct.