Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▼0.01MB] [CPU: ▼5.18ms] Passed 4 tests
Analyzing server-side resources used by NPS Monitoring
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 41.82 ▲2.39 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 48.33 ▼15.94 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 49.66 ▲1.49 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 92.78 ▼7.41 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.70 ▲1.13 |
| NPS Monitoring /wp-admin/options-general.php?page=npsm-plugin-options | 3.18 | 31.41 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for NPS Monitoring
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,793 ▲32 | 14.27 ▼0.25 | 1.67 ▼0.12 | 40.07 ▼4.08 |
| Dashboard /wp-admin | 2,199 ▲22 | 5.66 ▲0.10 | 90.60 ▼7.98 | 41.10 ▲4.15 |
| Posts /wp-admin/edit.php | 2,104 ▲1 | 1.94 ▼0.07 | 38.98 ▲2.20 | 35.34 ▼0.90 |
| Add New Post /wp-admin/post-new.php | 1,529 ▲1 | 23.54 ▲0.56 | 694.29 ▲77.97 | 55.82 ▲1.40 |
| Media Library /wp-admin/upload.php | 1,404 ▲4 | 4.26 ▲0.12 | 112.15 ▲15.28 | 47.69 ▲5.92 |
| NPS Monitoring /wp-admin/options-general.php?page=npsm-plugin-options | 989 | 3.05 | 70.12 | 28.94 |
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
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Smoke test failed, please fix the following
- > GET request to /wp-admin/options-general.php?page=npsm-plugin-options
- > Warning in wp-content/plugins/nps-monitoring/index.php+220
Use of undefined constant URL_ROOT - assumed 'URL_ROOT' (this will throw an Error in a future version of PHP)
SRP Passed 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
Congratulations! This plugin passed the SRP test
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Please fix the following user-side errors
- > GET request to /wp-admin/options-general.php?page=npsm-plugin-options
- > Network (severe)
https://www.dimbal.com/dbm/banner/dbm.js?ver=6.3.1 - Failed to load resource: the server responded with a status of 404 ()
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that need to be fixed:
- Screenshots: Please a description for screenshot #3 in nps-monitoring/assets to your readme.txt
nps-monitoring/index.php 92% from 13 tests
Analyzing the main PHP file in "NPS Monitoring" version 2.1.2
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("nps-monitoring.php" instead of "index.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
No dangerous file extensions were detected133 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 46 | 100 | 133 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.30 |
| 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 | 4 | |
| ▷ Named functions | 4 | 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
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.04MB with 0.02MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| guage_180.png | 36.56KB | 12.75KB | ▼ 65.11% |