Die Leute bei codeable.io haben sich noch einmal das Thema ›Kosten einer Website mit WordPress‹ vorgeknöpft. Nach dem Beitrag von 2015, den ich hier teilweise übersetzt hatte, gibt es nun eine übersichtliche Infografik.

Auch wenn die Preise in US-Dollar angegeben sind – einen Orientierungshilfe und/oder Verhandlungsgrundlage können sie allemal bieten.

WordPress pricing debunked: how much does a WordPress website cost? How much for an e-commerce based on WordPress?

My colleague Lucy Beer recently discussed caching plugins on WPwatercooler. I took two favorite quotes from the show:

Lucy: “You should actually delete [that other caching plugin], because it doesn’t remove stuff when you just deactivate.”
Chris Lema: “It’s like Pastrami sitting there in the corner…”

…and, of course, this one which I hope goes viral. 🙂

No, do not add multiple caching plugins to your website!

The general issue with many so called “multi-purpose” themes from the performance point of view is that, by design, they focus on flexibility first.

A multi-purpose theme usually would be created and marketed with one single promise: to enable people who don’t necessarily know how to build a website to build a website.
Thus, flexibility and usability for the “builder” always come first. Accessibility and performance for the actual website visitor come second, or third—even if some of those themes provide their own “performance” features.

Caching plugins can make a page generated by a multi-purpose theme faster, but they can only do so much. Loading times will improve relative to size and speed of the non-optimized page.

For example, if a page would take 6 seconds to load without any optimization, a caching plugin may improve that by 100%, or even more. Yet, with a 100% improvement said page would still take 3 seconds to load—and no caching plugin could do anything about that.