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 successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼2.50ms] Passed 4 tests
This is a short check of server-side resources used by MTMO
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 42.97 ▲2.04 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 45.90 ▼3.06 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 46.36 ▼2.98 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 88.26 ▼6.01 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 38.76 ▲4.34 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| theysaidso_admin_options |
| widget_recent-comments |
| db_upgraded |
| can_compress_scripts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for MTMO
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,815 ▲80 | 14.68 ▲0.07 | 1.72 ▼0.04 | 44.03 ▲3.12 |
| Dashboard /wp-admin | 2,218 ▲27 | 5.80 ▼0.10 | 103.21 ▲0.06 | 65.83 ▲24.97 |
| Posts /wp-admin/edit.php | 2,104 ▲15 | 1.99 ▼0.02 | 36.11 ▲2.17 | 32.21 ▼0.10 |
| Add New Post /wp-admin/post-new.php | 1,681 ▲164 | 22.33 ▲4.57 | 622.34 ▼14.15 | 41.65 ▼24.35 |
| Media Library /wp-admin/upload.php | 1,403 ▲15 | 4.20 ▼0.08 | 120.98 ▲15.78 | 45.42 ▼6.89 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- 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
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Almost there! Just fix the following items
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/mtmo-b-v/content/widgets.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/mtmo-b-v/mtmo-plugin.php:12
- > 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 on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
4 plugin tags: mtmo, reviews, klantbeoordelingen, widget
mtmo-b-v/mtmo-plugin.php 92% from 13 tests
Analyzing the main PHP file in "MTMO" version 1.1
Please make the necessary changes and fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("mtmo-b-v.php" instead of "mtmo-plugin.php")
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
Everything looks great! No dangerous files found in this plugin127 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 14 | 9 | 127 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| 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 | 6 | |
| ▷ Named functions | 6 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/icon.png | 2.45KB | 0.67KB | ▼ 72.52% |