Today we received an email along the lines of :
“Help! A customer’s website is slow and they’re complaining it’s taking over 2 seconds to load!”
Starting with just inspecting a page load in Chrome showed that the rendering of the PHP side of the page was a main bottleneck (taking between 1.5 and 3 seconds).
A quick rummage and analysis through Xdebug‘s profiler showed each request to the home page was dependent on a curl/http connection.
-
xdebug output – note the big blue box
Further investigation took us to mod_jmtwitterroll to which we added some crude caching – to stop each request to the site was being dependent on twitter’s response time.