How to run a performance review that changes something
A meeting where everyone agrees the site is slow is not a review. It is a shared feeling.
Bring three things or do not bring the meeting: a number, its trend over four weeks, and one change you want to make. Everything else is a conversation about vibes.
“It feels slower” and “LCP moved from 2.1 to 3.4 seconds over four weeks” produce completely different meetings, and only one of them ends with a ticket.
Ana Fielding, performance engineer
Close by writing down what you expect the number to be in two weeks. If you were wrong, that is the most useful thing you will learn all month.