It could be CPU throttling or also running out of apache workers to handle the requests (see it happen a lot with keep-alive enabled where the request has to wait for an existing connection to close).
You can look at the apache stats to see the state of the workers (assuming you are running apache). Configuring apache to handle a large number of persistent connections can be a pain.
Thanks for that. The site is running on what I suspect is an overloaded shared hosting box. It’s running LiteSpeed. My suggestion is they move the site to a less crowded server - sounds like that could help significantly.
Thanks,
Alastair.[hr]
Is there an easy way, from these results, to calculate Render/Full Load delays caused solely by TTFB?
The static files all have long TTFB’s on them so it’s highly unlikely to be a problem where flushing would help. It’s very much a server tuning/overload problem (at least that’s what it looks like from the outside). Could be the web server or the filesystem but it should be able to turn around static files off of disk in the same amount of time as a socket connect.