If you put in the URL alone to test you get 67 ms.
I understand that multiple things can be affecting it, but just curious on your thoughts on how to improve the time to first byte for static content when requesting a page with a lot of static content.
Any savings off of the base page will go directly towards the load time and to improving your server utilization so faster is always better but you have to see if it is worth the effort. Depending on the application you can get those times to be almost as fast as static content but it takes quite a bit of effort and dedicated servers to have full control over it.
Eliminating network latency, I have my average response time for dynamic content running ~10-15ms but that’s on a dedicated server with Nginx+PHP-FPM+APC, gobs of RAM and SSD storage.
Thanks. So a quick recap to identifying TTFB and trying to optimize it.
Look at results and see which request has a high TTFB respectively.
Dynamic content - 200ms-500ms
Static content - under 100 ms
Apply the rules to try to optimize the TTFB:
If your TTFB for static content is high, then you may have reached the hardware/configuration limits of your server.
If your TTFB for your static content is low but dynamic content is high, then your application or server configuration may be to blame.
If you find a server with little load and fast static content but slow dynamic content, configuration changes to Apache/IIS/etc., MySQL/SQL/tc. and PHP/etc. may help. If these configuration changes do not help, then the bottleneck may be in the code itself. In this case, you may need to consider profiling your application.
Let me know your thoughts on the resolving slow TTFB issues.