Media diagnostics · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Start with a baseline
The browser method getVideoPlaybackQuality returns metrics for a video element, including frame counts. MDN also notes that totalVideoFrames includes dropped or corrupted frames; it is not simply a count of successfully displayed pictures. A report which says ten dropped frames without a starting value or observation window gives too little context. Ten accumulated during startup is a different observation from ten appearing during a specific short scene.
Calculate only the interval you observed
An original arithmetic example starts with 12 dropped frames and 2,000 total frames, then ends with 18 dropped frames and 2,600 total frames. The differences are six and 600. Six divided by 600 is one percent for that interval, using these illustrative counters. Dividing the ending dropped total by the interval total would mix different windows. Keep the raw readings as well as the calculation so another person can check what was compared.
Do not assign a cause from the counter alone
Pair the interval with the actual visible symptom and browser, device, source dimensions and playback action. A rise in dropped frames provides a useful rendering observation; it does not alone prove packet loss, a slow subscription server or an unsupported codec. Repeat only a relevant controlled comparison, such as the same permitted sample with a heavy background task closed. State the changed condition instead of treating one percentage as a universal quality score.