Support » Fixing WordPress » Performance issues with too many static pages

  • We’re attempting to use WordPress as a CMS for a website of ours which has 2000+ static pages outside the blog and news areas. We’ve ported these all in as Pages and found the performance of many areas of the site (editing pages, permalink control panel, and simply viewing a page) has decreased SIGNIFICANTLY (upwards of 20-30 seconds to load a page). Are there plugins we should be using or patches for handling higher volume Pages? We’ve actually rewritten a few of the function calls we found to be extremely inefficient, but there is still more work to be done.

    Any information would be appreciated.


Viewing 8 replies - 1 through 8 (of 8 total)
  • Moderator Samuel Wood (Otto)

    (@otto42) Admin

    WordPress is not written to support vast amounts of Pages. Pages are sort of an add-on. The average site doesn’t have more than a couple dozen or so.

    So if all you need is that, then you should look into an alternative system to deal with those. Perhaps a wiki or something similar. There are plugins and hacks for WordPress that will let you do it, but why use a piece of software not designed for your goals? Re-evaluate your goals and choose the right piece of software for it. If you then want to tie it to WordPress for the blog aspects, then you can do that.

    WordPress handles thousands of posts just fine- why the design shortcomings in the pages mechanism? I’d use them as posts, but this introduces a slew of issues (e.g. like filenames from different categories).

    Moderator Samuel Wood (Otto)

    (@otto42) Admin

    Internally, Pages are just Posts with a special type. However, Pages have a different mechanism for URL handling and display (Pages are hierarchical, Posts are not). This is enough to make them not scale as well as Posts do.

    Admittedly, there’s a lot of really inefficient code surrounding Pages, but since most people don’t use many of them, there’s never been much reason to optimize for that use case.

    I have a similar issue… but in my case I only have 60 or 70 pages.

    Just to load the home page it takes 2947 queries = 4.465 seconds.

    The only solution that appears to work is to use Super Cache but it sucks to know that WordPress can’t scale on this area and as Otto’s comments it looks like there is no plan for the Core Dev Team to fix it in the short term.

    It looks like it was fixed with the latest version (2.8.2).

    Can someone else confirm it?

    It wasn’t… I still have the problem.

    2.8.5 still the same problem…

    I would be interested in a better separation in the permalink setup for pages and posts. A simple /content/ or /static/ as keyword for the pages would do the trick!


    I am a huge WordPress fan but I have to be honest when I encountered some of these problems described above it made me extremely disappointed in WP.

    I used to be one of those people that would always say “WP is a great solution for a CMS” etc etc as so many people have been saying recently but honestly this page load time issue is pretty pathetic if WP wants to market itself as not just blog software but as anything remotely approaching a full CMS.

    If anyone could come up with a solution to this problem I would be happy to pay (although from what I have read a plugin won’t be able to do the trick since this is a major problem with the WP core itself). Anyone have any ideas?

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Performance issues with too many static pages’ is closed to new replies.