{"id":364832,"date":"2026-09-15T18:30:48","date_gmt":"2026-09-15T18:30:48","guid":{"rendered":"https:\/\/fr.wordpress.org\/plugins\/site-audit-by-webdiagnosis\/"},"modified":"2026-09-19T13:50:48","modified_gmt":"2026-09-19T13:50:48","slug":"webdiagnosis-site-audit","status":"publish","type":"plugin","link":"https:\/\/cor.wordpress.org\/plugins\/webdiagnosis-site-audit\/","author":23268617,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.1.0","stable_tag":"1.1.0","tested":"7.1.2","requires":"6.0","requires_php":"7.4","requires_plugins":null,"header_name":"WebDiagnosis Site Audit","header_author":"WebDiagnosis","header_description":"Run a complete audit of your WordPress website to detect performance, security and configuration issues. Powered by WebDiagnosis. (Independent plugin - not affiliated with WordPress or the WordPress Foundation.)","assets_banners_color":"","last_updated":"2026-09-19 13:50:48","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/webdiagnosis.io","rating":0,"author_block_rating":0,"active_installs":10,"downloads":135,"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":"nicoblandel","date":"2026-09-15 18:30:17","revision":3697555},"1.1.0":{"tag":"1.1.0","author":"nicoblandel","date":"2026-09-19 13:50:48","revision":3703339}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3697594,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3697594,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3697573,"resolution":false,"location":"assets","locale":false}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.1.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3703339,"resolution":"1","location":"assets","locale":"","width":2042,"height":870},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3703339,"resolution":"2","location":"assets","locale":"","width":1840,"height":1316},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3703339,"resolution":"3","location":"assets","locale":"","width":1372,"height":1526}},"screenshots":{"1":"Diagnostic summary: overall verdict, share of checks passed, and severity breakdown","2":"Action plan: every issue ranked by impact, split between what to fix now and what to schedule","3":"Results by theme, each finding explained: why it matters, what to do, and who should do it"}},"plugin_section":[262246],"plugin_tags":[8533,23516,247,600,151481],"plugin_category":[54],"plugin_contributors":[280942],"plugin_business_model":[],"class_list":["post-364832","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-audit","plugin_tags-diagnostic","plugin_tags-performance","plugin_tags-security","plugin_tags-site-health","plugin_category-security-and-spam-protection","plugin_contributors-nicoblandel","plugin_committers-nicoblandel"],"banners":[],"icons":{"svg":"https:\/\/ps.w.org\/webdiagnosis-site-audit\/assets\/icon.svg?rev=3697573","icon":"https:\/\/ps.w.org\/webdiagnosis-site-audit\/assets\/icon.svg?rev=3697573","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/webdiagnosis-site-audit\/assets\/screenshot-1.png?rev=3703339","caption":"Diagnostic summary: overall verdict, share of checks passed, and severity breakdown"},{"src":"https:\/\/ps.w.org\/webdiagnosis-site-audit\/assets\/screenshot-2.png?rev=3703339","caption":"Action plan: every issue ranked by impact, split between what to fix now and what to schedule"},{"src":"https:\/\/ps.w.org\/webdiagnosis-site-audit\/assets\/screenshot-3.png?rev=3703339","caption":"Results by theme, each finding explained: why it matters, what to do, and who should do it"}],"raw_content":"\n

Most audit tools hand you a score and leave you guessing. WebDiagnosis Site Audit<\/strong> hands you a list of what to fix, in what order, and why it matters.<\/p>\n\n

One click runs more than 170 checks<\/strong> across 14 themes<\/strong> \u2014 security, performance, SEO, accessibility, WordPress configuration, eco-design and more. Every finding comes with three things a score cannot give you: what was observed, what it costs you, and the concrete action that resolves it.<\/p>\n\n

Built to be trusted<\/h4>\n\n

An audit is only useful if you can act on its results. That shapes how this plugin works:<\/p>\n\n

    \n
  • No false alarms.<\/strong> When a check cannot reach the data it needs, it says so instead of guessing. \"Not verifiable\" is a real answer \u2014 you will never chase a problem that does not exist.<\/li>\n
  • Severity that means something.<\/strong> Blocker, major, minor. A hardening suggestion is never dressed up as a vulnerability.<\/li>\n
  • Every finding is explained.<\/strong> Each result carries its own reasoning, the business impact, and the steps to fix it \u2014 including who can do it and how hard it is.<\/li>\n<\/ul>\n\n

    What gets checked<\/h4>\n\n
      \n
    • Security<\/strong> \u2014 SSL\/TLS, HTTP headers, exposed files, directory listing, user enumeration<\/li>\n
    • WordPress<\/strong> \u2014 core version, file editor, XML-RPC, REST API exposure, database prefix, cron<\/li>\n
    • Plugins & themes<\/strong> \u2014 updates, plugins removed from the directory, inactive items, abandoned code<\/li>\n
    • Performance<\/strong> \u2014 page cache, object cache, compression, render-blocking resources, TTFB<\/li>\n
    • SEO<\/strong> \u2014 title, meta description, canonical, robots.txt, sitemap, internal linking<\/li>\n
    • Structured data<\/strong> \u2014 Schema.org markup validated against what search engines actually require, not merely detected<\/li>\n
    • Accessibility<\/strong> \u2014 alt text, heading hierarchy, focus visibility, link purpose, landmarks<\/li>\n
    • Eco-design<\/strong> \u2014 page weight, image formats, web fonts, third-party scripts<\/li>\n
    • Infrastructure<\/strong> \u2014 PHP and MySQL versions, memory, execution limits, DNS<\/li>\n<\/ul>\n\n

      How it works<\/h4>\n\n
        \n
      1. Install and activate the plugin<\/li>\n
      2. Click Run a diagnostic<\/strong> from the Site Audit screen<\/li>\n
      3. Read the results by theme, starting with the priority action plan<\/li>\n<\/ol>\n\n

        The diagnostic runs only when you ask for it. It adds nothing to your front end and does not affect page load times.<\/p>\n\n

        Free and connected modes<\/h4>\n\n

        The plugin is fully functional on its own: one complete diagnostic per day, all themes, all findings, all recommendations.<\/p>\n\n

        Connecting a free WebDiagnosis account adds multi-page analysis, unlimited diagnostics, history, monitoring and shareable reports. No account is required to use the plugin.<\/p>\n\n

        External Services<\/h3>\n\n

        This plugin connects to an external service to perform website diagnostics.<\/p>\n\n

        The plugin does not send any personal data or content from the website.\nOnly technical configuration data is transmitted for analysis.<\/p>\n\n

        Service name:<\/strong> WebDiagnosis\nService URL:<\/strong> https:\/\/webdiagnosis.io<\/p>\n\n

        What the service is used for:<\/strong>\nThe service analyzes the WordPress website configuration and provides a diagnostic report with recommendations about performance, security and best practices.<\/p>\n\n

        What data is sent:<\/strong><\/p>\n\n

          \n
        • WordPress version<\/li>\n
        • PHP version<\/li>\n
        • List of active plugins<\/li>\n
        • Active theme name<\/li>\n
        • Site URL<\/li>\n
        • Basic server configuration information<\/li>\n<\/ul>\n\n

          When data is sent:<\/strong>\nData is only sent when the user manually runs a diagnostic analysis from the plugin interface.<\/p>\n\n

          Links to the service:<\/strong><\/p>\n\n

            \n
          • Privacy policy: https:\/\/webdiagnosis.io\/privacy-policy\/<\/li>\n
          • Terms of service: https:\/\/webdiagnosis.io\/terms-of-service\/<\/li>\n<\/ul>\n\n\n
              \n
            1. Upload the plugin files to the \/wp-content\/plugins\/webdiagnosis-site-audit\/<\/code> directory, or install through the WordPress plugins screen<\/li>\n
            2. Activate the plugin through the 'Plugins' screen in WordPress<\/li>\n
            3. Navigate to Site Audit in the admin menu to run your first diagnostic<\/li>\n<\/ol>\n\n\n
              \n

              Does this plugin slow down my site?<\/h3><\/dt>\n

              No. The diagnostic only runs when you manually trigger it. It does not add any frontend scripts or affect page load times.<\/p><\/dd>\n

              What data is collected?<\/h3><\/dt>\n

              Only technical configuration data is collected during a diagnostic: WordPress version, PHP version, active plugins list, theme information, and server configuration. No personal data or site content is transmitted.<\/p><\/dd>\n

              Do I need a WebDiagnosis account?<\/h3><\/dt>\n

              No. The plugin works standalone with a complete daily diagnostic. A WebDiagnosis account unlocks multi-page analysis, unlimited diagnostics, history, and monitoring.<\/p><\/dd>\n

              Why does a check sometimes say \"not verifiable\"?<\/h3><\/dt>\n

              Because it is honest. Some checks depend on data the plugin could not reach \u2014 a page that did not load, a server that did not answer. Reporting that plainly is better than reporting a problem that may not exist.<\/p><\/dd>\n

              Is this plugin affiliated with WordPress?<\/h3><\/dt>\n

              No. WebDiagnosis Site Audit is an independent plugin developed by WebDiagnosis. It is not affiliated with, endorsed by, or sponsored by WordPress\u00ae, the WordPress Foundation, or Automattic. \"WordPress\" is a registered trademark of the WordPress Foundation, used here only to describe the software the plugin runs on.<\/p><\/dd>\n\n<\/dl>\n\n\n

              1.1.0<\/h4>\n\n
                \n
              • Fixed and improved several checks<\/li>\n
              • Restored 56 checks that were silently skipped<\/li>\n
              • Fixed how translatable strings are handled, so the plugin can be translated into any language<\/li>\n
              • Strengthened the checks run before a release is published<\/li>\n<\/ul>\n\n

                1.0.0<\/h4>\n\n
                  \n
                • Initial public release<\/li>\n
                • 14 diagnostic themes, 170+ checks<\/li>\n
                • Structured data validated against search engine requirements<\/li>\n
                • Plain-language explanation and fix for every finding<\/li>\n
                • Bilingual interface (English\/French)<\/li>\n
                • Expert assistance request and feedback form<\/li>\n
                • Optional connected mode with the WebDiagnosis platform<\/li>\n<\/ul>","raw_excerpt":"Know what is actually wrong with your site. 170+ checks, ranked by urgency, each explained in plain language with the fix.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/364832","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=364832"}],"author":[{"embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/nicoblandel"}],"wp:attachment":[{"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=364832"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=364832"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=364832"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=364832"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=364832"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/cor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=364832"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}