A WordPress checkout can hit PHP memory or concurrency limits while its monthly traffic allowance still has room.

That is the sizing problem I want answered before I compare Kinsta prices. Monthly traffic tells me how much activity a configuration allows over a billing period. It does not tell me how many requests it can process at the same time.

Concurrency is that second thing. Requests being processed simultaneously.

I want one number to settle the hosting decision. Nice, tidy, probably wrong.

For a checkout or membership workload, I would ask Kinsta to size the dynamic workload rather than infer capacity from a visits column.…