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 successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.27MB] [CPU: ▲0.99ms] Passed 4 tests
An overview of server-side resources used by EnvyPopup - All-in-One Popup Management WordPress Plugin
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.76 ▲0.30 | 39.09 ▼1.44 |
Dashboard /wp-admin | 3.56 ▲0.26 | 46.06 ▼2.12 |
Posts /wp-admin/edit.php | 3.68 ▲0.32 | 48.44 ▲4.18 |
Add New Post /wp-admin/post-new.php | 6.15 ▲0.26 | 93.28 ▲12.18 |
Media Library /wp-admin/upload.php | 3.49 ▲0.26 | 35.45 ▲3.33 |
Settings /wp-admin/edit.php?post_type=envypopup&page=envy_popup_options | 3.45 | 32.62 |
Add New /wp-admin/post-new.php?post_type=envypopup | 3.61 | 58.76 |
All Messages /wp-admin/edit.php?post_type=envypopup | 3.53 | 34.54 |
Server storage [IO: ▲1.45MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 45 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
widget_envy_popup_widget_function |
can_compress_scripts |
widget_recent-comments |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by EnvyPopup - All-in-One Popup Management WordPress Plugin
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,953 ▲218 | 13.70 ▼0.53 | 5.71 ▲3.77 | 50.85 ▲8.05 |
Dashboard /wp-admin | 2,240 ▲52 | 4.86 ▲0.01 | 111.39 ▲0.15 | 42.57 ▼3.98 |
Posts /wp-admin/edit.php | 2,123 ▲34 | 2.01 ▼0.01 | 39.58 ▲5.01 | 36.32 ▼0.09 |
Add New Post /wp-admin/post-new.php | 1,546 ▲13 | 23.43 ▲0.29 | 596.09 ▼1.84 | 56.57 ▼3.78 |
Media Library /wp-admin/upload.php | 1,422 ▲34 | 4.22 ▼0.02 | 98.37 ▼2.82 | 46.23 ▲3.26 |
Settings /wp-admin/edit.php?post_type=envypopup&page=envy_popup_options | 1,222 | 2.08 | 23.18 | 27.27 |
Add New /wp-admin/post-new.php?post_type=envypopup | 2,580 | 7.83 | 175.49 | 68.90 |
All Messages /wp-admin/edit.php?post_type=envypopup | 1,084 | 2.09 | 29.32 | 29.97 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 7 options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
- widget_envy_popup_widget_function
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
- 10× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_post_meta() in wp-content/plugins/envypopup/includes/options/popup-button-js.php:4
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/envypopup/includes/envy-popup-widget.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/envypopup/includes/envy-popup-js-options.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/envypopup/includes/options/popup-timer-js.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/envypopup/includes/class-envy-popup.php:240
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/envypopup/includes/envy-popup-css-options.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/envypopup/includes/envy-popup-post-options.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/envypopup/includes/envy-popup-global-options.php:83
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/envypopup/public/partials/envy-popup-public-display.php:258
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/envypopup/includes/options/popup-animation-js.php:6
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need to be fixed:
- Tags: Please reduce the number of tags, currently 16 tag instead of maximum 10
envypopup/envy-popup.php 85% from 13 tests
"EnvyPopup - All-in-One Popup Management WordPress Plugin" version 1.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("envypopup.php" instead of "envy-popup.php")
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
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
No dangerous file extensions were detected5,162 lines of code in 30 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
SVG | 1 | 0 | 0 | 2,671 |
PHP | 20 | 311 | 518 | 1,549 |
CSS | 5 | 73 | 45 | 857 |
JavaScript | 4 | 21 | 24 | 85 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.34 |
Average class complexity | 6.25 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 38.00 |
Average method complexity | 2.62 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 36.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 26 | |
▷ Static methods | 2 | 7.69% |
▷ Public methods | 21 | 80.77% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 19.23% |
Functions | 44 | |
▷ Named functions | 44 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.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
2 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
public/img/timer_long.png | 3.82KB | 2.32KB | ▼ 39.16% |
public/img/timer.png | 2.39KB | 2.37KB | ▼ 0.98% |