Meatloaf927

2,627 rated blitz games · the whole archive, 100 days · 2026-05-23 to 2026-08-31 · current rating 2709

One unit, used throughout. Edge is measured in percentage points of score: how many points per hundred games you score above or below what your rating predicted against the opponents you actually faced. Zero is par. Near a 50% score one point of edge is worth about 7 Elo of equilibrium rating, and that is the conversion used everywhere a number is quoted in Elo.

The highest-value changes available to you

Nothing cleared the bar. No opening line, tilt pattern, session effect or colour asymmetry was both statistically significant and large enough to be worth acting on. On this sample that is a real result, not a gap in the analysis — it means the losses are distributed rather than concentrated in a fixable situation.

What the evidence does support

These are real: each is significant with the game as the unit of analysis. None carries an Elo figure, because none has a counterfactual measured inside your own games — you cannot elect to have blundered less, so there is no second group to compare against. A number here would be invented, and an invented number that looks measured is worse than none.

The move right after a blunder is the dangerous one

Your blunder rate is 2.7 per 100 moves normally and 11.1 on the very next move after a blunder — 4.1× the risk, on 2,769 such moves across 2,614 games (95% CI +7.2 to +9.7 points, p < 0.001). It decays but is still measurable 6 moves later, which was as far as this looked. This is the one thing on the page you can act on inside a single game, and it costs no study time: after a move you dislike, stop and look again before playing the next one.

The last ten seconds cost more than anything else

With more than 80 seconds left you blunder 1.5 times per 100 moves. Under ten seconds that becomes 9.6, a 6.6× increase. Some of this is that hard positions eat clock as well as causing mistakes, so it is not purely the hurry — but the size of the gap is not explained by that alone.

You see material; you miss forced mate

Across 22,091 tactical moments you find 69% of forced mate chances (95% CI 64–74) against 97% of hanging piece chances (96–97). The intervals do not overlap. This is the same pattern as the winning positions you dropped, where the moves you missed were the quiet ones: what is obviously material you take, what has to be seen you sometimes do not.

You do not slow down for the moves that need it

When the tactic is forced — a recapture, a move with one sensible answer — you find 96%. When it has to be seen, you find 74%. Yet you spend 3.36s on the genuine ones against 3.07s on ordinary moves: 0.29 seconds more, on the positions that decide games. Nothing in your clock use distinguishes the critical moments from the rest, which is exactly the habit the blunder finding above also points at.

Your accuracy falls as the board empties

With 15 or more pieces on the board you blunder 2.0 times per 100 moves. At 9-10 pieces that rises to 5.6 — 2.8× — across 107,019 analysed moves. Piece count is a cleaner axis than the phase label, which is only a boundary rule; this is the same weakness stated in terms of the thing that actually causes it.

The endgame is your worst phase, not the middlegame

You blunder 5.4 times per 100 endgame moves against 2.3 in the middlegame (+3.1, p < 0.00001, across 1,826 games that reach both). That is the reverse of the usual pattern and it points study at technique rather than opening preparation.

The arc

2704 2517
Read this arc with care. The archive covers 100 days and opens 433 points below where it settles. On an account whose rated play starts from a provisional rating, that opening climb is Glicko finding your level, not you improving. The only part of the line that describes your chess is what happens after it flattens.

Monthly mean rating runs from 2517 (May 2026) to 2704 (Aug 2026) across 4 months with at least five games.

Splitting the window in half, the second half is worse by 3.1 points of score (1313 games against 1314, p = 0.068, not significant).

Openings reached with White

LineGamesScore %Opp EloPerf EloEdgepq
Caro-Kann Defense17768.625572693+5.50.0800.231
Ruy Lopez24867.525572684+3.80.1490.231
Sicilian Defense48465.725652678+2.20.2580.309
French Defense14757.825472602-6.60.0760.231
Pirc Defense4557.825392594-6.70.3410.341
Scandinavian Defense5056.025452587-9.40.1540.231

These are openings reached while playing white, named by the opening rather than by whose choice it was: as White you appear here under your opponent's defence. Ordered by score %, the number you feel at the board — but read it beside Opponent Elo, because a line can score well simply because weaker players reach it. Where score %, performance and edge disagree, edge is the one to trust: it is the only like-for-like comparison. q is the Benjamini-Hochberg false-discovery rate across the 6 lines tested here; testing that many guarantees some p < 0.05 by chance, and only lines with q < 0.05 survive that correction.

After false-discovery correction, none of these 6 lines is distinguishable from par. Any ordering you see above is within what chance produces at this sample size — which is itself the finding: the repertoire is not where the points are going.

Openings reached with Black

LineGamesScore %Opp EloPerf EloEdgepq
English Opening8371.125732729+8.10.0810.484
King's Indian Attack, with Bf55468.525732708+7.40.2200.562
Sicilian Defense62264.525572660+1.00.5620.562
Queen's Indian Defense14263.025612654-2.40.5280.562
Nimzo-Indian Defense11462.325532641-2.60.5430.562
Indian Defense9358.625712631-3.50.4660.562

These are openings reached while playing black, named by the opening rather than by whose choice it was: as White you appear here under your opponent's defence. Ordered by score %, the number you feel at the board — but read it beside Opponent Elo, because a line can score well simply because weaker players reach it. Where score %, performance and edge disagree, edge is the one to trust: it is the only like-for-like comparison. q is the Benjamini-Hochberg false-discovery rate across the 6 lines tested here; testing that many guarantees some p < 0.05 by chance, and only lines with q < 0.05 survive that correction.

After false-discovery correction, none of these 6 lines is distinguishable from par. Any ordering you see above is within what chance produces at this sample size — which is itself the finding: the repertoire is not where the points are going.

What this sample could have detected

Game-to-game variation in edge has a standard deviation of 44 points, which is large: a single game is won or lost, and one result tells you almost nothing. That sets a floor on what any number of games can resolve. The column below is the smallest edge that would have reached p < 0.05 in each line, given how many games you actually played in it.

LineGamesObserved edgeDetectableVisible?Games needed
Sicilian Defense (black)622+1.0±3.4no7148
Sicilian Defense (white)484+2.2±3.9no1491
Ruy Lopez (white)248+3.8±5.4no493
Caro-Kann Defense (white)177+5.5±6.4no240
French Defense (white)147-6.6±7.0no168
Queen's Indian Defense (black)142-2.4±7.2no1262
Nimzo-Indian Defense (black)114-2.6±8.0no1088
Indian Defense (black)93-3.5±8.9no603
English Opening (black)83+8.1±9.4no110
King's Indian Attack, with Bf5 (black)54+7.4±11.6no133
Scandinavian Defense (white)50-9.4±12.1no83
Pirc Defense (white)45-6.7±12.7no160

Games needed is how many games in that line it would take for an effect of the size you are already showing to become statistically visible. Where it is close to the games you have, the line is worth continuing to watch rather than acting on.

Every one of these 12 lines shows an effect smaller than this sample can resolve. That is the real reading of the empty recommendation list above: not that your repertoire is uniform, but that at 2,627 games spread across 12 lines, nothing you are doing is far enough from par to separate from chance. The honest summary is no fixable leak is visible yet, which is not the same claim as no leak exists.

Thematic plans inside your openings

Each row replays your games in one opening family and splits them on whether a thematic idea actually appeared. 36 plans were tested, so the raw p-values cannot be read at face value: at p < 0.05 you would expect about 2 to look significant by chance alone. The q column corrects for that across the whole set, and 0 survive it.

PlanGames in familyUsed inWorthpq
kingside expansion f4–f5 (Sicilian Defense, white)48414%-17.60.0030.11
the ...f5 break (Sicilian Defense, black)62224%-8.50.0370.22
queenside expansion ...b5 (Queen's Indian Defense, black)14268%+18.40.0280.22
kingside fianchetto ...g6 (Queen's Indian Defense, black)14266%+17.10.0370.22
the ...f6 break (Nimzo-Indian Defense, black)11431%-23.00.0130.22
queenside expansion ...b5 (English Opening, black)8358%-18.30.0330.22
f3 (Sämisch / big centre) (Ruy Lopez, white)24821%-11.60.0740.38
queenside expansion ...b5 (Sicilian Defense, black)62259%+5.50.1260.57
problem bishop out before ...e6 (Sicilian Defense, black)62247%-4.90.1640.57
queens off early (by move 15) (Sicilian Defense, black)6227%-8.70.1880.57
kingside pawn storm ...g5/...h5 (Sicilian Defense, black)62238%-4.80.1810.57
castled queenside (Sicilian Defense, black)6225%-9.80.2050.57
queenside expansion ...b5 (Indian Defense, black)9350%+12.10.2030.57
the ...f6 break (Sicilian Defense, black)62219%-5.40.2260.58
the ...e5 break (Queen's Indian Defense, black)14232%-9.30.2740.63
kingside pawn storm ...g5/...h5 (Indian Defense, black)9340%-10.60.2800.63
kingside fianchetto ...g6 (Indian Defense, black)9360%+9.90.3210.68
f3 (Sämisch / big centre) (Sicilian Defense, white)48420%-3.90.4090.82
kingside pawn storm ...g5/...h5 (Nimzo-Indian Defense, black)11442%-5.50.5230.99
minority attack (b4 and b5) (Sicilian Defense, white)4847%-0.60.9361.00

Worth is the difference in edge between the games where the idea appeared and the games where it did not, inside the same opening family. Only rows with a bold q below 0.05 survive correction; the rest are shown so you can see the full set that was searched rather than only its winners.

Nothing here survives correction. The strongest raw p-values in this table are what searching fifty splits produces on noise, and acting on them would be acting on chance.

What the engine sees

Stockfish 18 evaluated every position in 2,614 of these games at a fixed 150,000-node budget — 107,030 of your own moves. Nodes rather than depth or time, so the numbers do not move with machine load.

Mean centipawn loss 29, mean move accuracy 92.6, blunders 2.8 per 100 moves.

PhaseMovesMean cp lossAccuracyBlunders / 100
Opening26,019996.70.1
Middlegame45,6733390.82.9
Endgame35,3383892.04.7

Accuracy against the clock

Time leftMovesAccuracyBlunders / 100
under 5s1,05890.79.8
5-10s1,44191.28.9
10-20s3,70391.47.0
20-40s8,50191.16.5
40-80s17,86690.75.0
80s+74,39793.41.4

Time remaining when the move was played. This is descriptive, not causal: hard positions eat clock and also cause mistakes, so some of this gap is the position rather than the hurry.

You against the players you actually face

MovesMean cp lossAccuracyBlunders / 100
You107,0302992.62.83
Your opponents106,7573391.73.35

The same engine, the same node budget, the same positions — the cleanest like-for-like comparison available, because you and your opponent faced literally the same games.

Errors against material left on the board

PiecesMovesMean cp lossAccuracyBlunders / 100
1-42,2972197.23.61
5-62,8963694.15.42
7-84,1763892.95.51
9-105,2874291.65.60
11-125,6904091.55.17
13-146,6874290.75.16
15+79,9862592.72.03

Every ply tagged with the actual piece count rather than a phase label. The phase boundary is a rule of thumb; this is the quantity the question is really about, and it separates the same games more cleanly.

How long the risk stays elevated after a blunder

Moves laterBlunder rateRate otherwiseDifference95% CIp
111.12.7+8.4+7.2 to +9.7< 0.001
29.72.8+6.9+5.7 to +8.1< 0.001
37.82.9+4.9+3.8 to +6.0< 0.001
49.03.0+6.0+4.7 to +7.3< 0.001
57.53.1+4.4+3.3 to +5.5< 0.001
68.03.2+4.8+3.5 to +6.1< 0.001

Rates pool every move, which is the honest estimate — averaging per-game rates would bias it upward, because a short game with one blunder reads as a high rate and then counts the same as a long one. The interval instead comes from resampling whole games, so the fact that moves inside a game are not independent is priced into the uncertainty rather than ignored. Testing per move would produce far smaller p-values here, and they would be wrong.

Winning positions

You reached a position the engine scores at +3.00 or better in 1,734 games (66% of the analysed set) and scored 85.0% from them (95% CI 83.2–86.6). 318 of those games were not won.

No Elo figure is attached to this. Converting every winning position is not available to anyone, so the gap to 100% is not a gain you could bank, and quoting it as one would be inventing a number.

Which tactics you find, and which you miss

Every position in the analysed games was checked for a tactical opportunity, and the move you actually played was compared against it. 22,091 tactical moments across 2,509 games; you found 82.2% of them overall.

MotifMomentsFound95% CI
forced mate38668.9%64.0–73.8
quiet / positional3,99374.4%72.9–75.9
check / king attack2,04575.3%73.3–77.5
wins a loose piece2,49576.8%75.1–78.4
fork1,23876.8%74.3–79.3
back rank97078.6%75.8–81.1
discovered attack57180.6%77.3–83.9
skewer1,97781.0%79.4–82.7
passed pawn push63481.2%78.1–84.6
pin40881.4%77.5–85.0
wins a pawn1,13087.5%85.5–89.6
favourable exchange81590.1%87.6–92.4
removes the defender2,29391.3%90.2–92.4
hanging piece3,07896.6%95.9–97.2

Sorted worst first. Red is below your own overall rate of 82.2% with the interval clear of it, green above. Intervals come from resampling whole games, because several tactical moments in one game are not independent observations.

Train the weakest one. There are 96 positions in your own games where a forced mate was on the board and you played something else — 40 of them mate in three or fewer. Each was re-searched until the engine proved the mate, and anything it would not prove was dropped. Mate in one is left out: seeing it is the whole exercise. Work through them.

How long you thought, and whether you found it

Time on the moveMomentsFound
under 1s8,68890.0%
1-2s6,59586.8%
2-4s3,37475.8%
4-8s2,20764.2%
8s or more1,22751.8%

This runs the wrong way at first glance — the longer you thought, the less often you found it — and it is not evidence that thinking hurts. The causation runs the other way: you stop to think precisely when the position is hard, so this is a map of difficulty rather than of effort. What it does say is that the positions where you spend your clock are ones you get wrong roughly half the time — which is where study would actually land.

Winning positions you did not win

Each of these is a position from your own games where the engine had you at +3.00 or better and the move you played threw most of it away. They are sorted by how much was lost. 5 of 20 had a quiet winning move — no capture, no check — which is the pattern worth noticing: the wins that get missed are the ones that do not announce themselves.

. . r . . . . .
P . . . . . . .
. . . . . . . .
. R b . . k . .
. . P . R p p .
. . . . . P . p
. . . . . . K .
. . . . . . . .

White to play, move 48

Engine had you at +5.3. You played Kh2; Kh1 wins (Kh1 gxf3 Re1 f2 Rf1 Kg4). That dropped 1532 centipawns — a quiet winning move.

2026-07-30 · opponent 2542 · endgame · 26s on the clock · game

. . . R . . . .
. Q . P q . k p
. . . . . . p .
p B . . b p . .
P . . . p . n .
. . . . . . . .
. P . . . . P P
. . . . . R . K

Black to play, move 35

Engine had you at +10.0. You played Qxd8; Qh4 wins (Qh4 Rg8+ Kh6 Rxg6+ hxg6 h3). That dropped 1359 centipawns — a quiet winning move.

2026-07-13 · opponent 2581 · middlegame · 103s on the clock · game

. . . . . . . .
. . k . P . . .
P . . p . . . p
. K . P . . . .
. . . . . . . .
. . . . b . . P
. . . . . . . .
. . . . . . . .

Black to play, move 50

Engine had you at +3.3. You played Ba7; Kd7 wins (Kd7 e8=Q+ Kxe8 Kc4 Kd7 Kb5). That dropped 1326 centipawns — a quiet winning move.

2026-06-09 · opponent 2470 · endgame · 13s on the clock · game

. r . . . b . k
. . R . . . . .
. . . . b . . p
. . . p P . . q
. . . P . Q . N
. . . . . . . .
. . . . . . P K
. . . . . . . .

Black to play, move 51

Engine had you at +2.7. You played Rb1; Bg7 wins (Bg7 Qf2 Kg8 Qg3 Bg4 Qf2). That dropped 1267 centipawns — a quiet winning move.

2026-07-17 · opponent 2587 · middlegame · 0s on the clock · game

r . b . . r k .
. . . n b . p p
p . n p N . . .
q . . N . . P .
. p Q . P . . .
. . . . . . . .
P P P B . P . P
R . . . K . . R

Black to play, move 17

Engine had you at +4.2. You played Qb5; Nde5 wins (Nde5 Qb3 Nf3+ Kd1 Bxe6 Nxe7+). That dropped 779 centipawns — a quiet winning move.

2026-07-17 · opponent 2586 · middlegame · 104s on the clock · game

. . . . . . . Q
p K . k . . . .
. p . p . . . q
. . p . . . . .
. . P . P . n .
. . . P . . . .
r . . . . . . .
. . . . . . . .

Black to play, move 47

Engine had you at +10.0. You played Qh7; Qxh8 wins (Qxh8 d4 Qc8#). That dropped 1539 centipawns — a forcing winning move.

2026-06-18 · opponent 2507 · endgame · 0s on the clock · game

r . . . . . . .
P . . . . . . .
. . . . . . . .
R . . . . p . .
. . . . . k . K
. . . . . . . .
. . . . . P . .
. . . . . . . .

Black to play, move 56

Engine had you at +10.0. You played Kf3; Rh8# wins (Rh8#). That dropped 1482 centipawns — a forcing winning move.

2026-06-04 · opponent 2583 · endgame · 4s on the clock · game

r . . . r b k .
. . . . . p . p
. . . . . . P .
. . . . B P . P
. p . . . P . .
. P . . . . . .
P K . R . . Q .
. . . . q . . .

Black to play, move 37

Engine had you at +4.6. You played Rac8; Rxe5 wins (Rxe5). That dropped 1462 centipawns — a forcing winning move.

2026-07-22 · opponent 2517 · middlegame · 44s on the clock · game

Situations

SituationGamesEdge hereEdge otherwiseDifferencep
Right after a loss765+2.7+0.2+2.40.189not significant
Right after a win1378+0.4+1.5-1.00.544not significant
Eleventh game of a session or later1128+0.1+1.6-1.40.406not significant

Each row compares that situation against every other game in the window, with the game as the unit of analysis. A difference that is not significant is reported as such rather than dropped, because the absence of a tilt effect is as useful to know as its presence.

The clock

You finish won games with a median of 58s left and lost games with 37s. 28 games (1.1%) ended in a loss on time.

How this page was made

Source: the complete Lichess export for Meatloaf927, 2,627 rated blitz games from 2026-05-23 to 2026-08-31, restricted to the the whole archive, 100 days.

Every p-value uses the game as the unit of analysis. This is not a detail: testing at the level of moves treats the forty moves of one game as forty independent observations, which they are not, and inflates significance to the point where almost anything looks real. Two-sided Student's t throughout; Welch's variant where two groups of games are compared. Opening tables carry a Benjamini-Hochberg false-discovery rate because testing thirty lines at p < 0.05 produces roughly one and a half false positives by construction.

Sections appear only where the data supports them. Nothing on this page is hand-written about this player: every number, every opening name and every recommendation is derived from the archive at build time.