logoalt Hacker News

Tade0today at 1:33 PM5 repliesview on HN

Pitch this to whoever is in charge of performance at Wordpress.

A Wordpress instance will happily take over 20 seconds to fully load if you disable cache.


Replies

rectangtoday at 5:26 PM

Are you talking about a new, empty WordPress instance running the default theme? Because if so, that doesn't match my anecdotal experience.

If you're talking about a WordPress instance with arbitrary plugins running an arbitrary theme, then sure — but that's an observation about those plugins and themes, not core.

As someone who has to work with WordPress, I have all kinds of issues with it, but "20 seconds to load core with caching disabled" isn't one of them.

show 1 reply
embedding-shapetoday at 1:46 PM

Microbenchmarks are very different from optimizing performance in real applications in wide use though, they could do great on this specific benchmark but still have no clue about how to actually make something large like Wordpress to perform OK out of the box.

tracker1today at 6:19 PM

Wordpress is something that I cannot believe hasn't been displaced by a service that uses a separate application for editing and delivery.

It seems like something like vercel/cloudflare could host the content-side published as a worker for mostly-static content from a larger application and that would be more beneficial and run better with less risk, for that matter. Having the app editing and auth served from the same location is just begging for the issues WP and plugins have seen.

show 1 reply
rkozik1989today at 4:39 PM

Much like anything else your performance is going to vary a lot based on architecture of implementation. You really shouldn't deploying anything into production without some kind of caching. Whether that's done in the application itself or with memcached/redis or varnish or OPcache.

show 2 replies
monkey_monkeytoday at 2:34 PM

That's often a skill issue.

show 1 reply