Quality of experience score (QoE score)
A quality of experience score is a single number, usually 0 to 100, that sums up how good video playback felt to a viewer. It blends how fast the video started, how often it stalled, and how sharp it looked. One score makes it possible to compare days, regions, devices or releases at a glance instead of reading a dozen separate metrics.
Why it matters
Leaders cannot read a dozen playback metrics every morning, but they can watch one number. A single score makes it quick to see whether a release, a new CDN or a new market made viewing better or worse, and it gives product, engineering and business teams a shared target. A team can put that shared number on its dashboard without changing players, because FastPix Video Data calculates a QoE score on any supported player, with 100,000 plays a month included free.
How it works
- The player reports events for every view, such as start time, buffering, errors and the resolution shown on screen.
- Each view gets sub-scores for how fast it started, how smoothly it played and how sharp it looked.
- The sub-scores are weighted and combined into one number, usually on a 0 to 100 scale.
- Scores are averaged across views so they can be compared by day, country, device, title or player version.
What is a good QoE score?
There is no universal standard, because every vendor weights its score differently, so a good score is one that holds steady or rises against your own baseline. As a rough guide, many teams treat scores in the 90s as healthy and investigate any sustained drop of a few points. Compare scores only within the same tool, and always check which sub-score moved.
QoE vs QoS: what is the difference?
QoS (quality of service) measures the network and delivery side, such as throughput, request latency and CDN errors. QoE (quality of experience) measures what the viewer actually felt: waiting to start, stalls and picture sharpness. Good QoS usually leads to good QoE, but not always. A fast network cannot fix a slow player or a weak device, which is why teams track both.
How is a QoE score calculated?
A QoE score is calculated by grading each view on a few experience factors and combining them with weights. Typical factors are startup time, buffering and picture quality. For example, a view might score 95 for smoothness, 80 for sharpness and 70 for startup, and a weighted blend gives one view score. The platform then averages view scores over the period you select. If you want to know exactly why your score moved, FastPix Video Data publishes its weights: 0.395 x stability + 0.330 x render quality + 0.275 x startup.
Where it's used
OTT services and online learning platforms put a QoE score on their main dashboard so a product lead can tell at a glance whether this week's viewers had a better or worse experience than last week's.
Where it usually goes wrong, and how FastPix handles it
Teams often watch one blended score without knowing what drives it, so when the number drops they cannot tell whether startup, buffering or picture sharpness caused the change.
Stability, render quality and startup each get their own score in FastPix Video Data, next to the blended QoE score for the view. It works with any supported player, with or without FastPix delivery. When the number drops, your team can see which part moved and hand the problem to the right owner.
By the numbers
- In a 2012 study of 23 million video views, viewers began abandoning videos that did not start within 2 seconds, and each extra second of delay raised abandonment by about 5.8 percent. (Research quantifies how video stream quality affects viewer behavior (ScienceDaily, 2012))
- A 2012 study of online video viewers found that a viewer whose video froze for 1 percent of its duration watched 5 percent fewer minutes than a comparable viewer whose video did not freeze. (Research quantifies how video stream quality affects viewer behavior (ScienceDaily, 2012))
