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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.06MB] [CPU: ▼6.13ms] Passed 4 tests
A check of server-side resources used by HTM Custom Areas
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.07 | 39.73 ▼2.94 |
Dashboard /wp-admin | 3.36 ▲0.06 | 51.08 ▼1.54 |
Posts /wp-admin/edit.php | 3.48 ▲0.12 | 53.10 ▼13.89 |
Add New Post /wp-admin/post-new.php | 5.94 ▲0.06 | 95.37 ▼3.84 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 35.20 ▼3.84 |
Add New /wp-admin/post-new.php?post_type=custom_area | 3.42 | 54.21 |
Custom Areas /wp-admin/edit.php?post_type=custom_area | 3.33 | 38.38 |
Custom Area Options /wp-admin/edit.php?post_type=custom_area&page=htmcas-options | 3.33 | 32.44 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 27 new files
Database: no new tables, 8 new options
New WordPress options |
---|
widget_recent-comments |
db_upgraded |
can_compress_scripts |
widget_recent-posts |
HTMCustomAreasVersion |
HTMCAS-options |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
HTM Custom Areas: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,861 ▲90 | 14.78 ▲0.48 | 2.11 ▲0.13 | 42.99 ▲2.00 |
Dashboard /wp-admin | 2,237 ▲46 | 4.85 ▼0.25 | 100.18 ▼6.75 | 43.01 ▼3.05 |
Posts /wp-admin/edit.php | 2,120 ▲31 | 1.99 ▼0.01 | 39.10 ▲2.10 | 35.04 ▲0.21 |
Add New Post /wp-admin/post-new.php | 1,545 ▲7 | 22.71 ▲4.43 | 645.99 ▼52.87 | 54.97 ▼3.91 |
Media Library /wp-admin/upload.php | 1,419 ▲31 | 4.16 ▼0.05 | 95.21 ▼5.99 | 43.96 ▼2.55 |
Add New /wp-admin/post-new.php?post_type=custom_area | 2,226 | 7.59 | 171.31 | 71.44 |
Custom Areas /wp-admin/edit.php?post_type=custom_area | 1,084 | 1.95 | 30.86 | 30.36 |
Custom Area Options /wp-admin/edit.php?post_type=custom_area&page=htmcas-options | 1,120 | 1.76 | 23.46 | 26.66 |
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
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
Smoke tests 25% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
SRP 0% 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 take a closer look at the following
- 4× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/htm-customareas/lib/admin/templates/linkmeta.php
- > /wp-content/plugins/htm-customareas/lib/admin/templates/ajaxlookup.php
- > /wp-content/plugins/htm-customareas/lib/frontend/templates/content.php
- > /wp-content/plugins/htm-customareas/lib/admin/templates/shortcodebox.php
- 40× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Warning
require_once(ABSPATH/wp-admin/includes/plugin.php): failed to open stream: No such file or directory in wp-content/plugins/htm-customareas/plugin.php on line 11
- > PHP Fatal error
Uncaught Error: Class 'HTMCustomAreasController' not found in wp-content/plugins/htm-customareas/lib/admin/controller/admin.php:7
- > PHP Notice
Trying to access array offset on value of type null in wp-content/plugins/htm-customareas/lib/admin/templates/ajaxlookup.php on line 26
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATH/wp-admin/includes/plugin.php' (include_path='.:/usr/share/php') in wp-content/plugins/htm-customareas/plugin.php on line 11
- > PHP Notice
Trying to access array offset on value of type null in wp-content/plugins/htm-customareas/lib/admin/templates/ajaxlookup.php on line 27
- > PHP Notice
Trying to access array offset on value of type null in wp-content/plugins/htm-customareas/lib/admin/templates/ajaxlookup.php on line 18
- > PHP Notice
Undefined variable: saved in wp-content/plugins/htm-customareas/lib/admin/templates/admin.php on line 4
- > PHP Notice
Trying to access array offset on value of type null in wp-content/plugins/htm-customareas/lib/admin/templates/ajaxlookup.php on line 68
- > PHP Fatal error
Uncaught Error: Class 'HTMCustomAreasController' not found in wp-content/plugins/htm-customareas/lib/frontend/controller/shortcodes.php:7
- > PHP Notice
Trying to access array offset on value of type null in wp-content/plugins/htm-customareas/lib/admin/templates/ajaxlookup.php on line 28
- > PHP Warning
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Please fix the following user-side errors
- > GET request to /wp-admin/post-new.php?post_type=custom_area
- > Network (severe)
wp-content/plugins/htm_customareas/assets/css/linkinput.css - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/edit.php?post_type=custom_area&page=htmcas-options
- > Network (severe)
wp-content/plugins/htm_customareas/assets/script/ui-tabs.js?ver=6.3.1 - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/edit.php?post_type=custom_area&page=htmcas-options
- > Network (severe)
wp-content/plugins/htm_customareas/assets/css/admin.css - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 93% 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
Please fix the following attributes:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== htm-customareas ===
)
htm-customareas/plugin.php 92% from 13 tests
"HTM Custom Areas" version 1.0.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("htm-customareas.php" instead of "plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Everything looks great! No dangerous files found in this plugin1,334 lines of code in 24 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 16 | 333 | 259 | 934 |
CSS | 4 | 44 | 14 | 273 |
JavaScript | 4 | 48 | 37 | 127 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.32 |
Average class complexity | 10.90 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 24.00 |
Average method complexity | 2.48 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 10 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 10 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 67 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 51 | 76.12% |
▷ Protected methods | 7 | 10.45% |
▷ Private methods | 9 | 13.43% |
Functions | 0 | |
▷ Named functions | 0 | 0.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
1 compressed PNG file occupies 0.00MB
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/css/customarea.png | 0.46KB | 0.41KB | ▼ 11.23% |