Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.11MB] [CPU: ▲0.88ms] Passed 4 tests
Analyzing server-side resources used by WP Revenue Booster
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.54 ▲0.08 | 37.20 ▲1.06 |
Dashboard /wp-admin | 3.48 ▲0.13 | 53.57 ▼5.40 |
Posts /wp-admin/edit.php | 3.51 ▲0.15 | 56.40 ▲7.89 |
Add New Post /wp-admin/post-new.php | 6.01 ▲0.13 | 99.08 ▼0.02 |
Media Library /wp-admin/upload.php | 3.33 ▲0.11 | 47.81 ▲14.03 |
Segments /wp-admin/edit.php?post_type=mprb-segment | 3.63 | 51.26 |
Options /wp-admin/admin.php?page=wprb-options | 3.35 | 40.08 |
Server storage [IO: ▲0.25MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 81 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_wprb_customizations |
New WordPress options |
---|
db_upgraded |
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
widget_theysaidso_widget |
can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for WP Revenue Booster
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,932 ▲186 | 13.77 ▼0.61 | 9.54 ▲7.61 | 39.93 ▼0.28 |
Dashboard /wp-admin | 2,235 ▲43 | 4.98 ▲0.02 | 109.30 ▼1.18 | 40.94 ▼4.34 |
Posts /wp-admin/edit.php | 2,127 ▲38 | 2.04 ▼0.00 | 40.25 ▲5.94 | 36.57 ▲4.22 |
Add New Post /wp-admin/post-new.php | 1,549 ▲35 | 23.28 ▲5.76 | 630.19 ▼47.18 | 35.39 ▼12.33 |
Media Library /wp-admin/upload.php | 1,427 ▲39 | 4.15 ▼0.03 | 100.86 ▼6.78 | 47.60 ▼1.29 |
Segments /wp-admin/edit.php?post_type=mprb-segment | 1,098 | 2.40 | 31.81 | 31.18 |
Options /wp-admin/admin.php?page=wprb-options | 830 | 2.17 | 25.41 | 25.04 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% 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 tables were found after uninstall: 1 table
- wp_wprb_customizations
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
SRP 0% 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
Almost there! Just fix the following items
- 35× PHP files output non-empty strings when accessed directly via GET requests (only 10 are shown):
- > /wp-content/plugins/wp-revenue-booster/app/lib/class-config.php
- > /wp-content/plugins/wp-revenue-booster/app/lib/class-user-data.php
- > /wp-content/plugins/wp-revenue-booster/app/lib/activation.php
- > /wp-content/plugins/wp-revenue-booster/app/views/index.php
- > /wp-content/plugins/wp-revenue-booster/app/lib/class-utils.php
- > /wp-content/plugins/wp-revenue-booster/app/controllers/class-options.php
- > /wp-content/plugins/wp-revenue-booster/app/helpers/class-app.php
- > /wp-content/plugins/wp-revenue-booster/app/lib/class-base-builtin-model.php
- > /wp-content/plugins/wp-revenue-booster/app/lib/class-ctrl-factory.php
- > /wp-content/plugins/wp-revenue-booster/app/views/admin/options/template-general.php
- 25× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wp-revenue-booster/app/lib/data/states/JP.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wp-revenue-booster/app/lib/data/states/MY.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wp-revenue-booster/app/lib/data/states/TR.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wp-revenue-booster/app/lib/data/states/BR.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wp-revenue-booster/app/lib/data/states/BG.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wp-revenue-booster/app/lib/data/states/TH.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wp-revenue-booster/app/lib/data/states/IT.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wp-revenue-booster/app/lib/data/states/AU.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wp-revenue-booster/app/lib/data/states/PE.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wp-revenue-booster/app/lib/data/states/MX.php:6
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Please fix the following attributes:
- Tags: Please delete some tags, you are using 20 tag instead of maximum 10
wp-revenue-booster/wp-revenue-booster.php Passed 13 tests
The primary PHP file in "WP Revenue Booster" version 1.0.2 is used by WordPress to initiate all plugin functionality
76 characters long description:
Dynamically personalize any text on your site based on your users' behavior.
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
Success! There were no dangerous files found in this plugin6,124 lines of code in 73 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 59 | 950 | 464 | 4,737 |
CSS | 7 | 169 | 25 | 772 |
JavaScript | 7 | 132 | 51 | 615 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.43 |
Average class complexity | 17.77 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 103.00 |
Average method complexity | 3.06 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 21.00 |
Code structure | ||
---|---|---|
Namespaces | 5 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 31 | |
▷ Abstract classes | 7 | 22.58% |
▷ Concrete classes | 24 | 77.42% |
▷ Final classes | 0 | 0.00% |
Methods | 258 | |
▷ Static methods | 134 | 51.94% |
▷ Public methods | 220 | 85.27% |
▷ Protected methods | 32 | 12.40% |
▷ Private methods | 6 | 2.33% |
Functions | 5 | |
▷ Named functions | 2 | 40.00% |
▷ Anonymous functions | 3 | 60.00% |
Constants | 25 | |
▷ Global constants | 25 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
No PNG images were found in this plugin