# Optimizing Scratch Projects for Smooth 30 FPS > Eliminate lag by reducing expensive color checks, merging forever loops, and avoiding needless costume switches. Optimizing Scratch Projects for Smooth 30 FPS — Eliminate lag by reducing expensive color checks, merging forever loops, and avoiding needless costume switches. ## Core approach Scratch runs at 30 frames per second. Heavy pixel checks ("touching color?") and dozens of active forever loops are the main causes of slowdown. - Replace "touching color?" with "touching Sprite?" or distance math. - Drive all sprites from one main game-loop broadcast ("Tick"). - Never put "wait" blocks inside "Run without screen refresh" custom blocks. ## Pro tip & next steps Test on a lower-powered Chromebook or browser tab to spot bottlenecks early. - [All Techniques](/en/techniques/): Browse more English guides in this section. - [Scratch Block Dictionary](/en/dictionary/): Look up any Scratch 3.0 block with examples. Updated: 2026-11-23 Author: [Takamasa Suzuki](https://scratch.gmnavi.jp/about/author/) Japanese Edition: https://scratch.gmnavi.jp/techniques/optimization/ [Scratch Daizen (English)](https://scratch.gmnavi.jp/en/)