{"id":395191,"date":"2026-11-11T23:43:52","date_gmt":"2026-11-11T23:43:52","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/speed-doctor-by-imzura-site-speed-check-and-performance-optimization\/"},"modified":"2026-11-14T14:10:53","modified_gmt":"2026-11-14T14:10:53","slug":"imzura-site-check","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/imzura-site-check\/","author":23595519,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.7.0","stable_tag":"1.7.0","tested":"7.1.4","requires":"6.2","requires_php":"7.4","requires_plugins":null,"header_name":"imzura Site Check \u2013 Page Speed & Core Web Vitals Optimization","header_author":"imzura.com","header_description":"Finds what slows your site down, on the front end, in the admin and in WooCommerce, and proves every fix with a measurement.","last_updated":"2026-11-14 14:10:53","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/imzura.com\/products\/site-check","header_author_uri":"https:\/\/imzura.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":272,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"imzura","date":"2026-11-11 23:43:18","revision":3797250},"1.3.0":{"tag":"1.3.0","author":"imzura","date":"2026-11-12 01:30:29","revision":3797325},"1.4.0":{"tag":"1.4.0","author":"imzura","date":"2026-11-12 03:09:43","revision":3797416},"1.5.0":{"tag":"1.5.0","author":"imzura","date":"2026-11-12 08:58:06","revision":3797865},"1.6.0":{"tag":"1.6.0","author":"imzura","date":"2026-11-14 06:07:36","revision":3801444},"1.6.1":{"tag":"1.6.1","author":"imzura","date":"2026-11-14 13:58:28","revision":3802030},"1.7.0":{"tag":"1.7.0","author":"imzura","date":"2026-11-14 14:10:53","revision":3802052}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3797250,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3797250,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3797250,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3799225,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3799225,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.3.0","1.4.0","1.5.0","1.6.0","1.6.1","1.7.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3797865,"resolution":"1","location":"assets","locale":"","width":1470,"height":2250},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3797865,"resolution":"2","location":"assets","locale":"","width":1470,"height":2250},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3797865,"resolution":"3","location":"assets","locale":"","width":1470,"height":2250},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3797865,"resolution":"4","location":"assets","locale":"","width":1470,"height":1989},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3797865,"resolution":"5","location":"assets","locale":"","width":1470,"height":1275}},"screenshots":{"1":"The check: what slows the site down on the pages visitors see, ranked, with the pages each finding was seen on.","2":"CSS &amp; JS: every fix is tried first, and kept only if nothing on the pages changed and something was saved. The numbers show what it saved.","3":"Images: pictures served at the size they are shown, and YouTube videos shown as a picture until play is pressed.","4":"Plugins: WooCommerce and Contact Form 7 files only on the pages that use them.","5":"Cache: which page cache is active, a test that opens the home page as a new visitor, and a button that clears it."}},"plugin_section":[],"plugin_tags":[187460,1513,247,794,286],"plugin_category":[45,52,54],"plugin_contributors":[292116],"plugin_business_model":[],"class_list":["post-395191","plugin","type-plugin","status-publish","hentry","plugin_tags-core-web-vitals","plugin_tags-pagespeed","plugin_tags-performance","plugin_tags-speed","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_contributors-imzura","plugin_committers-imzura"],"banners":{"banner":"https:\/\/ps.w.org\/imzura-site-check\/assets\/banner-772x250.png?rev=3799225","banner_2x":"https:\/\/ps.w.org\/imzura-site-check\/assets\/banner-1544x500.png?rev=3799225","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/imzura-site-check\/assets\/icon.svg?rev=3797250","icon":"https:\/\/ps.w.org\/imzura-site-check\/assets\/icon.svg?rev=3797250","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/imzura-site-check\/assets\/screenshot-1.png?rev=3797865","caption":"The check: what slows the site down on the pages visitors see, ranked, with the pages each finding was seen on."},{"src":"https:\/\/ps.w.org\/imzura-site-check\/assets\/screenshot-2.png?rev=3797865","caption":"CSS &amp; JS: every fix is tried first, and kept only if nothing on the pages changed and something was saved. The numbers show what it saved."},{"src":"https:\/\/ps.w.org\/imzura-site-check\/assets\/screenshot-3.png?rev=3797865","caption":"Images: pictures served at the size they are shown, and YouTube videos shown as a picture until play is pressed."},{"src":"https:\/\/ps.w.org\/imzura-site-check\/assets\/screenshot-4.png?rev=3797865","caption":"Plugins: WooCommerce and Contact Form 7 files only on the pages that use them."},{"src":"https:\/\/ps.w.org\/imzura-site-check\/assets\/screenshot-5.png?rev=3797865","caption":"Cache: which page cache is active, a test that opens the home page as a new visitor, and a button that clears it."}],"raw_content":"<!--section=description-->\n<p>A slow WordPress site usually has a few causes: a plugin that loads its files on every page, a heavy picture, a font from another server, a script that keeps the browser busy, a database that has piled up. PageSpeed Insights gives a score; this plugin names the plugin, theme or file behind each problem on your own pages, and fixes what can be fixed safely. It works next to the cache plugin you already have.<\/p>\n\n<p>This plugin does two things.<\/p>\n\n<p><strong>It checks.<\/strong> One button reads your site the way a first-time visitor gets it and tells you, in plain words, what is slowing it down: on the front end, in the admin and in WooCommerce. Checking changes nothing on the site.<\/p>\n\n<p><strong>It fixes, and proves it.<\/strong> A fix is never just switched on. This plugin first opens your own pages in a hidden frame, twice without the fix and once with it, and compares them: the text, the place of every visible element, script errors, files that failed to load. The fix stays on only if nothing changed for the visitor and something was actually saved. If not, it is left off and you are told why.<\/p>\n\n<p>It is not a cache plugin and does not replace one. It works next to the one you already have.<\/p>\n\n<h4>What the check looks at<\/h4>\n\n<p>The check opens your pages in a hidden frame of its own screen, at phone width and as a first-time visitor, so it sees what a visitor's browser sees, not only what the server sends.<\/p>\n\n<ul>\n<li>Front-end pages: the time the server takes, the weight of each page and whose files make it up, heavy pictures and videos, and plugins whose files load on pages where nothing of them is shown (every rule of their stylesheets is checked against the page)<\/li>\n<li>What each plugin and the theme cost your pages: server time, database queries, scripts and stylesheets and their weight, on how many pages. A plugin that takes 100 ms or more of a page (or a quarter of its time), or makes 100 or more queries there, is named with the numbers<\/li>\n<li>The admin too: the dashboard and the posts list (with WooCommerce, the products and orders lists), and the plugins and dashboard widgets that keep them waiting<\/li>\n<li>The largest stylesheets (50 KB or more) and scripts (100 KB or more), with the plugin or theme behind each<\/li>\n<li>Errors put down to the plugin or theme they come from: PHP errors while the page is built (fatal ones included), script errors in the browser, and files that do not load<\/li>\n<li>Pictures: the main picture of the first screen waiting for lazy loading or not marked as urgent, other lazy pictures on the first screen, pictures without a width and height, layout shift with what moved and what was added late, animations that never stop, how much more 3\u00d7 phone screens download than 2\u00d7, and how many copies of each upload WordPress keeps, with the theme or plugin behind each size<\/li>\n<li>Fonts: fonts from Google's servers, how many font files a page loads, text waiting for its font, Font Awesome or the same font loaded more than once (with who loads each copy), font preloads that cannot be used, and a font used for less than 3% of the text<\/li>\n<li>Scripts: files from other websites, the same library loaded twice, scripts that keep the browser busy while the page loads, and slow taps (Interaction to Next Paint): the check taps menus, buttons and tabs (never a link or a form, with the network held back) and names the plugin or theme whose code made the visitor wait<\/li>\n<li>Pages built from more than 1,400 elements, how many of them are hidden at phone width, and the largest parts<\/li>\n<li>Pages that no server or CDN cache can keep: the plugin or theme that gives every first-time visitor a cookie or a PHP session, or sends a no-store, no-cache or private header (the cart and the checkout are left out)<\/li>\n<li>Settings loaded on every request (autoloaded options): the largest, with the plugin or theme each belongs to (active, switched off or removed), and a button that stops loading the ones left behind by plugins and themes that are not active (they stay in the database, and it can be undone)<\/li>\n<li>Speed settings of well-known plugins that are off: Elementor (Inline Font Icons, CSS Print Method, optimized image loading, lazy background images, local Google Fonts and their font-display), Formidable Forms styles on every page, Wordfence logging every visit, and local Google Fonts in Astra, Kadence, OceanWP and Spectra (or GeneratePress font-display). This plugin only reads these settings<\/li>\n<li>Housekeeping: the PHP error log (whether strangers can download it, its size, who fills it), backup files left in wp-content, the largest database tables, plugins installed but switched off, two SEO plugins at once, scheduled jobs that have fallen behind (Action Scheduler included), and with WooCommerce the order storage, sessions that pile up and the cart script running outside the shop<\/li>\n<li>Server and hosting: PHP version, object cache, the page cache in use (and a cache plugin active with page caching off: WP Super Cache, W3 Total Cache, WP Fastest Cache, WP-Optimize, Breeze, Hummingbird), compression and browser caching of files, PHP without OPcache or with OPcache full, and slow pages whose time passes outside every plugin and the theme, which points at the server<\/li>\n<li>Links on the checked pages that lead to a missing page or go through redirects, each with the page it is on (up to 30 links per check)<\/li>\n<\/ul>\n\n<h4>The fixes<\/h4>\n\n<ul>\n<li><strong>Load the cart script only when the cart is in use.<\/strong> WooCommerce asks the server for the header cart on every visitor's first page view, even when the cart is empty. With the fix the empty cart comes with the page and the script loads the moment something is added. The cart and checkout pages are left as they are.<\/li>\n<li><strong>Load WooCommerce files only on pages that show something from the store.<\/strong> WooCommerce adds its stylesheets and scripts to every page of the site. With the fix a page that shows nothing from the store, no product, cart, notice or widget, is sent without them. Store pages and every page that shows a product keep all of them. Needs WordPress 6.9 or newer.<\/li>\n<li><strong>Load Contact Form 7 only on pages that have a form.<\/strong> Its script and stylesheet, and the reCAPTCHA or Turnstile script when one is connected, load only where a form is shown. Forms added by a template or placed with Elementor are covered.<\/li>\n<li><strong>Serve heavy pictures at the size they are shown.<\/strong> A JPEG or PNG far larger than the space it fills is replaced, for visitors, by a copy of the right size in WebP. The original stays in the media library untouched. Needs WordPress 6.9 or newer.<\/li>\n<li><strong>Load the main picture of each page first.<\/strong> The largest picture on the first screen is what Google times as the page's Largest Contentful Paint. Some themes and page builders make it wait for lazy loading or leave it unmarked, so the browser fetches it last. The fix finds that picture on your pages as visitors see them and has the browser fetch it first; on posts and products whose main picture is the featured image, it does the same for every such page. Where WordPress already does this, the fix has nothing to do. Needs WordPress 6.9 or newer.<\/li>\n<li><strong>Serve Google Fonts from your own server.<\/strong> Fonts from Google make the browser connect to two more servers before text in them can show, and they pass each visitor's IP address to Google. When you start its test, the fix downloads the fonts your pages load from Google into your uploads folder, adds font-display swap where it is missing, and points your pages at the copies. Fonts that a stylesheet pulls in with @import are left as they are. Needs WordPress 6.9 or newer.<\/li>\n<li><strong>Keep room for pictures while they load.<\/strong> A picture without a width and height in its tag takes no room until it arrives, and the text around it jumps when it does (Cumulative Layout Shift). The fix reads the size of each such picture from its file on your server and writes it into the tag. Pictures that load only when scrolled to get it once the test has seen them load; pictures from other websites are left as they are. Needs WordPress 6.9 or newer.<\/li>\n<li><strong>Minify stylesheets (CSS)<\/strong> and <strong>Minify scripts (JavaScript)<\/strong>, two separate fixes. The spaces, line breaks and comments come out of your theme's and plugins' own files, and a smaller copy is sent instead, under the same handle. Files that are minified already, files from other sites and code written into the page are left alone, and so is a file that would not get at least 5% smaller. Addresses inside stylesheets are rewritten, so fonts and pictures still load. If a script stops working once minified, the trial sees the error in that file, sends it as it is from then on and tests again; the fix is kept only if the pages then work, and the screen shows how many files are sent as they are.<\/li>\n<li><strong>Leave out the emoji script.<\/strong> WordPress adds a script and styles to every page so that very old browsers can show emoji as pictures. Browsers in use today show emoji themselves.<\/li>\n<li><strong>Stop Heartbeat calls from visitors.<\/strong> When a plugin loads WordPress Heartbeat on public pages, every open tab calls admin-ajax.php again and again, past any page cache. Before the trial this plugin calls admin-ajax.php itself as a visitor and looks at what answers Heartbeat there; only when nothing does is the Heartbeat file left out, with a stand-in that keeps the scripts that asked for it working. Logged-in users keep Heartbeat.<\/li>\n<li><strong>Load jQuery without jQuery Migrate.<\/strong> Migrate only helps code written for old versions of jQuery. If a script on your site still needs it, the test sees it fail and the fix is not kept.<\/li>\n<li><strong>Load scripts in the head with defer.<\/strong> Scripts in the head of the page make the browser wait before it shows anything. With the fix they download alongside the page and run once it is read, in the same order as before. jQuery is left as it is, because code written into pages often needs it right away. Needs WordPress 6.3 or newer.<\/li>\n<li><strong>Show YouTube videos as a picture until play is pressed.<\/strong> An embedded YouTube video loads the whole player as soon as the page opens, even for visitors who never watch it. With the fix the video shows its picture, from YouTube, and a play button in the same place and size, and the player loads when the button is pressed. Needs WordPress 6.9 or newer.<\/li>\n<li><strong>Show Google Maps as a button until the visitor asks for the map.<\/strong> An embedded Google Map loads its whole map viewer as soon as the page opens, even for visitors who never look at it. With the fix the map keeps its place and size and shows a button; the map loads when the button is pressed. Needs WordPress 6.9 or newer.<\/li>\n<\/ul>\n\n<p>The screen has a tab for each kind of fix (CSS &amp; JS, Images, Plugins), one for the check, and one for your page cache: which one is active, a test that opens the home page as a new visitor, and a button that clears it.<\/p>\n\n<h4>Works with other optimizers<\/h4>\n\n<p>When Autoptimize, LiteSpeed Cache, WP Fastest Cache, WP-Optimize or another optimizer already minifies or defers your files, this plugin does not do it a second time: it names the plugin and the exact setting (more in the FAQ). When a fix has nothing to do on your site, it says \"Nothing to gain\" and stays off.<\/p>\n\n<h4>Safety<\/h4>\n\n<ul>\n<li>A fix is on only after it passed the test on your pages. There is no switch that skips the test.<\/li>\n<li>Every page is tested twice, at the width of a desktop screen and at the width of a phone, because a stylesheet can hold rules that only apply on a phone.<\/li>\n<li>The test also notices a script that stopped reacting to something still on the page, such as a button that looks the same but no longer adds a product to the cart.<\/li>\n<li>While a fix is being tested, visitors do not see it. It is applied only to the test views.<\/li>\n<li>\"Turn off\" puts everything back at once.<\/li>\n<li>An emergency address, shown on the plugin's screen, switches every fix off without logging in.<\/li>\n<li>When a fix is switched on or off, this plugin clears the page cache so visitors do not keep getting the old pages.<\/li>\n<li>Removing the plugin removes its settings, the picture copies and the minified copies it made.<\/li>\n<\/ul>\n\n<h4>Privacy<\/h4>\n\n<p>This plugin sends nothing from your site anywhere. There is no account, no cloud service and no tracking. Everything it measures stays in your own database. The only link that leads away is one block on the plugin's own screen, for people who would rather have the work done for them.<\/p>\n\n<p>One fix fetches files from outside, and only when you start its test: \"Serve Google Fonts from your own server\" downloads the font stylesheets your pages already load from Google Fonts (fonts.googleapis.com) and the font files they name (fonts.gstatic.com) into your uploads folder. The request carries nothing about your site or visitors beyond what any browser sends for those files. Google Fonts terms: https:\/\/developers.google.com\/fonts\/terms \u00b7 Google privacy policy: https:\/\/policies.google.com\/privacy<\/p>\n\n<p>The fix \"Show YouTube videos as a picture until play is pressed\" changes what visitors' browsers load from YouTube, not whether they do: the page shows the video's picture from YouTube's image server (i.ytimg.com), and the YouTube player loads only when the visitor presses play. YouTube terms: https:\/\/www.youtube.com\/t\/terms<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install and activate the plugin.<\/li>\n<li>Open <strong>Site Check<\/strong> in the admin menu and press <strong>Check my site<\/strong>.<\/li>\n<li>Read the findings. Where a fix is available, press <strong>Fix it safely<\/strong> and keep the screen open until the test is done.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20it%20work%20next%20to%20wp%20rocket%2C%20litespeed%20cache%2C%20autoptimize%20and%20other%20optimizers%3F\"><h3>Does it work next to WP Rocket, LiteSpeed Cache, Autoptimize and other optimizers?<\/h3><\/dt>\n<dd><p>Two plugins minifying the same files is a common cause of broken pages. If Autoptimize, LiteSpeed Cache, WP Fastest Cache, W3 Total Cache, Speed Optimizer, WP-Optimize, Breeze, Jetpack Boost, Asset CleanUp or Fast Velocity Minify already minifies your stylesheets or scripts, this plugin does not try its own fix: it names the plugin and the exact setting, and links to that plugin's settings. This plugin only reads their settings and never changes them. For WP Rocket, Perfmatters, FlyingPress, NitroPack and Hummingbird, whose settings it cannot read, it reminds you to keep only one of the two.<\/p>\n\n<p>The same goes for loading scripts with defer: while Autoptimize, LiteSpeed Cache, WP Fastest Cache, Speed Optimizer, WP-Optimize or Jetpack Boost already defers your scripts, this plugin's defer fix cannot be tried.<\/p>\n\n<p>When a fix has nothing to do on your site, for example because your theme does not load that file in the first place, this plugin says \"Nothing to gain\" and leaves it off.<\/p><\/dd>\n<dt id=\"which%20themes%20and%20page%20caches%20is%20it%20tested%20with%3F\"><h3>Which themes and page caches is it tested with?<\/h3><\/dt>\n<dd><p>Themes: Astra, Kadence, GeneratePress, OceanWP, Twenty Twenty-Five, Hello Elementor with Elementor, Storefront.<\/p>\n\n<p>Page caches, switching a fix on and off with the cache running: Cache Enabler, WP Super Cache, WP-Optimize, W3 Total Cache, Breeze, WP Fastest Cache.<\/p>\n\n<p>This plugin also asks WP Rocket, LiteSpeed Cache, Speed Optimizer, Hummingbird and Autoptimize to clear their cache, but we have not yet tested those ourselves. Other caches can listen to the <code>imzura_site_check_clear_cache<\/code> action.<\/p><\/dd>\n<dt id=\"will%20it%20raise%20my%20pagespeed%20insights%20score%3F\"><h3>Will it raise my PageSpeed Insights score?<\/h3><\/dt>\n<dd><p>It removes causes the score is built from, such as files a page does not use, the main picture loading late, pictures without a size and fonts from another server, and each fix shows what it saved on your pages. How much the score moves depends on what your site had to begin with, so this plugin makes no promise about the number.<\/p><\/dd>\n<dt id=\"can%20someone%20fix%20my%20site%20for%20me%3F\"><h3>Can someone fix my site for me?<\/h3><\/dt>\n<dd><p>Yes. The people behind this plugin fix slow WordPress and WooCommerce sites for a fixed price, on a copy of the site first, with a before-and-after measurement: <a href=\"https:\/\/imzura.com\/services\/wordpress-speed-optimization?utm_source=imzura-site-check&amp;utm_medium=readme\">imzura.com<\/a>. The plugin works the same whether you ask or not.<\/p><\/dd>\n<dt id=\"is%20there%20a%20pro%20version%3F\"><h3>Is there a Pro version?<\/h3><\/dt>\n<dd><p>Yes, as a separate add-on: <a href=\"https:\/\/imzura.com\/products\/site-check?utm_source=imzura-site-check&amp;utm_medium=readme#pro\">imzura Site Check Pro<\/a>. It tries every fix for you, lets you switch plugins and scripts off on the pages that do not need them, checks your site after every update (if an update and a fix clash, the fixes go off and you get an email) and keeps a checked backup of your Media Library. Every change is still tried on your pages first. This plugin stays free and complete without it.<\/p><\/dd>\n<dt id=\"site%20health%20says%20%22autoloaded%20options%20could%20affect%20performance%22.%20can%20this%20plugin%20help%3F\"><h3>Site Health says \"Autoloaded options could affect performance\". Can this plugin help?<\/h3><\/dt>\n<dd><p>Yes. The check lists the largest settings WordPress loads on every request and the plugin or theme each one belongs to. Settings left behind by plugins and themes that are switched off or removed, and not read on any page the check opened, can be taken off the every-request list with one button. Nothing is deleted, a plugin that comes back still finds its settings, and the button next to it puts everything back.<\/p><\/dd>\n<dt id=\"my%20host%20or%20cloudflare%20should%20cache%20my%20pages%2C%20but%20every%20visit%20is%20a%20miss.%20why%3F\"><h3>My host or Cloudflare should cache my pages, but every visit is a miss. Why?<\/h3><\/dt>\n<dd><p>Run the check: it names the plugin or theme that gives every first-time visitor a cookie or a PHP session, or sends a header that tells caches not to keep the page. Server and CDN caches do not keep such pages by default. Look in that plugin's settings for a way to set the cookie only when it is needed, or ask its author.<\/p><\/dd>\n<dt id=\"does%20it%20replace%20my%20cache%20plugin%3F\"><h3>Does it replace my cache plugin?<\/h3><\/dt>\n<dd><p>No. This plugin does not cache pages. Keep the cache plugin you have; this plugin clears its cache when a fix is switched on or off.<\/p><\/dd>\n<dt id=\"another%20plugin%20already%20minifies%20my%20files.%20what%20happens%3F\"><h3>Another plugin already minifies my files. What happens?<\/h3><\/dt>\n<dd><p>This plugin reads that plugin's setting, and while it is on, its own minify fix cannot be tried. The fix shows which plugin and which setting, with a link to its settings. Turn it off there, or keep that plugin and leave this plugin's fix off.<\/p><\/dd>\n<dt id=\"is%20minifying%20worth%20it%20if%20my%20server%20compresses%20files%3F\"><h3>Is minifying worth it if my server compresses files?<\/h3><\/dt>\n<dd><p>Less than without compression, and this plugin says so. The test measures what each fix saves on your own pages, and a fix that saves nothing is left off.<\/p><\/dd>\n<dt id=\"what%20happens%20if%20a%20fix%20breaks%20something%3F\"><h3>What happens if a fix breaks something?<\/h3><\/dt>\n<dd><p>It should not get that far: a fix that changes the text or the layout of a tested page, adds a script error or stops a file from loading is not kept. If you still see a problem, press \"Turn off\" next to the fix, or open the emergency address shown on the plugin's screen. Both put the pages back as they were.<\/p><\/dd>\n<dt id=\"the%20test%20said%20%22not%20kept%22.%20is%20something%20wrong%20with%20my%20site%3F\"><h3>The test said \"Not kept\". Is something wrong with my site?<\/h3><\/dt>\n<dd><p>No. It means the pages did not look exactly the same with the fix, so this plugin left it off. The reason is shown next to the fix.<\/p><\/dd>\n<dt id=\"i%20use%20w3%20total%20cache%20and%20still%20see%20the%20old%20page%20right%20after%20switching%20a%20fix\"><h3>I use W3 Total Cache and still see the old page right after switching a fix<\/h3><\/dt>\n<dd><p>In its \"Disk: Enhanced\" mode W3 Total Cache can keep serving a page for up to 30 seconds after the cache was cleared. Wait half a minute and reload.<\/p><\/dd>\n<dt id=\"the%20check%20or%20a%20test%20fails%20on%20a%20staging%20site%20locked%20with%20a%20server%20password\"><h3>The check or a test fails on a staging site locked with a server password<\/h3><\/dt>\n<dd><p>When a site sits behind HTTP Basic Auth, WordPress can mistake the lock's user name and password for an application password and refuse the request. On the locked copy, switch application passwords off while you test:<\/p>\n\n<pre><code>add_filter( 'wp_is_application_passwords_available', '__return_false' );\n<\/code><\/pre><\/dd>\n<dt id=\"i%20use%20recaptcha%20v3%20with%20contact%20form%207.%20anything%20i%20should%20know%3F\"><h3>I use reCAPTCHA v3 with Contact Form 7. Anything I should know?<\/h3><\/dt>\n<dd><p>With the Contact Form 7 fix on, the reCAPTCHA script loads only on pages that show a form. Google <a href=\"https:\/\/developers.google.com\/recaptcha\/docs\/v3\">recommends<\/a> running reCAPTCHA v3 on forms \"as well as in the background of pages for analytics\". If you rely on v3 scores, weigh that before you keep the fix on.<\/p><\/dd>\n<dt id=\"which%20woocommerce%20files%20stay%20on%20every%20page%3F\"><h3>Which WooCommerce files stay on every page?<\/h3><\/dt>\n<dd><p>The two scripts that record where a visitor came from. WooCommerce credits an order to the first page of the visit, and that is often a blog post or the homepage, so they are never removed. A stylesheet your theme has replaced with its own version is left alone as well: such a file also styles parts of the theme. On those themes the fix says \"Nothing to gain\".<\/p><\/dd>\n<dt id=\"why%20does%20this%20plugin%20not%20remove%20unused%20css%3F\"><h3>Why does this plugin not remove unused CSS?<\/h3><\/dt>\n<dd><p>Because nobody can know for sure which rules a site will never need. A rule unused on the pages a tool looks at may be needed on another page, by a menu or a form once a visitor taps it, or by a script that adds a class later; a site broken that way can look fine in every test. So this plugin tells you which stylesheets are the largest and who adds them, minifies them if you want, and leaves the rules alone.<\/p><\/dd>\n<dt id=\"how%20does%20this%20plugin%20time%20each%20plugin%3F\"><h3>How does this plugin time each plugin?<\/h3><\/dt>\n<dd><p>Only while the check reads a page or an admin screen, this plugin places a marker in WordPress's hooks wherever the code passes from one plugin to another, and notes the time at each marker. A plugin's time is what its own code took, without the time of the other plugins it called on the way; its database queries are those its code asked for, directly or through WordPress. Dashboard widgets are not run from a hook, so each one is timed on its own. The plugins themselves are not changed or wrapped, and the visits of real visitors are not measured. The time it takes to load a plugin's files is not counted, so its real cost is a little higher than shown.<\/p><\/dd>\n<dt id=\"which%20pictures%20does%20the%20picture%20fix%20leave%20alone%3F\"><h3>Which pictures does the picture fix leave alone?<\/h3><\/dt>\n<dd><p>Pictures WordPress already resizes for each screen (those with <code>srcset<\/code>), pictures set as a CSS background, and pictures on pages that were not opened during the test.<\/p><\/dd>\n<dt id=\"does%20it%20work%20without%20woocommerce%3F\"><h3>Does it work without WooCommerce?<\/h3><\/dt>\n<dd><p>Yes. The WooCommerce checks and the cart fix simply do not appear.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.7.0<\/h4>\n\n<ul>\n<li>\"Leave out the emoji script\" is no longer turned back on pages that show emoji: the test compared the emoji WordPress draws as pictures with the same emoji shown as text, and saw a change of text. Emoji are now left out of that comparison.<\/li>\n<li>The plugin's code now uses its own name inside too (imzura_site_check_ instead of speed_doctor_). Saved settings and test results move to the new names by themselves on the first load after the update, and the emergency address you may have saved still works.<\/li>\n<li>For other caches: the action this plugin fires when a fix changes is now imzura_site_check_clear_cache.<\/li>\n<li>A fix that saves server time shows it after its trial: the time the server took to build each page and its database queries, before and after.<\/li>\n<li>Freesoul Deactivate Plugins and Plugin Organizer are recognised as plugins that already choose which plugins each page loads.<\/li>\n<li>The Site Check screen and the FAQ mention imzura Site Check Pro, the paid add-on. The note shows only on this plugin's own screen and goes away once Pro is installed.<\/li>\n<\/ul>\n\n<h4>1.6.1<\/h4>\n\n<ul>\n<li>A layout shift now names a late element that has no id or class by its text (or its picture), and moved text by its words. Elements that are in the page from the start are no longer named as added late.<\/li>\n<li>The check no longer says the server sends files without compression, or that browsers are not told to keep them, when it could not read the answer as a visitor: a site behind a password (a staging copy), a maintenance page or a security challenge.<\/li>\n<\/ul>\n\n<h4>1.6.0<\/h4>\n\n<ul>\n<li>New check: slow taps (Interaction to Next Paint). After the page has loaded, the check taps up to five menus, buttons or tabs and names the plugin or theme whose click code made the visitor wait, and scripts that keep the browser busy after load.<\/li>\n<li>New check: pages built from more than 1,400 elements, with how many are hidden at phone width and the largest parts.<\/li>\n<li>New check: pages that no server or CDN cache can keep, with the plugin or theme that gives every first-time visitor a cookie or a PHP session, or marks the page no-store, no-cache or private.<\/li>\n<li>The autoloaded settings finding names the plugin or theme behind each large entry, and a button stops loading the entries of plugins and themes that are not active or were removed (undo puts them back). Needs WordPress 6.4 or newer.<\/li>\n<li>New fix: Google Maps embeds show a button in the same place and size, and the map loads when the visitor asks for it.<\/li>\n<li>A layout shift now names what was added while the page loaded and pushed the content down, not only what moved.<\/li>\n<li>The Contact Form 7 fix can be tried on a site where no page shows a form, and it finds forms kept in page-builder data (Elementor, Beaver Builder, Bricks, Oxygen).<\/li>\n<\/ul>\n\n<h4>1.5.0<\/h4>\n\n<ul>\n<li>A new look for the plugin's screen: the last check is summed up at the top, with a ring of the findings by level and the four counts, cards that show each finding's level with a coloured strip and a label, plainer tabs, and a short explanation before the first check.<\/li>\n<li>The summary of the check shows on the Check tab only, so the fix tabs start right below the title.<\/li>\n<li>On a phone, the tables that show what a fix saved keep each number on one line and scroll sideways.<\/li>\n<\/ul>\n\n<h4>1.4.0<\/h4>\n\n<ul>\n<li>The check names hosting problems: PHP without OPcache, OPcache that is full, and slow pages where most of the server time passes outside every plugin and the theme, with the numbers for each page.<\/li>\n<li>The check follows the same-site links on the pages it opens and names links that lead to a missing page (404 or 410) and links that go through redirects, with the whole chain.<\/li>\n<li>After a check, the block at the bottom of the screen says how many findings are to fix first and worth fixing.<\/li>\n<\/ul>\n\n<h4>1.3.0<\/h4>\n\n<ul>\n<li>After a fix is kept, the plugin's screen asks once, below the fixes, for a review on WordPress.org. \"Do not ask again\" hides it for good; nothing else on the admin changes.<\/li>\n<li>The fix that keeps room for pictures leaves alone pictures marked sizes=\"auto\". Browsers that support it, such as Chrome, already give them a fixed box, and writing a size into the tag changed how they look, so the trial did not keep the fix.<\/li>\n<li>Add-ons can read what the check's browser saw on each page (the imzura_site_check_seen action), and the list of plugins that may already do a job names Perfect Images and Disable Media Sizes when they choose which picture sizes are made.<\/li>\n<li>The fixes that change the finished page (WooCommerce files, heavy pictures, the main picture, Google Fonts, room for pictures, YouTube) use the page WordPress hands to plugins from 6.9 on, and need WordPress 6.9 or newer. The plugin opens no output buffer of its own across the page.<\/li>\n<li>New fix: stop Heartbeat calls from visitors. When a plugin loads WordPress Heartbeat on public pages, every open tab calls admin-ajax.php again and again, past any page cache. Before the trial this plugin calls admin-ajax.php itself as a visitor and looks at what answers Heartbeat there; only when nothing does is the Heartbeat file left out, with a stand-in that keeps the scripts that asked for it working. Logged-in users keep Heartbeat.<\/li>\n<li>Old revisions can be removed from the check's report: all but the newest 5 of each post (or the number set in WP_POST_REVISIONS) go, autosaves stay. They are first written to a compressed copy in wp-content\/uploads\/imzura-site-check\/copies, so \"Put them back\" restores the same rows and fields; \"Delete the copy\" removes it.<\/li>\n<li>The check names Heartbeat loaded for visitors (how often it calls and who asks for it), admin screens where a plugin made Heartbeat call more often than every 60 seconds, and old revisions piling up in the database (how many, how much text, and the posts with the most).<\/li>\n<li>New fix: serve Google Fonts from your own server. The trial counts the other websites each page connects to, among those both untouched views connected to; fewer is a gain and shows as a column in the table.<\/li>\n<li>The check names the setting that keeps Google Fonts on your server in Astra, Kadence, OceanWP and Spectra, and GeneratePress font-display, when the fonts they load come from Google.<\/li>\n<li>The check weighs what phones with 3\u00d7 screens download next to 2\u00d7 screens, from the srcset of each picture and the sizes of its files on the server. PageSpeed Insights tests phones at a lower density and does not show it.<\/li>\n<li>The check counts the copies WordPress keeps of each picture (one per size the theme and plugins ask for) and the disk space they take, and names who added each size. It does not say which sizes to drop: pages pick sizes by screen width.<\/li>\n<li>The check names a font that is loaded twice: asked from Google Fonts by two stylesheets (with the theme or plugin that likely adds each), or the same font file downloaded from two places.<\/li>\n<li>The check also names animations on the first screen that never stop, and a font loaded for less than 3% of the text on pages where another font draws at least 10%.<\/li>\n<li>New fix: keep room for pictures while they load. Pictures without a width and height get them from their file on the server; the trial counts such pictures on each page and shows the count in the table.<\/li>\n<li>New fix: load the main picture of each page first. The trial counts a main picture that waits (lazy loading, or not marked urgent) and shows it in the table; a fix that makes the main picture wait is not kept.<\/li>\n<li>The WooCommerce files fix now works on block themes such as Twenty Twenty-Five. WooCommerce adds its account link to the header of block themes, so every page counted as showing something from the store and the fix found nothing to leave out. The plain account link no longer counts; an account menu that opens still does.<\/li>\n<li>The WooCommerce files fix also leaves out WooCommerce's block stylesheet on pages without anything from the store.<\/li>\n<li>The report keeps, for each page, which scripts and stylesheets it loaded, and the admin screen lets add-ons run a fix's trial as its own button does.<\/li>\n<\/ul>\n\n<h4>1.2.0<\/h4>\n\n<ul>\n<li>The check now opens each page in a hidden frame, at phone width and as a first-time visitor, and reports what only a browser sees.<\/li>\n<li>Errors on your pages, each put down to the plugin or theme it comes from: PHP errors while the page is built (a fatal error is named as such, with the pages it stops), script errors, and files that do not load.<\/li>\n<li>Pictures: the largest picture on the first screen waiting for lazy loading or not marked as urgent, other lazy pictures on the first screen, pictures without a width and height, and layout shift with what moved the page.<\/li>\n<li>Fonts: Google's servers, many font files, text that waits for its font, Font Awesome loaded more than once, font preloads that cannot be used.<\/li>\n<li>Scripts: files from other websites, the same library loaded twice, scripts that keep the browser busy; the largest stylesheets and scripts with the plugin or theme behind each.<\/li>\n<li>Plugins that load their stylesheets on pages where none of their rules apply, and block styles on pages without blocks.<\/li>\n<li>Plugins that keep the server busy: how long the code of each plugin and the theme ran while each page was built, and how many database queries it made. The table of plugins shows it for all of them. The same for the dashboard, the posts list and, with WooCommerce, the products and orders lists, opened as the administrator.<\/li>\n<li>Speed settings that are off in Elementor, Formidable Forms and Wordfence, named as each plugin's own screen names them.<\/li>\n<li>A cache plugin that is active with its page caching switched off is named, with the setting. It no longer counts as a second cache next to the one in use (WP-Optimize kept for its database tools, for example).<\/li>\n<li>Housekeeping: the PHP error log (public, large, who fills it), backup files in wp-content, the largest database tables, switched-off plugins, two SEO plugins at once.<\/li>\n<li>The FAQ explains why this plugin minifies stylesheets but does not remove the parts a page does not use.<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>Minify scripts: a file that stops working once minified is now sent as it is, and the trial runs again without it, instead of the whole fix being turned off. The fix shows how many files are sent as they are.<\/li>\n<li>Every fix now changes the page and its files in one pass, in a fixed order: files left out first, then the rest minified, then pictures and video players. Each fix works on what the fixes before it left, and a fix that fails leaves the page as the fixes before it made it.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>New fixes: minify stylesheets, minify scripts, leave out the emoji script, load jQuery without jQuery Migrate, load scripts in the head with defer, show YouTube videos as a picture until play is pressed.<\/li>\n<li>A trial now also counts the files a page waits for before it shows anything, and the embedded frames that load something.<\/li>\n<li>A fix that does what another active optimizer already does cannot be tried; the screen names the plugin and the exact setting.<\/li>\n<li>The check now looks at how the server delivers pages and files: compression and browser caching.<\/li>\n<li>The same finding on several pages is now one finding that lists the pages.<\/li>\n<li>The screen has tabs: Check, CSS &amp; JS, Images, Plugins and Cache. The Cache tab shows the page cache in use, opens the home page as a new visitor, and clears the cache.<\/li>\n<li>Fixed: from WordPress 6.7 every page logged a notice because the plugin's texts were loaded too early.<\/li>\n<\/ul>\n\n<h4>0.8.0<\/h4>\n\n<ul>\n<li>Every page is now tested at phone width as well as at desktop width.<\/li>\n<\/ul>\n\n<h4>0.7.0<\/h4>\n\n<ul>\n<li>New fix: load WooCommerce files only on pages that show something from the store.<\/li>\n<li>The test now notices a script that stopped reacting to something still on the page.<\/li>\n<li>The check no longer counts the WooCommerce scripts that record where a visitor came from as unused.<\/li>\n<\/ul>\n\n<h4>0.6.1<\/h4>\n\n<ul>\n<li>Database reads use prepared table names.<\/li>\n<li>Added this readme.<\/li>\n<\/ul>\n\n<h4>0.6.0<\/h4>\n\n<ul>\n<li>Switching a fix on or off, the emergency address and deactivating the plugin now clear the page cache.<\/li>\n<\/ul>\n\n<h4>0.5.0<\/h4>\n\n<ul>\n<li>New fix: serve heavy pictures at the size they are shown.<\/li>\n<\/ul>\n\n<h4>0.4.0<\/h4>\n\n<ul>\n<li>New in the check: what each plugin and the theme add to your pages.<\/li>\n<li>Fixed: on block themes a form added by a template lost its stylesheet.<\/li>\n<\/ul>\n\n<h4>0.3.0<\/h4>\n\n<ul>\n<li>New fix: load Contact Form 7 only on pages that have a form.<\/li>\n<\/ul>\n\n<h4>0.2.0<\/h4>\n\n<ul>\n<li>The test engine: try a fix on hidden views, keep it only if the pages stay the same.<\/li>\n<li>New fix: load the cart script only when the cart is in use.<\/li>\n<\/ul>\n\n<h4>0.1.0<\/h4>\n\n<ul>\n<li>The check and the admin screen.<\/li>\n<\/ul>","raw_excerpt":"Find what makes WordPress slow and fix it safely: Core Web Vitals, PageSpeed, WooCommerce. Every fix is tested on your own pages before it stays on.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/395191","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=395191"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/imzura"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=395191"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=395191"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=395191"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=395191"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=395191"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=395191"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}