Start here. This is the direct spoken answer to practice first.
Overview
A slow Angular screen can come from framework work, application computation, browser rendering, or data latency, so measurement comes first.
I reproduce one slow interaction in a production build and record it with browser performance tools and Angular profiling support. I determine whether the time is spent in network work, JavaScript, repeated change detection, a specific component, layout, or paint. Then I fix the measured bottleneck and compare the same interaction again.