Yet another time to first byte question

[pmeenan]

Are you running the main site through the cdn (http://www.headfonia.com) or do you have a separate domain for the static content that is being routed through the CDN? It's possible that the CDN is adding to the first byte times for the non-cacheable HTML. If not then you should turn on the W3TC debugging because those times are way longer than what I'd expect to see for a site where the page, objects and database queries are being cached by APC.

It also looks like beyond the first byte time, the rest of the base page took longer to generate than it should (looks like there was an early flush and then another 1.5 seconds before the rest of the base page was actually sent).

You might want to look into turning on logging of the server-side processing time in your access logs which will help narrow it down a bit (it will let you know if the time is coming from something in front of the server or on the processing itself).

If one.headfonia.com is the cdn then you should move the timthumb, css and js requests to the CDN as well.