Welcome to ManageWP.org

Register to share, discuss and vote for the best WordPress stories every day, find new ideas and inspiration for your business and network with other members of the WordPress community. Join the #1 WordPress news community!

×

3 min read Brian Jackson
Community | learnwp.io | Jun. 1, 2015

Beware the 100 Page WordPress Limitation - Learn WP

Make sure you think twice before launching a bunch of pages in WordPress as it can bring your backend to a crawl. There is a huge difference between how pages and posts are handled that some people don't realize. Except for maybe WP developers :) Please use custom post types!

Beware the 100 Page WordPress Limitation - Learn WP

Community | learnwp.io | Jun. 1, 2015

If you are having performance issues on the backend (in your dashboard) you might want to check on how many pages you currently have. WordPress was not meant for over 100 pages as it will start running into memory issues. This won’t affect the front end load times, but you will want to start banging your head against your desk. I had a client recently with a little over 1,000 pages and it brought WordPress to a crawl. And yes they are on a high-end VPS. It doesn’t have to do with the server, but rather how WordPress is structured. WordPress Mentions This Limitation In Their Documentation
Note: this parameter was planned for Pages. Be careful, when choosing it for your custom post type – if you are planning to have many entries (say – over 100), you will run into memory issue. With this parameter set to true WordPress will fetch all entries of that particular post type, together with all meta data, on each administration page load for your post type. Src: Function Reference/register post type
And in layman’s terms…
Pages have a hierarchy tree. So in the WP dashboard, anything to do with a page ends up having to load the entire page hierarchy tree to distinguish how that page relates