Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
You still need to fix the following installer errors
- The plugin did not install without errors
- > Deprecated in wp-content/plugins/sidepost/zmsrp.php+36
Methods with the same name as their class will not be constructors in a future version of PHP; srp_plugin has a deprecated constructor
Server metrics [RAM: ▼1.85MB] [CPU: ▼58.33ms] Passed 4 tests
A check of server-side resources used by SidePost
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.13 ▼1.33 | 5.74 ▼40.27 |
Dashboard /wp-admin | 2.15 ▼1.15 | 6.49 ▼48.37 |
Posts /wp-admin/edit.php | 2.15 ▼1.20 | 8.09 ▼48.24 |
Add New Post /wp-admin/post-new.php | 2.15 ▼3.73 | 6.50 ▼96.42 |
Media Library /wp-admin/upload.php | 2.15 ▼1.07 | 5.29 ▼34.64 |
Server storage [IO: ▲0.13MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 7 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_recent-comments |
widget_theysaidso_widget |
can_compress_scripts |
theysaidso_admin_options |
widget_srp_plugin |
widget_recent-posts |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for SidePost
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,793 ▲22 | 14.22 ▲0.08 | 1.57 ▼0.26 | 43.44 ▼0.03 |
Dashboard /wp-admin | 2,197 ▲20 | 5.65 ▲0.01 | 91.25 ▲3.27 | 37.72 ▼5.49 |
Posts /wp-admin/edit.php | 2,102 ▼1 | 1.98 ▲0.02 | 39.09 ▼3.55 | 34.58 ▼2.61 |
Add New Post /wp-admin/post-new.php | 1,530 ▼7 | 23.06 ▲4.68 | 599.50 ▼12.38 | 50.15 ▼13.15 |
Media Library /wp-admin/upload.php | 1,405 ▲5 | 4.21 ▼0.02 | 93.88 ▼12.00 | 43.92 ▼5.55 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- Uninstall procedure validation failed for this plugin
- > Deprecated in wp-content/plugins/sidepost/zmsrp.php+36
Methods with the same name as their class will not be constructors in a future version of PHP; srp_plugin has a deprecated constructor
- This plugin did not uninstall successfully, leaving 7 options in the database
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- widget_srp_plugin
- theysaidso_admin_options
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
Please take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/sidepost/zmsrp.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
7 plugin tags: sidebar, news, categories, simple, thumbnails...
sidepost/zmsrp.php 92% from 13 tests
The principal PHP file in "SidePost" v. 1.0.7 is loaded by WordPress automatically on each request
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("sidepost.php" instead of "zmsrp.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected163 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 5 | 22 | 142 |
CSS | 2 | 0 | 0 | 21 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.09 |
Average class complexity | 10.00 |
▷ Minimum class complexity | 10.00 |
▷ Maximum class complexity | 10.00 |
Average method complexity | 3.25 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 8.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 4 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 4 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 5 | |
▷ Named functions | 3 | 60.00% |
▷ Anonymous functions | 2 | 40.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
All PNG images should be compressed to minimize bandwidth usage for end users
1 PNG file occupies 0.10MB with 0.06MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 106.45KB | 41.07KB | ▼ 61.42% |