Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.10MB] [CPU: ▼0.65ms] Passed 4 tests
A check of server-side resources used by WP Visual Sitemap
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.54 ▲0.08 | 42.40 ▲3.95 |
Dashboard /wp-admin | 3.40 ▲0.09 | 46.09 ▲1.06 |
Posts /wp-admin/edit.php | 3.51 ▲0.15 | 50.23 ▲4.27 |
Add New Post /wp-admin/post-new.php | 6.00 ▲0.11 | 84.42 ▼11.86 |
Media Library /wp-admin/upload.php | 3.32 ▲0.09 | 43.70 ▲10.19 |
WP Visual Sitemap /wp-admin/options-general.php?page=wpvs_settings | 3.26 | 32.56 |
Server storage [IO: ▲1.23MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 17 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
theysaidso_admin_options |
widget_theysaidso_widget |
db_upgraded |
widget_recent-comments |
widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WP Visual Sitemap
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,837 ▲66 | 13.48 ▼1.10 | 1.69 ▼0.43 | 43.28 ▼0.85 |
Dashboard /wp-admin | 2,241 ▲56 | 5.12 ▼0.73 | 102.69 ▼0.80 | 36.56 ▼6.21 |
Posts /wp-admin/edit.php | 2,126 ▲37 | 2.52 ▲0.49 | 47.31 ▲5.61 | 31.70 ▼3.25 |
Add New Post /wp-admin/post-new.php | 1,701 ▲178 | 22.95 ▼0.30 | 613.21 ▲25.58 | 29.85 ▼21.00 |
Media Library /wp-admin/upload.php | 1,423 ▲32 | 4.54 ▲0.41 | 98.87 ▼12.35 | 40.10 ▼9.89 |
WP Visual Sitemap /wp-admin/options-general.php?page=wpvs_settings | 1,628 | 3.07 | 70.09 | 53.99 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
These errors were triggered by the plugin
- 6 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=wpvs_settings
- > Warning in wp-content/plugins/wp-visual-sitemap/wpvs.php+214
Use of undefined constant value - assumed 'value' (this will throw an Error in a future version of PHP)
- 6 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=wpvs_settings
- > Warning in wp-content/plugins/wp-visual-sitemap/wpvs.php+214
Use of undefined constant text - assumed 'text' (this will throw an Error in a future version of PHP)
SRP Passed 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Congratulations! This plugin passed the SRP test
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
3 plugin tags: front end sitemap, visual sitemap, sitemap
wp-visual-sitemap/wpvs.php 92% from 13 tests
"WP Visual Sitemap" version 1.0.2's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("wp-visual-sitemap.php" instead of "wpvs.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected7,058 lines of code in 11 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 6 | 33 | 56 | 2,792 |
SVG | 1 | 0 | 0 | 2,671 |
JavaScript | 3 | 69 | 11 | 1,070 |
PHP | 1 | 173 | 92 | 525 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.42 |
Average class complexity | 17.50 |
▷ Minimum class complexity | 9.00 |
▷ Maximum class complexity | 26.00 |
Average method complexity | 6.50 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 22.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 6 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 6 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 13 | |
▷ Named functions | 13 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 0 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
PNG images were not found in this plugin