A practical checklist for time to first byte

The advice here is unglamorous, which is probably why it gets skipped. Run through this the next time time to first byte comes up.

Performance work is mostly subtraction, which makes it unpopular and effective. It is the sort of thing that looks like polish right up until it costs you an enquiry.

The checklist

• Slow server response caps how fast the page can ever be
• Caching at the edge often fixes it outright
• Cheap shared hosting shows up here first
• Someone is named as the owner
• There is a date to review it again

What is actually at stake

Slow server response caps how fast the page can ever be. The reasoning matters more than the rule, because the rule has exceptions. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.

What this looks like day to day

Speed is a feature people notice only in its absence, and then they leave rather than complain. Three things worth confirming about time to first byte before you move on:

• Someone can say what the current setup is without going to look
• Caching at the edge often fixes it outright — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If you want a second opinion on how yours is set up, ask.