A backup you have never restored is only a hopeful file.
What to check next
We started by reading the code rather than the documentation, because the code is what runs. Most of the surprises in a WordPress project live in the gap between what a function promises and what the theme actually asks of it. An hour with the templates open told us more than a week of status meetings ever had, and it gave us a list of real questions to bring to the client.
The first measurement is always the most useful one, even when it is rough. Write down the query count, the page weight and the time to first byte before you change anything. Without those numbers you cannot tell an improvement from a coincidence, and three weeks later nobody will remember what the site felt like before you touched it.






Maya Okafor Mar 17, 2026
Tried this on a client site this morning. The query count dropped straight away.
Felix Moreau Aug 05, 2026
Sending this to a colleague who is about to start a migration next week.
Aisha Khan Oct 14, 2026
We hit the same thing last spring and blamed the host for a month. Wish I had read this then.
Noah Bennett Apr 09, 2026
I disagree slightly on the rollback plan, but the rest matches what we do.
Omar Haddad May 26, 2026
Could you share the checklist as a plain text file? I would like to adapt it.
Ines Costa May 03, 2026
Thanks for showing the failed attempts as well. That is the useful part.
Lena Fischer Jun 19, 2026
We do something similar with WP-CLI in our deploy step and it has been solid.
Maya Okafor Jul 12, 2026
The point about small diffs is the one I keep having to repeat at work.
Grace Tanaka Aug 28, 2026
Nice. One small correction: that hook fires earlier than the post suggests.
Grace Tanaka Sep 21, 2026
This saved me an afternoon. The bit about testing the cold path first is going on the team wiki.