This game · 148 FGA|Season model · 357 games · 48,742 shots
Connecticut Sun won on finishing, not shot quality.

led the way with 18 points on 6-for-11 (55%), headlined by 5-for-7 from above the break — 5.9 more than expected overall on a night most other looks were tougher.
- Toronto Tempo created 3.6 more expected points from field-goal attempts.
- Connecticut Sun outperformed expected value by 7.5 points on makes and misses.
- Q1 swung the look battle — Toronto Tempo built a +4.0 expected-point edge in that period.
Shot quality
Shot diet
Connecticut Sun (34% good looks) and Toronto Tempo (42% good looks) ran comparable diets with small zone-by-zone differences.

carried the offense at the rim — 6/7 in the restricted area.
This is where the shot diets diverged most — 35% of Toronto's attempts came from the rim vs 31% of Connecticut's, with Toronto leaning on the higher-value zone (35% vs 31%).

This is where the shot diets diverged most — 35% of Toronto's attempts came from the rim vs 31% of Connecticut's, with Toronto leaning on the higher-value zone (35% vs 31%).
Possession context

Inferred from ESPN play-by-play — transition, steals, and offensive rebounds before each FGA. Not official possession tracking.
Process scorecard

Full process edge
Connecticut Sun won by 17.8 pts — SQ edge said TOR.
Toronto Tempo got the better looks, but Connecticut Sun won the full process battle by 17.8 pts.
Process edge blends expected points from shots, finishing, free throws, turnover cost, and second-chance value — not just who found the better offense.
Tracked FGA
ESPN box score
Process value (pts)
Process total = expected pts from shots + finishing + free throws − turnover cost + second-chance value (1.05 expected pts per OReb). SQ edge alone ignores the last three terms.
Player shots
Key insightAngloma struggled most from Above — 0/2 against a 39% baseline.
Expected value is an estimate from public shot data — location, shooter history, and shot clock. No defender distance, closeout speed, spacing, or proprietary tracking.
Learn how it works →



