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
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.23 ▲0.77 | 40.16 ▲3.95 |
Dashboard /wp-admin | 4.10 ▲0.80 | 51.28 ▲2.03 |
Posts /wp-admin/edit.php | 4.15 ▲0.79 | 56.69 ▲9.38 |
Add New Post /wp-admin/post-new.php | 6.61 ▲0.72 | 92.64 ▲1.39 |
Media Library /wp-admin/upload.php | 3.93 ▲0.70 | 40.64 ▲8.57 |
Digihood HTML sitemap /wp-admin/admin.php?page=sitemap | 3.93 | 49.05 |
Digi Plugins /wp-admin/admin.php?page=d1g1-plugins | 3.93 | 77.52 |
DIGI Log /wp-admin/admin.php?page=d1g1-logs | 3.93 | 40.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
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,001 ▲266 | 15.43 ▲1.23 | 1.70 ▼0.13 | 37.51 ▼22.86 |
Dashboard /wp-admin | 2,404 ▲216 | 6.80 ▲0.91 | 129.80 ▲24.50 | 51.55 ▲9.04 |
Posts /wp-admin/edit.php | 2,316 ▲227 | 3.77 ▲1.76 | 56.16 ▲17.91 | 30.72 ▼3.68 |
Add New Post /wp-admin/post-new.php | 1,566 ▲22 | 23.20 ▲4.84 | 597.43 ▼27.32 | 34.03 ▼38.43 |
Media Library /wp-admin/upload.php | 1,455 ▲67 | 4.59 ▲0.28 | 88.37 ▼9.53 | 47.63 ▲1.99 |
Digihood HTML sitemap /wp-admin/admin.php?page=sitemap | 1,170 | 3.38 | 62.45 | 93.66 |
Digi Plugins /wp-admin/admin.php?page=d1g1-plugins | 1,037 | 3.36 | 70.60 | 74.12 |
DIGI Log /wp-admin/admin.php?page=d1g1-logs | 1,044 | 3.37 | 58.01 | 36.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
- > PHP Fatal error
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:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 61 | 959 | 1,448 | 3,605 |
CSS | 4 | 122 | 49 | 1,070 |
Markdown | 1 | 115 | 0 | 184 |
PO File | 1 | 36 | 39 | 155 |
JavaScript | 3 | 13 | 29 | 69 |
SVG | 12 | 0 | 0 | 60 |
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 code | 0.43 |
Average class complexity | 15.47 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 108.00 |
Average method complexity | 3.29 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 37.00 |
Code structure | ||
---|---|---|
Namespaces | 17 | |
Interfaces | 0 | |
Traits | 3 | |
Classes | 31 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 31 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 214 | |
▷ Static methods | 60 | 28.04% |
▷ Public methods | 162 | 75.70% |
▷ Protected methods | 7 | 3.27% |
▷ Private methods | 45 | 21.03% |
Functions | 12 | |
▷ Named functions | 11 | 91.67% |
▷ Anonymous functions | 1 | 8.33% |
Constants | 8 | |
▷ Global constants | 7 | 87.50% |
▷ Class constants | 1 | 12.50% |
▷ Public constants | 1 | 100.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 | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
plugin-framework/FrameworkAssets/img/d1g1-logo-cz.png | 14.23KB | 6.39KB | ▼ 55.07% |