Uninstall and cleanup hooks in Wordpress - Performance & Optimization

Performance: Uninstall and cleanup hooks

MEDIUM IMPACT

This affects page load speed and backend performance by ensuring no leftover data or processes slow down the site after plugin removal.

Removing a plugin and cleaning up its data

Wordpress

<?php
register_uninstall_hook(__FILE__, 'my_plugin_uninstall');
function my_plugin_uninstall() {
  delete_option('my_plugin_option');
  global $wpdb;
  $wpdb->query("DROP TABLE IF EXISTS {$wpdb->prefix}my_plugin_table");
}
?>

Removes all plugin data on uninstall, keeping database lean and queries fast.

📈 Performance GainReduces database bloat, improves query speed, helps faster LCP

Removing a plugin and cleaning up its data

Wordpress

<?php
// No uninstall hook, data remains in database
// Plugin deactivated but options and custom tables remain
?>

Leftover data causes larger database size and slower queries, impacting site load speed.

📉 Performance CostIncreases database size, slows queries, indirectly delays LCP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No uninstall cleanup	No change	0	0	[X] Bad
Proper uninstall hook cleanup	No change	0	0	[OK] Good

Rendering Pipeline

Uninstall hooks run during plugin removal and do not directly affect frontend rendering but impact backend database size and query speed, which influence page load times.

→Database Query

→Backend Processing

→Initial Page Load

⚠️ BottleneckDatabase Query

Core Web Vital Affected

LCP

This affects page load speed and backend performance by ensuring no leftover data or processes slow down the site after plugin removal.

Optimization Tips

1Always register uninstall hooks to remove plugin data.

2Deleting options and custom tables reduces database bloat.

3Smaller databases improve backend response and page load speed.

Performance Quiz - 3 Questions

What is the main performance benefit of using uninstall hooks in WordPress plugins?

A Adding extra CSS for better styling

B Removing leftover data to keep database queries fast

C Loading scripts asynchronously

D Caching plugin files on the server

DevTools: Network and Performance

How to check: Use Network panel to check backend response times before and after uninstall; use Performance panel to measure page load speed improvements.

What to look for: Look for reduced backend response time and faster LCP after uninstall cleanup.

Practice

1. What is the main purpose of using register_uninstall_hook in a WordPress plugin?

easy

A. To register a new shortcode for the plugin

B. To add a settings page in the admin dashboard

C. To clean up plugin data when the plugin is deleted

D. To enqueue scripts and styles for the plugin

Solution

1. Step 1: Understand the role of uninstall hooks

   Uninstall hooks are designed to remove all plugin data when the plugin is deleted to keep the site clean.

2. Step 2: Identify the function of register_uninstall_hook

   This function links a cleanup function that runs on plugin deletion to remove options, transients, and custom tables.

3. Final Answer:

   To clean up plugin data when the plugin is deleted -> Option C

4. Quick Check:

   Uninstall hook purpose = clean up data [OK]

Hint: Uninstall hooks remove plugin data on deletion [OK]

Common Mistakes:

• Confusing uninstall hooks with activation hooks
• Thinking uninstall hooks add features instead of cleaning
• Using uninstall hook to enqueue scripts

2. Which of the following is the correct way to register an uninstall hook in a WordPress plugin?

easy

A. register_activation_hook(__FILE__, 'my_cleanup_function');

B. add_action('uninstall_plugin', 'my_cleanup_function');

C. add_filter('uninstall_hook', 'my_cleanup_function');

D. register_uninstall_hook(__FILE__, 'my_cleanup_function');

Solution

1. Step 1: Recall the correct function for uninstall hooks

   The correct function to register an uninstall hook is register_uninstall_hook with the plugin file and cleanup function.

2. Step 2: Check the syntax of each option

   register_uninstall_hook(__FILE__, 'my_cleanup_function'); uses the correct function and parameters. Options A, B, and D use incorrect functions or hooks.

3. Final Answer:

   register_uninstall_hook(__FILE__, 'my_cleanup_function'); -> Option D

4. Quick Check:

   Correct uninstall hook syntax = register_uninstall_hook(__FILE__, 'my_cleanup_function'); [OK]

Hint: Use register_uninstall_hook with __FILE__ and function name [OK]

Common Mistakes:

• Using activation hook instead of uninstall hook
• Using add_action with wrong hook name
• Confusing filters with hooks

3. Consider this uninstall function in a plugin:

function cleanup_plugin() {
  delete_option('plugin_setting');
  delete_transient('plugin_cache');
  global $wpdb;
  $wpdb->query("DROP TABLE IF EXISTS {$wpdb->prefix}plugin_data");
}

What will happen when the plugin is uninstalled?

medium

A. All plugin data including options, transients, and custom tables will be removed

B. Only the option 'plugin_setting' will be deleted

C. The transient 'plugin_cache' will be deleted but the table remains

D. Nothing will be deleted because uninstall hooks do not run functions

Solution

1. Step 1: Analyze the cleanup function actions

   The function deletes an option, a transient, and drops a custom database table using SQL.

2. Step 2: Understand uninstall hook behavior

   When the uninstall hook calls this function, all these cleanup actions will run, removing all plugin data.

3. Final Answer:

   All plugin data including options, transients, and custom tables will be removed -> Option A

4. Quick Check:

   Cleanup function deletes all data = All plugin data including options, transients, and custom tables will be removed [OK]

Hint: Cleanup function removes all data types explicitly [OK]

Common Mistakes:

• Assuming uninstall hooks do not run cleanup functions
• Thinking only options or transients are deleted
• Ignoring the SQL DROP TABLE command

4. Identify the error in this uninstall hook registration:

register_uninstall_hook('my-plugin/my-plugin.php', 'cleanup_plugin');

function cleanup_plugin() {
  delete_option('my_plugin_option');
}

medium

A. The plugin file path should use __FILE__ instead of a string

B. The cleanup function name must be prefixed with 'uninstall_'

C. delete_option cannot be used in uninstall functions

D. The uninstall hook must be registered inside the cleanup function

Solution

1. Step 1: Check the first parameter of register_uninstall_hook

   The first parameter should be the plugin main file path, usually passed as __FILE__ for reliability.

2. Step 2: Understand why using a string path is problematic

   Using a string path can cause the hook not to trigger if the path is incorrect or changes; __FILE__ ensures correct reference.

3. Final Answer:

   The plugin file path should use __FILE__ instead of a string -> Option A

4. Quick Check:

   Use __FILE__ for plugin path in uninstall hook [OK]

Hint: Always use __FILE__ for plugin path in uninstall hook [OK]

Common Mistakes:

• Using string path instead of __FILE__
• Thinking function name must have uninstall prefix
• Registering hook inside cleanup function

5. You want to ensure your plugin cleans up all its data on uninstall, including options, transients, and a custom table named wp_custom_data. Which of the following uninstall functions correctly performs this cleanup?

hard

A. function uninstall_plugin() {
delete_option('plugin_option');
delete_transient('plugin_transient');
global $wpdb;
$wpdb->query("DROP TABLE wp_custom_data");
}

B. function uninstall_plugin() {
delete_option('plugin_option');
delete_transient('plugin_transient');
global $wpdb;
$wpdb->query("DROP TABLE IF EXISTS wp_custom_data");
}

C. function uninstall_plugin() {
delete_option('plugin_option');
delete_transient('plugin_transient');
global $wpdb;
$wpdb->query("DELETE FROM wp_custom_data");
}

D. function uninstall_plugin() {
delete_option('plugin_option');
delete_transient('plugin_transient');
}

Solution

1. Step 1: Review each cleanup action

   function uninstall_plugin() { delete_option('plugin_option'); delete_transient('plugin_transient'); global $wpdb; $wpdb->query("DROP TABLE IF EXISTS wp_custom_data"); } deletes the option, transient, and drops the custom table safely using IF EXISTS.

2. Step 2: Compare with other options

   function uninstall_plugin() { delete_option('plugin_option'); delete_transient('plugin_transient'); global $wpdb; $wpdb->query("DROP TABLE wp_custom_data"); } drops table without IF EXISTS (may cause error if table missing). function uninstall_plugin() { delete_option('plugin_option'); delete_transient('plugin_transient'); global $wpdb; $wpdb->query("DELETE FROM wp_custom_data"); } deletes rows but not table. function uninstall_plugin() { delete_option('plugin_option'); delete_transient('plugin_transient'); } misses table cleanup.

3. Final Answer:

   function uninstall_plugin() { delete_option('plugin_option'); delete_transient('plugin_transient'); global $wpdb; $wpdb->query("DROP TABLE IF EXISTS wp_custom_data"); } -> Option B

4. Quick Check:

   Safe drop table + delete option and transient = function uninstall_plugin() { delete_option('plugin_option'); delete_transient('plugin_transient'); global $wpdb; $wpdb->query("DROP TABLE IF EXISTS wp_custom_data"); } [OK]

Hint: Use DROP TABLE IF EXISTS to safely remove custom tables [OK]

Common Mistakes:

• Dropping table without IF EXISTS causing errors
• Deleting rows instead of dropping table
• Forgetting to remove custom tables