What Counts as a Good Parse

"What did you parse?" is one of the most common questions in raiding, and one of the most misunderstood. A parse is a percentile rank, not a score. Understanding exactly what it ranks you against — and what it deliberately ignores — is the difference between using parses to improve and using them to feel bad for no reason.

A parse is a percentile

When Warcraftlogs gives you a 90 on a boss, it does not mean you did 90% of some maximum. It means that out of everyone of your class and spec who killed that boss at that difficulty, you performed better than 90 percent of them on the metric being ranked. A 99 means you were in the top one percent. A 50 is literally average — the median player. This is why a parse is only meaningful relative to a population, and why the population matters enormously.

The color brackets

Warcraftlogs colors percentiles so you can read them at a glance. The widely used scale is grey for the bottom quarter (1–24), green for 25–49, blue for 50–74, purple for 75–94, orange for 95–98, and pink (often called "legendary") for 99–100, with a special gold tone for a perfect 100. The colors are borrowed from item rarity on purpose: most players intuitively know purple is good and orange is rare without doing any math.

The important nuance is that the brackets are not evenly spaced in difficulty. Climbing from green to blue is mostly about not making mistakes. Climbing from purple to orange is about near-perfect execution. Going from 99 to 100 can require a specific group composition, optimal lust timing, and some luck. The visual scale hides how steep the top end is.

Why a 99 on one fight is harder than on another

Not all 99s are equal. On a pure single-target tank-and-spank fight with no movement, the field is enormous and tightly packed, so squeezing into the top one percent demands a flawless rotation and an ideal setup. On a chaotic fight with heavy movement, forced target swaps, and add priority, there is far more room for skill expression and the field spreads out — a strong player can post a very high parse with sound decisions rather than frame-perfect play.

There is also a timing effect. Early in a tier, before classes are well geared and strategies are refined, percentiles are volatile and a good parse is easier to get because the field is weak. As the tier matures, the same raw performance ranks lower because everyone else caught up. A 95 in week one and a 95 in week twenty are not the same accomplishment, even though the number is identical.

What a parse does not measure

A parse measures one metric — usually damage or healing throughput on that encounter — relative to a population. It does not measure whether you did your job. It does not know that you were assigned to soak a mechanic, kite an add, interrupt a caster, or hold cooldowns for a later phase. All of those correct decisions can lower your parse. A player with a 70 who executed their assignment perfectly contributed more to the kill than a player with a 95 who ignored mechanics to pad damage and got carried.

This is the single most important thing to internalize: the parse is a proxy for performance, not performance itself. It is an excellent tool for spotting your own rotational and uptime problems, and a terrible tool for judging whether a teammate is good. Use it on yourself, gently on others.

So what is a "good" parse?

For most raiders, a useful mental model is this: consistent blues and purples across a tier means you are executing solidly and should look for marginal gains. Consistent greys and greens means there is a systemic problem worth investigating — usually uptime, cooldown usage, or consumables long before it is your rotation. Oranges and above are the domain of dedicated optimization, often with help from group composition and external buffs you do not fully control.

The healthiest target is not a number. It is a trend. A player moving from green to blue to purple over a tier is improving faster than a player sitting flat at a static purple. Track the direction, not the digit.

To act on this, learn why your parse can differ from your damage meter and then how uptime drives most parse gains. You can also see your award history across logs on a ParseCard leaderboard.