The responsiveness is slow if the server has to recompile the webpage, which takes the mentioned 10-15 seconds as there's quite a bunch of expensive templates being used (sometimes multiple times on a single page). The wiki does use parser and html caching, but as I'm currently changing a lot of things every now and then, the wiki becomes very sluggish during those updates. Whenever a webpage that uses one of the templates I edited gets loaded for the first time after the update it redoes the caching, causing a slow load time again.
I changed some templates that affect all pages (and will continue this the next days) , so this'll occur some more until it improves again. There's only so much we can do to improve this on the server end, as many of those templates just need to be as complex as they are, and there's some pretty expensive parser calls I can't avoid. Also, mediawiki has a horrible parsing speed performance by default, which obviously is impossible to overcome except by not using mediawiki and going for a different presentation form (which again would take quite some time to convert to, despite the benefits it'd provide).
Me and the webadmin do monitor this. He still fiddles with cache settings to improve performance (it's apparently quite an art), and I will revisit those expensive templates to try and make them more efficient. But to be honest this is kind of low priority compared to getting the content correct and up to date.
To get an idea of how horribly messy those templates are, just look at
Quelltext von Seite Vorlage:Infobox Panzer ansehen ? WGPWiki
That's what has to get processed for every single vehicle on the faction pages. I know where some of the biggest performance hogs come from (#ifexist), but it's difficult to work around these without the wiki getting spammed with nasty image redlinks.
tl;dr : Whenever a page is updated in some way, the server needs to re-cache it. This is done when the page is visited for the first time. Every subsequent visit to the page will prompt the server to simply provide the cached finished version it has stored instead of recompiling the entire page, which usually is completed fairly instantaneous.