Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.01MB] [CPU: ▼3.75ms] Passed 4 tests
This is a short check of server-side resources used by WordPress Server Load
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 40.26 ▼3.82 |
Dashboard /wp-admin | 3.26 ▼0.04 | 44.29 ▼0.79 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 43.17 ▼2.67 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 80.68 ▼7.72 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 38.50 ▲3.19 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 3 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_recent-posts |
widget_theysaidso_widget |
can_compress_scripts |
recovery_mode_email_last_sent |
db_upgraded |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WordPress Server Load
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,164 ▼582 | 12.45 ▼2.13 | 1.85 ▼0.24 | 42.42 ▼1.99 |
Dashboard /wp-admin | 1,573 ▼612 | 1.41 ▼4.49 | 15.92 ▼93.90 | 32.50 ▼7.48 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.01 ▲0.01 | 38.50 ▼0.66 | 43.59 ▲5.89 |
Add New Post /wp-admin/post-new.php | 1,667 ▲148 | 22.28 ▼0.80 | 660.36 ▲4.36 | 37.11 ▼17.69 |
Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.23 ▲0.04 | 95.32 ▼15.86 | 43.81 ▼8.30 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- This plugin did not uninstall successfully, leaving 7 options in the database
- db_upgraded
- recovery_mode_email_last_sent
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- 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
Everything seems fine, however this is by no means an exhaustive test
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
The following issues need your attention
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wordpress-server-load-monitor/wordpress-server-load.php:15
- > 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 87% from 29 tests
readme.txt 88% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need your attention:
- Plugin Name: Please specify the plugin name on the first line (
=== wordpress-server-load-monitor ===
) - Screenshots: Screenshot #1 (Wordpress Server Load Admin Widget) image missing
wordpress-server-load-monitor/wordpress-server-load.php 85% from 13 tests
The main PHP file in "WordPress Server Load" ver. 2.0 adds more information about the plugin and also serves as the entry point for this plugin
Please make the necessary changes and fix the following:
- Description: Please keep the plugin description shorter than 140 characters (currently 196 characters long)
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("wordpress-server-load-monitor.php" instead of "wordpress-server-load.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Everything looks great! No dangerous files found in this plugin134 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 13 | 12 | 134 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.09 |
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
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.02MB with 0.01MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 16.01KB | 7.92KB | ▼ 50.55% |