4 ms·
Interesting, but somehow missing a point for me. You can have quite fast WordPress pages without rolling out this big of a tech stack. It all comes down to a g
by martin_a 8y ago
Interesting, but somehow missing a point for me. You can have quite fast WordPress pages without rolling out this big of a tech stack.
It all comes down to a good theme (most themes are not good) and utilizing a little bit of tech, most of which is already integrated into WP.
For example, I love the Transients API. You can easily cache database calls for posts with the Transients API and save lots of lookup/query time for complex datasets. One could argue that the Transients API is not meant to be used this way but I've build large sites which run fine (and fast) with that.
In the end it comes down to making smart choices: No tracking, few dependencies, minify all your assets, use browser caching, use scaled images, the whole toolset of good practices.
This will get you fast WordPress pages without worrying much about the tech stack you have to build around it.
- chungleong 8y agoThe setup is more useful in a mobile situation, where latency is high and connectivity isn't so certain. Imagine you're travelling by metro and reading something on your phone.
- martin_a 8y agoThat doesn't make sense. You have to deliver the whole markup and assets in one way or another. Keep it small so it gets transfered quickly, even on a slow connection. Once it has been transferred, you're done.