77% wedesin-html-sitemap

Code Review | Digihood HTML Sitemap

WordPress plugin Digihood HTML Sitemap scored 77% from 54 tests.

About plugin

  • Plugin page: wedesin-html-sitemap
  • Plugin version: 3.00
  • PHP version: 7.4.16
  • WordPress compatibility: 3.5-6.3
  • WordPress version: 6.3.1
  • First release: Aug 16, 2016
  • Latest release: Sep 20, 2023
  • Number of updates: 11
  • Update frequency: every 235.8 days
  • Top authors: Josif201 (90.91%)digihood (18.18%)

Code review

54 tests

User reviews

1 review

Install metrics

200+ active / 3,697 total downloads

Benchmarks

Plugin footprint 83% from 16 tests

Installer Passed 1 test

🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully

Server metrics [RAM: ▲0.75MB] [CPU: ▲3.99ms] Passed 4 tests

A check of server-side resources used by Digihood HTML Sitemap
No issues were detected with server-side resource usage
PageMemory (MB)CPU Time (ms)
Home /4.23 ▲0.7740.16 ▲3.95
Dashboard /wp-admin4.10 ▲0.8051.28 ▲2.03
Posts /wp-admin/edit.php4.15 ▲0.7956.69 ▲9.38
Add New Post /wp-admin/post-new.php6.61 ▲0.7292.64 ▲1.39
Media Library /wp-admin/upload.php3.93 ▲0.7040.64 ▲8.57
Digihood HTML sitemap /wp-admin/admin.php?page=sitemap3.9349.05
Digi Plugins /wp-admin/admin.php?page=d1g1-plugins3.9377.52
DIGI Log /wp-admin/admin.php?page=d1g1-logs3.9340.26

Server storage [IO: ▲0.77MB] [DB: ▲0.00MB] Passed 3 tests

How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 90 new files
Database: no new tables, 6 new options
New WordPress options
can_compress_scripts
widget_recent-posts
widget_theysaidso_widget
db_upgraded
theysaidso_admin_options
widget_recent-comments

Browser metrics Passed 4 tests

A check of browser resources used by Digihood HTML Sitemap
This plugin has a minimal impact on browser resources
PageNodesMemory (MB)Script (ms)Layout (ms)
Home /3,001 ▲26615.43 ▲1.231.70 ▼0.1337.51 ▼22.86
Dashboard /wp-admin2,404 ▲2166.80 ▲0.91129.80 ▲24.5051.55 ▲9.04
Posts /wp-admin/edit.php2,316 ▲2273.77 ▲1.7656.16 ▲17.9130.72 ▼3.68
Add New Post /wp-admin/post-new.php1,566 ▲2223.20 ▲4.84597.43 ▼27.3234.03 ▼38.43
Media Library /wp-admin/upload.php1,455 ▲674.59 ▲0.2888.37 ▼9.5347.63 ▲1.99
Digihood HTML sitemap /wp-admin/admin.php?page=sitemap1,1703.3862.4593.66
Digi Plugins /wp-admin/admin.php?page=d1g1-plugins1,0373.3670.6074.12
DIGI Log /wp-admin/admin.php?page=d1g1-logs1,0443.3758.0136.65

Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests

🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
  • This plugin did not uninstall successfully, leaving 6 options in the database
    • widget_theysaidso_widget
    • widget_recent-comments
    • theysaidso_admin_options
    • db_upgraded
    • widget_recent-posts
    • can_compress_scripts

Smoke tests 50% from 4 tests

Server-side errors Passed 1 test

🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
The smoke test was a success, however most plugin functionality was not tested

SRP 0% from 2 tests

🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Almost there! Just fix the following items
  • 3× PHP files perform the task of outputting text when accessed with GET requests:
    • > /wp-content/plugins/wedesin-html-sitemap/plugin-framework/Forms/html/FormFooter.php
    • > /wp-content/plugins/wedesin-html-sitemap/components/html-sitemap.php
    • > /wp-content/plugins/wedesin-html-sitemap/components/includes.php
  • 8× GET requests to PHP files trigger server-side errors or Error 500 responses:
    • > PHP Fatal error
      Uncaught Error: Class 'sitemap\\framework\\forms\\Fields\\FieldsVariables' not found in wp-content/plugins/wedesin-html-sitemap/plugin-framework/Forms/Fields/RepeaterFieldsHtml.php:12
    • > PHP Fatal error
      Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wedesin-html-sitemap/admin/admin-style-scripts.php:3
    • > PHP Fatal error
      Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wedesin-html-sitemap/languages/register-languages.php:2
    • > PHP Fatal error
      Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wedesin-html-sitemap/languages/register-languages.php:2
    • > PHP Fatal error
      Trait 'sitemap\\framework\\Forms\\Validation\\FieldValidator' not found in wp-content/plugins/wedesin-html-sitemap/plugin-framework/Forms/Validation/Validator.php on line 15
    • > PHP Fatal error
      Uncaught Error: Call to undefined function wp_upload_dir() in wp-content/plugins/wedesin-html-sitemap/plugin-framework/Functions/Logging/html.php:8
    • > PHP Fatal error
      Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wedesin-html-sitemap/plugin-framework/PluginAdmin/Menu/LoggingContent.php:12
    • > PHP Fatal error
      Uncaught Error: Call to undefined function settings_errors() in wp-content/plugins/wedesin-html-sitemap/plugin-framework/Forms/html/FormHeader.php:2

User-side errors Passed 1 test

🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found

Optimizations

Plugin configuration 86% from 29 tests

readme.txt Passed 16 tests

The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
5 plugin tags: html sitemap, sitemap, seo, simple sitemap, google sitemap

wedesin-html-sitemap/plugin.php 69% from 13 tests

The entry point to "Digihood HTML Sitemap" version 3.00 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
  • Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wedesin-html-sitemap.php" instead of "plugin.php")
  • Requires at least: Required version must match the one declared in readme.txt ("4.0" instead of "3.5")
  • Text Domain: The text domain name should consist of only dashes and lowercase characters
  • Description: Keep the plugin description shorter than 140 characters (currently 297 characters long)

Code Analysis Passed 3 tests

File types Passed 1 test

🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected5,143 lines of code in 82 files:
LanguageFilesBlank linesComment linesLines of code
PHP619591,4483,605
CSS4122491,070
Markdown11150184
PO File13639155
JavaScript3132969
SVG120060

PHP code Passed 2 tests

Analyzing cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity
Average complexity per logical line of code0.43
Average class complexity15.47
▷ Minimum class complexity1.00
▷ Maximum class complexity108.00
Average method complexity3.29
▷ Minimum method complexity1.00
▷ Maximum method complexity37.00
Code structure
Namespaces17
Interfaces0
Traits3
Classes31
▷ Abstract classes00.00%
▷ Concrete classes31100.00%
▷ Final classes00.00%
Methods214
▷ Static methods6028.04%
▷ Public methods16275.70%
▷ Protected methods73.27%
▷ Private methods4521.03%
Functions12
▷ Named functions1191.67%
▷ Anonymous functions18.33%
Constants8
▷ Global constants787.50%
▷ Class constants112.50%
▷ Public constants1100.00%

Plugin size Passed 2 tests

Image compression Passed 2 tests

It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.01MB with 0.01MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant
FileSize - originalSize - compressedSavings
plugin-framework/FrameworkAssets/img/d1g1-logo-cz.png14.23KB6.39KB▼ 55.07%