Benchmarks
Plugin footprint 83% 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 gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼6.33ms] Passed 4 tests
Analyzing server-side resources used by Mighty Content Locker
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 39.16 ▼6.59 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 45.79 ▼5.58 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 46.41 ▲0.21 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 81.89 ▼13.35 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 37.71 ▲3.63 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_recent-comments |
| db_upgraded |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Mighty Content Locker: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,852 ▲117 | 14.50 ▲0.03 | 2.18 ▲0.16 | 43.18 ▼5.33 |
| Dashboard /wp-admin | 2,224 ▲36 | 5.82 ▲0.96 | 101.42 ▼14.94 | 60.69 ▲14.17 |
| Posts /wp-admin/edit.php | 2,104 ▲15 | 2.02 ▼0.02 | 37.93 ▲0.58 | 34.60 ▼1.20 |
| Add New Post /wp-admin/post-new.php | 1,680 ▲163 | 22.41 ▲4.75 | 680.05 ▲3.72 | 56.84 ▼2.98 |
| Media Library /wp-admin/upload.php | 1,403 ▲12 | 4.12 ▼0.09 | 100.38 ▲7.33 | 74.70 ▲35.14 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
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
Good news, no errors were detected
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
Please fix the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/mighty-content-locker/wpmcl.php:12
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that need to be fixed:
- Contributors: Plugin contributors not specified
mighty-content-locker/wpmcl.php 85% from 13 tests
"Mighty Content Locker" version 1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please take the time to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 182 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("mighty-content-locker.php" instead of "wpmcl.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
No dangerous file extensions were detected110 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 19 | 10 | 110 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.37 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 9 | |
| ▷ Named functions | 9 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
3 PNG files occupy 0.05MB with 0.02MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 43.76KB | 15.50KB | ▼ 64.57% |
| wpmcl16.png | 0.67KB | 0.63KB | ▼ 6.39% |
| wpmcl.png | 4.38KB | 1.47KB | ▼ 66.29% |