How to read the results page
Start with the score, then use the graphs and diagnostics to decide what to fix first.
How to read the results page
Show the results page first so the reader knows where to start.
Priority asset. Use this as the visual anchor for the guide.
Highlight the diagnostic cards and the 'what next' logic.
Call out the graphs that answer the first question: what is wrong?
Animate the user from upload state to results state to next action.
Use the same workflow loop as the social teaser.
Start with the score, but do not stop there
The score is a summary of release readiness, not the whole story. It compresses loudness, tonal balance, low-end stability, stereo, and dynamics into one number so you can triage quickly.
Use the score to spot the general direction. Use the diagnostics and graphs to decide the actual move.
- •A high score can still hide one bad translation problem.
- •A low score does not mean the whole mix is broken.
- •The point is to get from score to action fast.
Use the charts as filters
Loudness over time tells you whether the track holds together from section to section.
Spectral balance tells you where the energy lives.
Stereo and mono checks tell you whether the center survives outside the room.
Pick the smallest useful fix
If low end disappears in mono, fix the low end first.
If the mix is muddy, cut low-mid buildup before you reach for loudness.
If the mix is already warm or bright, keep the tonal character intact while you correct translation issues.
Related guides
Jump to the next most useful page from here.