Pagination with custom queries in Wordpress - Performance & Optimization

Performance: Pagination with custom queries

MEDIUM IMPACT

This affects page load speed and interaction responsiveness by controlling how much data is fetched and rendered at once.

Loading posts with pagination using custom queries

Wordpress

<?php
$paged = max(1, get_query_var('paged'));
$args = array('posts_per_page' => 10, 'paged' => $paged);
$query = new WP_Query($args);
if ($query->have_posts()) : while ($query->have_posts()) : $query->the_post();
  the_title();
endwhile; endif;
wp_reset_postdata();
?>

Limits posts per page to 10, reducing data fetched and DOM nodes, improving load and render speed.

📈 Performance GainReduces initial load by 90%+, triggers only 1 reflow per page load

Loading posts with pagination using custom queries

Wordpress

<?php
$paged = (get_query_var('paged')) ? get_query_var('paged') : 1;
$args = array('posts_per_page' => -1, 'paged' => $paged);
$query = new WP_Query($args);
if ($query->have_posts()) : while ($query->have_posts()) : $query->the_post();
  the_title();
endwhile; endif;
wp_reset_postdata();
?>

Fetching all posts at once with 'posts_per_page' set to -1 loads too many items, causing slow page load and heavy DOM.

📉 Performance CostBlocks rendering for 300+ ms on large sites, triggers many reflows due to large DOM

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Load all posts at once	High (hundreds of nodes)	Multiple reflows	High paint cost	[X] Bad
Paginate with limited posts	Low (10-20 nodes)	Single reflow	Low paint cost	[OK] Good

Rendering Pipeline

Pagination controls how many posts are queried and rendered, affecting the browser's layout and paint stages by limiting DOM size.

→Layout

→Paint

→Composite

⚠️ BottleneckLayout stage due to large DOM when too many posts are loaded

Core Web Vital Affected

LCP

This affects page load speed and interaction responsiveness by controlling how much data is fetched and rendered at once.

Optimization Tips

1Always limit posts_per_page in custom queries to a reasonable number (e.g., 10-20).

2Avoid querying all posts at once to prevent large DOM and slow rendering.

3Use pagination controls to fetch and render only needed data per page.

Performance Quiz - 3 Questions

What is the main performance benefit of limiting posts per page in a custom WordPress query?

A Makes the page load slower by adding more JavaScript

B Reduces the number of DOM nodes and speeds up page rendering

C Increases the total number of database queries

D Causes more layout shifts on the page

DevTools: Performance

How to check: Record a performance profile while loading the paginated page. Look at the Layout and Paint sections for time spent and number of reflows.

What to look for: High layout or paint times and many reflows indicate poor pagination; low times and fewer reflows indicate good pagination.

Practice

1. What is the main purpose of using the paged parameter in a custom WordPress query?

easy

A. To order posts by date

B. To filter posts by category

C. To specify which page of posts to display for pagination

D. To limit the number of posts shown on the homepage

Solution

1. Step 1: Understand the role of paged in queries

   The paged parameter tells WordPress which page number of posts to fetch, enabling pagination.

2. Step 2: Differentiate from other query parameters

   Other parameters like category or order control filtering and sorting, not pagination.

3. Final Answer:

   To specify which page of posts to display for pagination -> Option C

4. Quick Check:

   paged controls page number in pagination [OK]

Hint: Remember: paged means page number for posts [OK]

Common Mistakes:

• Confusing paged with category filters
• Using paged to limit posts per page
• Ignoring the need to reset post data after custom queries

2. Which of the following is the correct way to include the paged parameter in a custom WP_Query to enable pagination?

easy

A. "page" => 1

B. "paged" => get_query_var('paged') ? get_query_var('paged') : 1

C. "paged" => 0

D. "pagination" => true

Solution

1. Step 1: Identify correct syntax for paged

   The correct way is to get the current page number using get_query_var('paged'), defaulting to 1 if not set.

2. Step 2: Check other options for correctness

   Options A, C, and D use wrong keys or values that won't work for pagination.

3. Final Answer:

   "paged" => get_query_var('paged') ? get_query_var('paged') : 1 -> Option B

4. Quick Check:

   Use paged with get_query_var for pagination [OK]

Hint: Use get_query_var('paged') or default to 1 [OK]

Common Mistakes:

• Using page instead of paged
• Setting paged to 0 disables pagination
• Using non-existent pagination parameter

3. Given this code snippet, what will be the output if the current page is 3?

$paged = get_query_var('paged') ? get_query_var('paged') : 1;
$args = [
  'post_type' => 'post',
  'posts_per_page' => 5,
  'paged' => $paged
];
$query = new WP_Query($args);
echo $query->query_vars['paged'];

medium

A. 1

B. 5

C. 0

D. 3

Solution

1. Step 1: Understand get_query_var('paged') behavior

   If the current page is 3, get_query_var('paged') returns 3, so $paged is 3.

2. Step 2: Check what is echoed

   The code echoes $query->query_vars['paged'], which is set to 3.

3. Final Answer:

   3 -> Option D

4. Quick Check:

   Current page number echoed = 3 [OK]

Hint: Echo query_vars['paged'] to see current page [OK]

Common Mistakes:

• Assuming default page 1 always prints
• Confusing posts per page with page number
• Expecting total posts count instead of page number

4. Identify the error in this pagination code snippet:

$paged = get_query_var('paged');
$args = [
  'post_type' => 'post',
  'posts_per_page' => 10,
  'paged' => $paged
];
$query = new WP_Query($args);
// Loop here
wp_reset_query();

medium

A. Missing default value for $paged, may cause page 0

B. Using wp_reset_query() instead of wp_reset_postdata()

C. Incorrect post type specified

D. Posts per page should be set to 5 for pagination

Solution

1. Step 1: Check $paged initialization

   $paged is set directly from get_query_var('paged') without defaulting to 1, so if no page is set, it may be 0 or empty.

2. Step 2: Evaluate other parts

   While wp_reset_postdata() is preferred after custom queries, the main error affecting pagination is missing default for $paged.

3. Final Answer:

   Missing default value for $paged, may cause page 0 -> Option A

4. Quick Check:

   Always default $paged to 1 if empty [OK]

Hint: Always default $paged to 1 to avoid page 0 [OK]

Common Mistakes:

• Not setting default page number
• Confusing wp_reset_query() with wp_reset_postdata()
• Assuming posts per page must be 5

5. You want to create a paginated list of 'product' posts showing 8 per page. Which code snippet correctly sets up the custom query and pagination, including resetting post data?

hard

A. $paged = get_query_var('paged') ?: 1;
$args = [
'post_type' => 'product',
'posts_per_page' => 8,
'paged' => $paged
];
$query = new WP_Query($args);
if ($query->have_posts()) {
while ($query->have_posts()) {
$query->the_post();
the_title();
}
}
wp_reset_postdata();

B. $paged = 1;
$args = [
'post_type' => 'product',
'posts_per_page' => 8
];
$query = new WP_Query($args);
while ($query->have_posts()) {
$query->the_post();
the_title();
}
wp_reset_query();

C. $paged = get_query_var('page') ?: 1;
$args = [
'post_type' => 'product',
'posts_per_page' => 8,
'paged' => $paged
];
$query = new WP_Query($args);
while ($query->have_posts()) {
$query->the_post();
the_title();
}
wp_reset_postdata();

D. $paged = get_query_var('paged') ?: 1;
$args = [
'post_type' => 'product',
'posts_per_page' => 8,
'page' => $paged
];
$query = new WP_Query($args);
if ($query->have_posts()) {
while ($query->have_posts()) {
$query->the_post();
the_title();
}
}
wp_reset_postdata();

Solution

1. Step 1: Correctly get current page number

   Use get_query_var('paged') ?: 1 to get current page or default to 1.

2. Step 2: Set query args and reset post data

   Use 'paged' => $paged (not 'page'), and call wp_reset_postdata() after the loop.

3. Step 3: Verify loop structure

   Check that the loop uses have_posts() and the_post() correctly.

4. Final Answer:

   Code snippet D correctly sets up pagination and resets post data -> Option A

5. Quick Check:

   Use paged param and wp_reset_postdata() [OK]

Hint: Use paged param and reset post data after loop [OK]

Common Mistakes:

• Using 'page' instead of 'paged' in query args
• Not resetting post data after custom query
• Hardcoding page number to 1 disables pagination