Custom post type queries in Wordpress - Performance & Optimization

Performance: Custom post type queries

MEDIUM IMPACT

This affects page load speed by controlling how many database queries run and how much data is fetched for custom post types.

Fetching all posts of a custom post type without limits or caching

Wordpress

<?php $paged = get_query_var('paged') ?: 1; $query = new WP_Query(array('post_type' => 'product', 'posts_per_page' => 10, 'paged' => $paged)); if ($query->have_posts()) { while ($query->have_posts()) { $query->the_post(); the_title(); } } wp_reset_postdata(); ?>

Limits posts per page and uses pagination to reduce query size and memory use.

📈 Performance Gainsingle DB query per page, reduces blocking to under 50 ms

Fetching all posts of a custom post type without limits or caching

Wordpress

<?php $posts = get_posts(array('post_type' => 'product')); foreach ($posts as $post) { setup_postdata($post); the_title(); } wp_reset_postdata(); ?>

This fetches all posts at once, causing heavy database load and slow page rendering.

📉 Performance Costblocks rendering for 200+ ms on large datasets, triggers multiple DB queries

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Fetching all posts without limits	N/A (server-side)	N/A	Blocks initial paint due to slow HTML generation	[X] Bad
Paginated query with limits	N/A (server-side)	N/A	Faster HTML generation enables quicker paint	[OK] Good
Query without caching	N/A (server-side)	N/A	Slower server response delays paint	[!] OK
Query with caching	N/A (server-side)	N/A	Fast server response improves paint timing	[OK] Good

Rendering Pipeline

Custom post type queries run on the server to fetch data before HTML is generated. Inefficient queries delay HTML generation, blocking the browser from starting rendering.

→Server Processing

→HTML Generation

→First Paint

⚠️ BottleneckServer Processing due to heavy or unoptimized database queries

Core Web Vital Affected

LCP

This affects page load speed by controlling how many database queries run and how much data is fetched for custom post types.

Optimization Tips

1Always limit the number of posts fetched per query to reduce server load.

2Use pagination to split large datasets into smaller chunks.

3Implement caching to avoid repeated database queries on each page load.

Performance Quiz - 3 Questions

What is a key performance benefit of limiting posts per page in a custom post type query?

A Reduces database load and speeds up server response

B Increases the number of queries to the database

C Makes the page heavier to download

D Causes more layout shifts on the page

DevTools: Network and Performance panels

How to check: Open DevTools, reload the page, check the Network panel for server response time and the Performance panel for time to first paint and contentful paint.

What to look for: Look for long server response times and delayed first contentful paint indicating slow queries.