Site health checks are a filter, so you can add your own

5.2 shipped a screen that reports on the installation, and the useful part is that the list of checks is filterable — so a site can test the things only it cares about.

add_filter( 'site_status_tests', function ( $tests ) {
    $tests['direct']['turkerdev_queue'] = array(
        'label' => __( 'Queue worker', 'turkerdev' ),
        'test'  => function () {
            $stale = get_option( 'turkerdev_last_job_at' ) < time() - 600;

            return array(
                'label'       => $stale ? __( 'Queue is stalled', 'turkerdev' )
                                        : __( 'Queue is running', 'turkerdev' ),
                'status'      => $stale ? 'critical' : 'good',
                'badge'       => array( 'label' => __( 'Performance', 'turkerdev' ), 'color' => 'blue' ),
                'description' => '<p>' . esc_html__( 'No job has completed in ten minutes.', 'turkerdev' ) . '</p>',
                'test'        => 'turkerdev_queue',
            );
        },
    );

    return $tests;
} );

The direct group runs during the page load and the async group runs over the REST API afterwards, so anything slow belongs in the second one or the screen takes ten seconds. The status values are good, recommended and critical, and using critical for something that is merely untidy is how the screen becomes noise. It is the first thing WordPress has ever shipped that reports on itself, which is worth more than any individual check.