Optimization Detective currently only applies its optimizations by default when the user is not an admin. The logic is here:

This can be easily overridden via the following, which is super helpful during development (but see #1423):

add_filter( 'od_can_optimize_response', '__return_true' );

However, it can be confusing to be required to do this. The README includes this bit:

URL metrics are not collected for administrators because it is likely that additional elements will be present on the page which are not also shown to non-administrators, meaning the URL metrics could not reliably be reused between them.

Additional elements include Customizer scripts, edit post links, and so on.

If we included admins, then we'd need to modify od_get_normalized_query_vars() as follows to vary the URL Metrics by whether the user is an admin (due to the additional elements present for admins):

--- a/plugins/optimization-detective/storage/data.php
+++ b/plugins/optimization-detective/storage/data.php
@@ -82,6 +82,10 @@ function od_get_normalized_query_vars(): array {
 		$normalized_query_vars['user_logged_in'] = true;
 	}
 
+	if ( current_user_can( 'customize' ) ) {
+		$normalized_query_vars['admin'] = true;
+	}
+
 	return $normalized_query_vars;
 }

This means that for every URL, there would potentially be separate od_url_metrics posts for:

1. Unauthenticated users.
2. Logged-in users who aren't admins.
3. Admin users.

Maybe this still isn't worthwhile to do and the existing logic is correct. But I wanted to open an issue to discuss further.