Investigate caching.

[khipkin]

Right now, loading our calendar takes a significant amount of time. It seems silly to reload the entire thing every time a user navigates to the page.

[chrissprague]

@khipkin can we make this issue a bit more specific? Like, would this be caching in general or are we just looking to do this for the calendar?

[khipkin]

@chrissprague, not sure. It depends how easy it is to implement.

[zg]

This could be done either in Django or Apache. It'd probably be easier to do it at the HTTP server layer (Apache).

[zg]

Wait, don't we just use Google Calendar? Were we using something else when you posted this?

[khipkin]

If you mean the Google Calendar API, no we don't. We couldn't figure out how to properly authenticate to use it. Also, caching pictures would be useful, although that might happen automatically depending on the browser.

[zg]

I ran an Audit using Chrome Dev Tools and they suggest leveraging browser caching for all the images, CSS, and JS files. I think this would have to get changed in the Apache config.