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.13MB] [CPU: ▼2.43ms] Passed 4 tests
Server-side resources used by WPO Enhancements
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.56 ▲0.10 | 43.86 ▲6.37 |
Dashboard /wp-admin | 3.44 ▲0.14 | 45.72 ▼1.90 |
Posts /wp-admin/edit.php | 3.55 ▲0.20 | 43.82 ▼4.10 |
Add New Post /wp-admin/post-new.php | 6.02 ▲0.13 | 92.92 ▼3.27 |
Media Library /wp-admin/upload.php | 3.36 ▲0.13 | 34.05 ▼0.43 |
WPO Enhancements /wp-admin/options-general.php?page=wpo_enhancements | 3.30 | 30.08 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 7 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
widget_theysaidso_widget |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for WPO Enhancements
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲58 | 13.21 ▼1.28 | 1.77 ▲0.14 | 42.58 ▲1.84 |
Dashboard /wp-admin | 2,210 ▲24 | 5.85 ▲0.87 | 110.49 ▼0.64 | 43.95 ▲0.98 |
Posts /wp-admin/edit.php | 2,096 ▲7 | 1.97 ▼0.05 | 34.03 ▼4.29 | 31.93 ▼6.32 |
Add New Post /wp-admin/post-new.php | 1,531 ▲17 | 23.10 ▲5.55 | 609.35 ▼73.26 | 58.75 ▲2.10 |
Media Library /wp-admin/upload.php | 1,395 ▲10 | 4.14 ▼0.09 | 94.27 ▼7.59 | 40.76 ▼6.82 |
WPO Enhancements /wp-admin/options-general.php?page=wpo_enhancements | 1,037 | 2.03 | 23.86 | 30.17 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
These errors were triggered by the plugin
- 5 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=wpo_enhancements
- > Notice in wp-content/plugins/wpo-enhancements/src/backend.php+266
Trying to access array offset on value of type bool
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
Almost there! Just fix the following items
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wpo-enhancements/src/backend.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
7 plugin tags: cdn, enhancements, page speed insights, optimization, wpo...
wpo-enhancements/plugin.php 85% from 13 tests
The principal PHP file in "WPO Enhancements" v. 2.0.11 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Description: Keep the plugin description shorter than 140 characters (currently 147 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wpo-enhancements.php" instead of "plugin.php")
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
There were no executable files found in this plugin934 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 196 | 58 | 893 |
JavaScript | 2 | 10 | 0 | 41 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
Average class complexity | 48.00 |
▷ Minimum class complexity | 7.00 |
▷ Maximum class complexity | 89.00 |
Average method complexity | 2.77 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 11.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 | 53 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 36 | 67.92% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 17 | 32.08% |
Functions | 0 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 5 | |
▷ Global constants | 2 | 40.00% |
▷ Class constants | 3 | 60.00% |
▷ Public constants | 3 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
PNG images were not found in this plugin