URP performance mistakes I look for first

Start with the obvious frame costs

URP performance problems often look mysterious because they arrive through many small, reasonable choices. Too many lights. Expensive transparent layers. Post-processing with ambitions. Shaders that were introduced to the target device very late in the relationship.

Before changing architecture, I look for the cheap truths. What is the target frame budget? Which passes are active? Are we paying for features the scene does not need, because a checkbox once seemed harmless?

Make the pipeline visible

The frame debugger, render graph view, GPU timings, and simple before-after captures usually tell the story faster than speculation. Speculation is fun, but the GPU does not respect vibes.

A good optimization pass removes uncertainty. It does not just make the frame faster; it leaves the team with a clearer model of why the frame was slow. The model is the part that keeps paying rent.

Prefer recoverable changes

The first fixes should be reversible and easy to explain: reduce overdraw, simplify materials, control shadow settings, split quality tiers, or move expensive effects behind explicit constraints. Heroic rewrites come later, if the numbers still demand tribute.