Benchmarks
Plugin footprint 48% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.06MB] [CPU: ▼152.66ms] Passed 4 tests
Server-side resources used by Privilege Menu
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.87 ▲0.03 | 27.90 ▲6.26 |
Dashboard /wp-admin | 3.17 ▲0.11 | 41.15 ▲5.73 |
Posts /wp-admin/edit.php | 3.22 ▲0.11 | 35.53 ▲5.17 |
Add New Post /wp-admin/post-new.php | 5.47 ▲0.03 | 70.80 ▼623.13 |
Media Library /wp-admin/upload.php | 3.06 ▲0.05 | 24.14 ▲1.61 |
Install Plugins /wp-admin/plugins.php?page=fuzzguard-plugin-manager | 3.12 | 21.44 |
Server storage [IO: ▲0.17MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 16 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
A check of browser resources used by Privilege Menu
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,706 ▲105 | 15.95 ▲0.22 | 5.41 ▲0.41 | 80.86 ▲4.75 |
Dashboard /wp-admin | 2,973 ▲77 | 6.12 ▼0.04 | 116.14 ▼17.24 | 185.07 ▲12.03 |
Posts /wp-admin/edit.php | 2,792 ▲55 | 3.25 ▲0.01 | 64.41 ▲2.68 | 152.08 ▲14.94 |
Add New Post /wp-admin/post-new.php | 3,767 ▼40 | 18.72 ▼0.05 | 439.09 ▼17.15 | 159.50 ▼9.80 |
Media Library /wp-admin/upload.php | 1,799 ▲47 | 5.56 ▲0.08 | 150.52 ▲3.33 | 204.12 ▲18.04 |
Install Plugins /wp-admin/plugins.php?page=fuzzguard-plugin-manager | 1,296 | 2.41 | 55.38 | 124.88 |
Uninstaller [IO: ▲0.17MB] [DB: ▲0.00MB] 25% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attentionThis plugin does not fully uninstall, leaving 1 option in the database
- This plugin cannot be uninstalled
- > Error in wp-content/plugins/privilege-menu/privMenu.php+54
Cannot declare class privMenu, because the name is already in use
- Incomplete uninstall procedure, leaving 16 files (0.17MB) in the plugin directory
- (new file) customWalker.php
- (new file) lang/privilege-menu-fr_FR.po
- (new file) lang/privilege-menu-sr_RS.mo
- (new file) lang/privilege-menu-fr_FR.mo
- (new file) lang/privilege-menu-de_DE.mo
- (new file) lang/privilege-menu-es_ES.po
- (new file) lang/privilege-menu-es_ES.mo
- (new file) class-tgm-plugin-activation.php
- (new file) lang/privilege-menu-sr_RS.po
- (new file) lang/privilege-menu-de_DE.po
- ...
- recovery_mode_email_last_sent
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
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
Please fix the following items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function did_action() in wp-content/plugins/privilege-menu/class-tgm-plugin-activation.php:2109
- > 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)
There were no browser issues found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
10 plugin tags: menu, menus, login, restriction, permission...
privilege-menu/privMenu.php 92% from 13 tests
"Privilege Menu" version 1.8.4's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("privilege-menu.php" instead of "privMenu.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
There were no executable files found in this plugin2,279 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 592 | 1,811 | 2,138 |
PO File | 5 | 29 | 29 | 141 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.47 |
Average class complexity | 43.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 206.00 |
Average method complexity | 4.47 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 34.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 9 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 9 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 109 | |
▷ Static methods | 5 | 4.59% |
▷ Public methods | 86 | 78.90% |
▷ Protected methods | 23 | 21.10% |
▷ Private methods | 0 | 0.00% |
Functions | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 3 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 3 | 100.00% |
▷ Public constants | 3 | 100.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
No PNG images were found in this plugin