Chrome and Firefox desktop · Research guidance. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Define the slow action
Record whether the whole browser is unresponsive, one page is slow or only the video picture stalls. These are different observations. Browser process tools can show resource use, but a high reading is not automatically a fault or a measure of internet speed. Keep the intended programme and other activity stable while observing.
Open the browser’s own view
Google documents Chrome’s More tools, Task manager route and sorting by memory. Mozilla documents Firefox’s Task Manager or about:processes page, including memory and CPU columns. Use the relevant browser view rather than assuming an operating-system process name identifies one exact website.
Read the numbers with their scope
Mozilla calls its readings rough estimates and notes that enabled extensions share an Extensions process entry. A large combined entry therefore does not identify one extension on its own. In either browser, note the named task and the action occurring at that time rather than comparing unrelated screenshots from different workloads.
Observe before ending anything
The process view offers actions that can close tabs or processes. Google warns that ending a task loses unsaved work. Save forms and other work first, and prefer ordinary closing for an unwanted tab that still responds. Do not terminate an unfamiliar process merely because its number is the largest.
Use a bounded comparison
If you close one unnecessary task, repeat the original action and record the difference. Preserve the browser version, task name and rough reading without exposing private tab titles or URLs. The observation can support a resource question; it does not verify a service account, establish a delivered bitrate or prove that every stall came from memory pressure.
Questions, answered
Does the largest number identify the faulty website automatically?
No. Interpret the process scope and workload first.
Can ending a task lose work?
Yes. Google explicitly warns about unsaved work loss.