All from one system really helps serious developers on the WordPress CMS.

I would like to better understand the rationale behind autoload loading this option. Is it essential for it to load with every request? Is there a possibility to reduce its autoload or load it more selectively?

Looking forward to your response. Thanks.

One of the issues I had was the user experience, did not seem to improve, much, unless browser caching was on.

Seems very comprehensive, but our host provider does also have it on the backend, so that may help.

One thing I miss is a status page, With WP Rocket it would tell you how many pages had been optimised and how many pending.

After database optimization warning started to appear at theme customization page. I used auto marked DataBase options. Ataching error message:
https://www.awesomescreenshot.com/image/33888615?key=1566d1992f5e67f0c30c06a09caa69b8

and the code lines from template.php

if ( 'private' === $post->post_status && 'private' !== $post_status ) {
		$post_states['private'] = _x( 'Private', 'post status' );
	}

	if ( 'draft' === $post->post_status ) {
		if ( get_post_meta( $post->ID, '_customize_changeset_uuid', true ) ) {
			$post_states[] = __( 'Customization Draft' );
		} elseif ( 'draft' !== $post_status ) {
			$post_states['draft'] = _x( 'Draft', 'post status' );
		}
	} elseif ( 'trash' === $post->post_status && get_post_meta( $post->ID, '_customize_changeset_uuid', true ) ) {
		$post_states[] = _x( 'Customization Draft', 'post status' );
	}

	if ( 'pending' === $post->post_status && 'pending' !== $post_status ) {
		$post_states['pending'] = _x( 'Pending', 'post status' );
	}

	if ( is_sticky( $post->ID ) ) {
		$post_states['sticky'] = _x( 'Sticky', 'post status' );
	}

	if ( 'future' === $post->post_status ) {
		$post_states['scheduled'] = _x( 'Scheduled', 'post status' );
	}

	if ( 'page' === get_option( 'show_on_front' ) ) {
		if ( (int) get_option( 'page_on_front' ) === $post->ID ) {
			$post_states['page_on_front'] = _x( 'Front Page', 'page label' );
		}

		if ( (int) get_option( 'page_for_posts' ) === $post->ID ) {
			$post_states['page_for_posts'] = _x( 'Posts Page', 'page label' );
		}
	}

	if ( (int) get_option( 'wp_page_for_privacy_policy' ) === $post->ID ) {
		$post_states['page_for_privacy_policy'] = _x( 'Privacy Policy Page', 'page label' );
	}

We have content going back to 2014 and our media storage is approaching 1TB.

Was wondering if there was a way to safely reduce and maybe archive our content, but still have it available?

Maybe a way to find all media files not being used in content, or duplicates where the duplicates are not being used?

Thoughts?

Terry