Critical CSS for small teams

The version of this that works is simpler than the version most people imagine. Most advice about critical CSS assumes a team that does not exist at your size. Here is the version that does not.

Speed is a feature people notice only in its absence, and then they leave rather than complain. If two people in the business would answer this differently, that gap is the actual problem.

What to keep

Inlining what is needed first shortens time to first paint. Where this goes wrong is almost never a lack of knowledge. Doing this properly once is usually cheaper than doing it approximately three times.

What to drop

Process that exists to coordinate ten people is overhead when there are two of you. There is a version of this that is over-engineered, and it is worth avoiding.

What good looks like

Only worth the complexity on high-traffic pages. The reasoning matters more than the rule, because the rule has exceptions. It rarely shows up as a line item, which is exactly why it slips.

The short version

Real-world numbers from actual visitors matter more than a score produced on a fast laptop. Three things worth confirming about critical CSS before you move on:

• Someone can say what the current setup is without going to look
• Only worth the complexity on high-traffic pages — and you know whether that is true here
• There is a way to tell whether the last change to this helped

The point is not perfection, it is knowing which of these you have consciously chosen to skip.