Query optimization in Wordpress - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does WP_Query cache results?

When you run a WP_Query in WordPress, how does it optimize repeated queries to the database?

A It runs the query every time without caching to ensure fresh data.

B It saves the results in a temporary file on the server to speed up future queries.

C It stores the query results in the object cache to reuse them if the same query runs again.

D It caches the SQL query string but not the results.

💡 Hint

Think about how WordPress avoids hitting the database multiple times for the same data.

WP_Query uses the WordPress object cache to store query results. This means if the same query runs again, WordPress can return cached results without querying the database again, improving performance.

📝 Syntax

intermediate

Correct way to limit posts in WP_Query

Which WP_Query argument correctly limits the number of posts returned to 5?

A { 'posts_per_page': 5 }

B { 'limit': 5 }

C { 'max_posts': 5 }

D { 'count': 5 }

💡 Hint

Look for the official WP_Query parameter that controls how many posts to fetch.

The correct parameter to limit posts in WP_Query is posts_per_page. Other options are not recognized and will be ignored.

🔧 Debug

advanced

Why does this WP_Query run slowly?

This WP_Query runs very slowly on a large site. What is the main cause?

Wordpress

new WP_Query(['meta_key' => 'color', 'meta_value' => 'blue']);

A Querying by meta_key and meta_value causes a slow meta table join without indexes.

B The query is missing a 'posts_per_page' limit, so it fetches all posts.

C WP_Query does not support meta queries, causing fallback to slow queries.

D The 'meta_value' should be 'meta_compare' to work correctly.

💡 Hint

Think about how WordPress stores custom fields and how that affects query speed.

Querying posts by meta_key and meta_value can be slow because it requires joining the postmeta table, which can be large and unindexed. This slows down the query on big sites.

🧠 Conceptual

advanced

Best practice to optimize complex WP_Query with taxonomies

You want to query posts filtered by multiple taxonomies efficiently. Which approach optimizes performance best?

A Run separate WP_Query calls for each taxonomy and merge results in PHP.

B Use 'tax_query' with multiple taxonomy filters combined with 'relation' => 'AND'.

C Use meta queries instead of taxonomies for better speed.

D Query all posts and filter taxonomies in PHP after fetching.

💡 Hint

Think about how WordPress builds SQL for taxonomies and how to combine filters efficiently.

Using 'tax_query' with multiple taxonomy filters and 'relation' => 'AND' lets WordPress build a single optimized SQL query. Running multiple queries or filtering in PHP is slower.

❓ state_output

expert

What is the number of posts returned by this WP_Query?

Consider this code snippet:

$query = new WP_Query(['posts_per_page' => 3, 'paged' => 2]);
$count = $query->post_count;

What is the value of $count if the site has 7 posts total?

Wordpress

$query = new WP_Query(['posts_per_page' => 3, 'paged' => 2]);
$count = $query->post_count;

A 7

B 4

C 1

D 3

💡 Hint

Think about how pagination works and how many posts appear on the second page.

With 7 posts total and 3 posts per page, page 1 has posts 1-3, page 2 has posts 4-6 (3 posts), and page 3 has post 7. Since 'paged' is 2, it returns 3 posts, so $count is 3.