Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.80MB] [CPU: ▼5.26ms] Passed 4 tests
A check of server-side resources used by PZ Frontend Manager
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.23 ▲0.77 | 43.28 ▼2.80 |
| Dashboard /wp-admin | 4.12 ▲0.78 | 53.76 ▼7.84 |
| Posts /wp-admin/edit.php | 4.18 ▲0.82 | 53.33 ▲3.14 |
| Add New Post /wp-admin/post-new.php | 6.71 ▲0.82 | 86.77 ▼13.52 |
| Media Library /wp-admin/upload.php | 4.05 ▲0.82 | 40.91 ▲10.44 |
Server storage [IO: ▲4.35MB] [DB: ▲0.00MB] 67% from 3 tests
How much does this plugin use your filesystem and database?
These are issues you should consider
- Illegal file modification found: 1 file (0.99KB) outside of "wp-content/plugins/pz-frontend-manager/" and "wp-content/uploads/"
- (new file) wp-content/mu-plugins/disable-plugins.php
Filesystem: 141 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| pzfm_dashboard |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| pzfm-activation |
| widget_recent-comments |
| db_upgraded |
| widget_recent-posts |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by PZ Frontend Manager
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,711 ▼35 | 13.90 ▼0.78 | 7.80 ▲5.70 | 42.51 ▲0.54 |
| Dashboard /wp-admin | 2,209 ▲21 | 4.85 ▼1.01 | 113.90 ▼6.97 | 44.57 ▲1.24 |
| Posts /wp-admin/edit.php | 2,092 ▲3 | 2.00 ▼0.01 | 41.07 ▲5.84 | 36.42 ▲2.82 |
| Add New Post /wp-admin/post-new.php | 1,517 ▲3 | 17.38 ▼0.19 | 601.10 ▼67.62 | 61.92 ▲3.52 |
| Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.21 ▲0.02 | 104.82 ▲0.00 | 41.97 ▼3.93 |
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: 8 options
- can_compress_scripts
- widget_theysaidso_widget
- pzfm-activation
- pzfm_dashboard
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
- widget_recent-comments
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
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 43× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_footer() in wp-content/plugins/pz-frontend-manager/templates/footer.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/pz-frontend-manager/templates/nav-menu.tpl.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_url() in wp-content/plugins/pz-frontend-manager/templates/emails/email-lost-password.tpl.php:9
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/plugin.php' (include_path='.:/usr/share/php') in wp-content/plugins/pz-frontend-manager/templates/settings/license-key-settings.php on line 3
- > PHP Fatal error
Uncaught Error: Call to undefined function home_url() in wp-content/plugins/pz-frontend-manager/templates/registration-form.tpl.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function home_url() in wp-content/plugins/pz-frontend-manager/templates/emails/email-create-acount.tpl.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_nonce_field() in wp-content/plugins/pz-frontend-manager/templates/users/profile.tpl.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/pz-frontend-manager/templates/emails/email-proof-of-payment.tpl.php:26
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/pz-frontend-manager/templates/settings/logo-banner-settings.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_url() in wp-content/plugins/pz-frontend-manager/templates/emails/email-registration-confirmation.tpl.php:9
- > 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)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need to be fixed:
- Screenshots: Please add descriptions for these screenshots #1, #10, #2, #3, #4, #5, #6, #7, #8, #9 in pz-frontend-manager/assets to your readme.txt
pz-frontend-manager/pz-frontend-manager.php 85% from 13 tests
The primary PHP file in "PZ Frontend Manager" version 1.0.5 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Description: Please keep the plugin description shorter than 140 characters (currently 317 characters long)
- Domain Path: The domain path points to an invalid folder, "/languages/" does not exist
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
Everything looks great! No dangerous files found in this plugin15,568 lines of code in 81 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 50 | 196 | 135 | 6,423 |
| CSS | 13 | 2,525 | 100 | 6,128 |
| JavaScript | 18 | 87 | 170 | 3,017 |
PHP code Passed 2 tests
This is a very shot review 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.31 |
| Average class complexity | 46.50 |
| ▷ Minimum class complexity | 7.00 |
| ▷ Maximum class complexity | 139.00 |
| Average method complexity | 7.67 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 33.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 28 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 27 | 96.43% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 3.57% |
| Functions | 210 | |
| ▷ Named functions | 202 | 96.19% |
| ▷ Anonymous functions | 8 | 3.81% |
| Constants | 10 | |
| ▷ Global constants | 10 | 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
34 PNG files occupy 0.45MB with 0.12MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/email-icons/facebook.png | 1.86KB | 1.29KB | ▼ 30.34% |
| assets/images/icons/gbs-user-mngmt-icon.png | 2.70KB | 2.03KB | ▼ 24.75% |
| assets/images/icons/upload.png | 0.96KB | 0.84KB | ▼ 13.17% |
| assets/images/email-icons/youtube.png | 2.02KB | 1.34KB | ▼ 33.43% |
| assets/images/icons/gbs-posts-icon.png | 2.01KB | 1.50KB | ▼ 25.19% |