It is actually using curl at the moment to retrieve and store the feeds locally. There's an element of slowdown somewhere in the parse/cache process that I'm trying to nail.

Everything will eventually be stored in a database and access from there. That's further down the line. This is really only a proof of concept at the moment. The whole thing will eventually be ajax-ified.