Avatar of Aleksa Strikovic

Aleksa Strikovic GM

lestri A Coruña Since 2014 (Inactive) Chess.com ♟♟♟♟
63.4%- 26.4%- 10.2%
Bullet 2393
62W 26L 3D
Blitz 2661
250W 105L 40D
Rapid 2343
75W 30L 19D
Coach Chesswick's Profile Photo
Coach Chesswick

Quick summary

Aleksa — nice work. Your blitz play shows clear strengths: active piece play, good use of central breaks and queen activity to punish loose kings, and a reliable opening base that gets you playable middlegames. The recent loss highlights a recurring theme: tactical oversight around knight forks and pawn breaks (especially c4), and some timing/prophylaxis issues. Below I break down the win and the loss, then give a compact training plan and a short checklist to use during blitz.

What went well (from your most recent win)

  • You converted pressure into concrete gains: after simplifying into an active queen + pawns attack you created threats that White couldn't parry. That shows good feel for turning initiative into tactical threats.
  • You used pawn breaks and exchanges to open lines for your pieces (especially the queen). Keeping the queen active and looking for checks worked well.
  • You were comfortable trading into a simplified position where your opponent's king was exposed — good sense for when to simplify and when to keep tension.
  • Opening play was smooth: typical structure from the English Opening led to a playable middlegame where you found the right breaks.

Where to improve (from your most recent loss)

  • Tactical vigilance: the decisive moment came from a knight jump to g4/f2-type squares combined with a pawn push (c4). Before pushing pawns or committing your pieces, double-check whether a single knight penetration or a fork is possible.
  • Prophylaxis and making luft for pieces: after you advanced queenside pawns (for example a5) the opponent gained tactical targets. Ask yourself: “Does this move allow enemy pieces an outpost or a tactic?”
  • Handling the c4 break: when your opponent prepares c4, compute the consequences — is it a permanent pawn that opens a squishy file or creates a knight outpost? If you’re not sure, delay or prepare with a defensive piece move instead of an immediate flank push.
  • Blitz-specific calculation: with limited time, prioritize checks/captures/threats — scan for forks, pins, and skewers before every move. That one extra second of scanning prevents many tactical losses.

Concrete examples (review key sequences)

Study the decisive sequence from the loss — it ends with a knight jumping into your camp creating decisive forks. Replay it and ask “what did I miss?”

Tactical & positional focus (short list)

  • Always check for forks and discovered attacks after an exchange or pawn push — especially knight jumps to e4/g4/f2 squares.
  • Before committing a flank pawn advance (a4/a5 or b4/b5), examine whether it gives your opponent a central break or an outpost.
  • When you have the initiative, prioritize moves that increase piece activity or restrict the enemy king — not just grabbing space.
  • In positions with c-file or d-file tension, calculate whether the c4/c5 break helps the opponent open lines toward your king or creates a passed pawn for them.
  • Back-rank and king safety: when exchanging heavy pieces, always check for back-rank weaknesses and whether queens + rooks can deliver checks.

Practical blitz training plan (for the next 2–4 weeks)

  • Daily 15–20 min tactics: focus on forks, skewers, and discovered attacks. Use a mix of easy and medium problems so you build pattern recognition under time pressure.
  • Two times per week: 30–45 minute focused session on positions with pawn breaks (c4/c5, f5/f4). Set up typical structures from the King's Indian Defense and English Opening and practice the key breaks and defensive ideas.
  • One weekly game at longer time control (15+10): when you lose a blitz game, replay it at slow time and force yourself to find the defensive resources you missed in blitz.
  • Endgame refresh: 10–15 minutes twice a week on common simplified positions you reach after exchanges (queen vs pawns, rook vs minor piece). You convert wins more reliably if you know basic conversion techniques.
  • Blitz checklist drill: before pressing the clock, quickly ask — “checks/captures/threats?” — train this until automatic.

Short tactical drills you can do right now

  • 10 knight-fork puzzles in a row — keep score and repeat until you get 9/10 within 5 minutes.
  • Set up a pawn-structure with c4 vs c5 tension and practice calculating c4 and c5 breaks both sides — especially the reply moves and knight outposts.
  • Play 5 rapid games (10+5) where you deliberately practice the “scan for tactic” routine before each move.

Short checklist to use in blitz (copy/paste to a sticky note)

  • 1) Any checks/captures/threats? (1–2 sec scan)
  • 2) Does my last pawn move create an outpost for their knight or a tactic?
  • 3) Before exchanging queens/rooks: check back-rank and king safety.
  • 4) If I’m low on time, simplify when I have a clear small advantage; avoid complications when behind.

Useful opponents / positions to review

  • Review your games versus kapinovo — you had both a recent loss and a recent win in that mini-match; comparing the two is very instructive.
  • Replay the win and the loss back-to-back and pause at every critical pawn push (c4/c5, a4/a5, f5/f4) to ask “what changed?”
  • Study model games in the English Opening and the King's Indian Defense to see how strong players time pawn breaks and knight jumps.

Next steps (this week)

  • Do the tactical drill and the 10-minute pawn-break practice three times this week.
  • Play two 10+5 games and one 15+10 game, and analyze the critical moments at slow time afterwards.
  • Keep the blitz checklist visible and force yourself to run through it before pressing the clock.

Want me to do a deeper post‑mortem?

If you want, I can analyze one of these games move-by-move and point out exactly where the evaluation swings happen, with candidate-move suggestions and short lines to practice. Tell me which game to deep-dive (win or loss) and whether you want engine suggestions or human-plausible improvements.

Opponents mentioned above: kapinovo and JOVELJIC1999.


Report a Problem