Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.00MB] [CPU: ▼9.94ms] Passed 4 tests
A check of server-side resources used by Custom Sitemap Shortcode
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 34.84 ▼6.29 |
Dashboard /wp-admin | 3.32 ▼0.03 | 44.47 ▼14.66 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.11 ▼1.91 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 90.50 ▼16.91 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.41 ▲1.79 |
Sitemap Settings /wp-admin/options-general.php?page=sitemap_settings | 3.18 | 32.78 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 11 new files
Database: no new tables, 8 new options
New WordPress options |
---|
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-posts |
widget_recent-comments |
cst_admin_css_setting |
db_upgraded |
theysaidso_admin_options |
cst_version |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Custom Sitemap Shortcode
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,937 ▲191 | 13.83 ▼0.78 | 5.30 ▲3.65 | 38.26 ▼3.64 |
Dashboard /wp-admin | 2,233 ▲51 | 5.10 ▼0.71 | 110.39 ▲4.45 | 38.85 ▼4.40 |
Posts /wp-admin/edit.php | 2,123 ▲34 | 2.35 ▲0.34 | 41.67 ▼1.11 | 33.98 ▼1.40 |
Add New Post /wp-admin/post-new.php | 1,535 ▲7 | 23.14 ▲4.90 | 677.49 ▲71.76 | 36.33 ▼20.33 |
Media Library /wp-admin/upload.php | 1,418 ▲36 | 4.35 ▲0.16 | 97.91 ▼0.16 | 40.99 ▼2.53 |
Sitemap Settings /wp-admin/options-general.php?page=sitemap_settings | 1,561 | 2.68 | 66.53 | 30.80 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie WordPress options were found after uninstall: 8 options
- widget_recent-posts
- cst_admin_css_setting
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- cst_version
- can_compress_scripts
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Please fix the following server-side errors
- 5 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=sitemap_settings
- > Notice in wp-content/plugins/custom-sitemap-template/lib/functions.php+248
Trying to access array offset on value of type bool
- > GET request to /wp-admin/options-general.php?page=sitemap_settings
- > Notice in wp-content/plugins/custom-sitemap-template/lib/functions.php+282
Undefined index: cst_admin_css_field
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following items
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/custom-sitemap-template/lib/functions.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/custom-sitemap-template/my-custom-sitemap.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need your attention:
- Screenshots: A description for screenshot #6 is missing in custom-sitemap-template/assets to your readme.txt
custom-sitemap-template/my-custom-sitemap.php 77% from 13 tests
The primary PHP file in "Custom Sitemap Shortcode" version 2.6.1 is used by WordPress to initiate all plugin functionality
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("custom-sitemap-template.php" instead of "my-custom-sitemap.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 150 characters long)
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
Success! There were no dangerous files found in this plugin640 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 108 | 37 | 470 |
CSS | 3 | 1 | 9 | 116 |
JavaScript | 4 | 18 | 4 | 54 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.21 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 14 | |
▷ Named functions | 14 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
PNG images were not found in this plugin