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.

Practice

1. What is the main benefit of optimizing queries in WordPress using WP_Query?

easy

A. It reduces server load and speeds up page loading.

B. It automatically fixes broken links on the site.

C. It changes the website's theme dynamically.

D. It increases the number of posts displayed without limits.

Solution

1. Step 1: Understand query optimization purpose

   Query optimization aims to fetch only necessary data to reduce processing time.

2. Step 2: Connect optimization to performance

   By limiting data fetched, server load decreases and pages load faster.

3. Final Answer:

   It reduces server load and speeds up page loading. -> Option A

4. Quick Check:

   Query optimization = faster site [OK]

Hint: Optimized queries fetch less data, making pages load faster [OK]

Common Mistakes:

• Thinking optimization changes site design
• Believing it fixes unrelated issues like broken links
• Assuming optimization increases data fetched

2. Which of the following is the correct way to limit posts to 5 using WP_Query?

easy

A. new WP_Query(array('count' => 5));

B. new WP_Query(array('limit' => 5));

C. new WP_Query(array('max_posts' => 5));

D. new WP_Query(array('posts_per_page' => 5));

Solution

1. Step 1: Recall WP_Query parameter for limiting posts

   The correct parameter to limit posts is 'posts_per_page'.

2. Step 2: Match parameter with correct syntax

   new WP_Query(array('posts_per_page' => 5)); uses 'posts_per_page' correctly with value 5.

3. Final Answer:

   new WP_Query(array('posts_per_page' => 5)); -> Option D

4. Quick Check:

   Limit posts = posts_per_page [OK]

Hint: Use 'posts_per_page' to limit posts in WP_Query [OK]

Common Mistakes:

• Using incorrect parameter names like 'limit' or 'count'
• Confusing 'posts_per_page' with other parameters
• Missing array syntax in WP_Query

3. What will be the effect of this query?

 $query = new WP_Query(array('category_name' => 'news', 'posts_per_page' => 3)); 

medium

A. Fetches all posts from all categories.

B. Fetches 3 posts from any category except 'news'.

C. Fetches 3 posts only from the 'news' category.

D. Fetches posts but ignores the category filter.

Solution

1. Step 1: Analyze the category filter

   The parameter 'category_name' => 'news' limits posts to the 'news' category.

2. Step 2: Analyze the posts_per_page limit

   'posts_per_page' => 3 limits the number of posts fetched to 3.

3. Final Answer:

   Fetches 3 posts only from the 'news' category. -> Option C

4. Quick Check:

   Category + limit = 3 news posts [OK]

Hint: Category filter + posts_per_page limits results [OK]

Common Mistakes:

• Ignoring category filter effect
• Assuming all categories are fetched
• Confusing posts_per_page with total posts

4. Identify the error in this WP_Query code snippet:

 $args = array('post_per_page' => 10, 'category_name' => 'updates'); $query = new WP_Query($args); 

medium

A. The 'category' parameter should be 'category_name'.

B. The parameter 'post_per_page' is misspelled; should be 'posts_per_page'.

C. WP_Query cannot accept arrays as arguments.

D. There is no error; the code is correct.

Solution

1. Step 1: Check parameter names for limiting posts

   The correct parameter is 'posts_per_page', not 'post_per_page'.

2. Step 2: Verify category parameter

   The parameter 'category_name' => 'updates' uses the correct syntax for category slug.

3. Final Answer:

   The parameter 'post_per_page' is misspelled; should be 'posts_per_page'. -> Option B

4. Quick Check:

   Correct parameter spelling = posts_per_page [OK]

Hint: Check spelling of WP_Query parameters carefully [OK]

Common Mistakes:

• Using 'post_per_page' instead of 'posts_per_page'
• Confusing 'category' with 'category_name'
• Assuming WP_Query doesn't accept arrays

5. You want to optimize a query to fetch only published posts from the 'events' category, limited to 4 posts, ordered by date descending. Which is the best WP_Query argument array?

hard

A. {'category_name' => 'events', 'posts_per_page' => 4, 'post_status' => 'publish', 'orderby' => 'date', 'order' => 'DESC'}

B. {'category' => 'events', 'limit' => 4, 'status' => 'published', 'order_by' => 'date', 'order' => 'desc'}

C. {'cat_name' => 'events', 'posts_per_page' => 4, 'post_status' => 'publish', 'orderby' => 'date', 'order' => 'ASC'}

D. {'category_name' => 'events', 'posts_per_page' => 10, 'post_status' => 'publish', 'orderby' => 'title', 'order' => 'DESC'}

Solution

1. Step 1: Identify correct category parameter

   'category_name' is the correct parameter to filter by category slug.

2. Step 2: Check post limit and status

   'posts_per_page' => 4 limits posts; 'post_status' => 'publish' fetches only published posts.

3. Step 3: Verify ordering parameters

   'orderby' => 'date' and 'order' => 'DESC' correctly order posts by newest first.

4. Final Answer:

   {'category_name' => 'events', 'posts_per_page' => 4, 'post_status' => 'publish', 'orderby' => 'date', 'order' => 'DESC'} -> Option A

5. Quick Check:

   Correct params + limit + order = {'category_name' => 'events', 'posts_per_page' => 4, 'post_status' => 'publish', 'orderby' => 'date', 'order' => 'DESC'} [OK]

Hint: Use exact WP_Query keys: category_name, posts_per_page, post_status, orderby [OK]

Common Mistakes:

• Using wrong parameter names like 'category' or 'limit'
• Mixing 'order' case sensitivity
• Setting wrong order direction or post status