Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼1.92MB] [CPU: ▼54.34ms] Passed 4 tests
Server-side resources used by Stratus
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.07 ▼1.40 | 4.99 ▼36.51 |
| Dashboard /wp-admin | 2.09 ▼1.22 | 5.53 ▼42.12 |
| Posts /wp-admin/edit.php | 2.09 ▼1.27 | 7.16 ▼40.97 |
| Add New Post /wp-admin/post-new.php | 2.09 ▼3.80 | 6.20 ▼97.74 |
| Media Library /wp-admin/upload.php | 2.09 ▼1.14 | 6.17 ▼30.48 |
| Stratus Settings /wp-admin/options-general.php?page=stratus | 2.09 | 6.97 |
Server storage [IO: ▲1.16MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-comments |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by Stratus
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,922 ▲176 | 13.71 ▼0.97 | 6.71 ▲4.91 | 37.34 ▼2.22 |
| Dashboard /wp-admin | 2,214 ▲23 | 5.01 ▼0.79 | 98.39 ▼4.40 | 38.04 ▼7.46 |
| Posts /wp-admin/edit.php | 2,097 ▲8 | 2.05 ▲0.06 | 34.00 ▼1.18 | 30.37 ▼9.55 |
| Add New Post /wp-admin/post-new.php | 1,535 ▲21 | 23.35 ▲5.81 | 658.84 ▼61.42 | 54.68 ▼0.76 |
| Media Library /wp-admin/upload.php | 1,399 ▲8 | 4.18 ▲0.04 | 92.13 ▼7.06 | 42.58 ▼0.25 |
| Stratus Settings /wp-admin/options-general.php?page=stratus | 848 | 2.02 | 23.43 | 26.25 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- Uninstall procedure validation failed for this plugin
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the stratus handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Please fix the following server-side errors
- > GET request to /wp-admin/options-general.php?page=stratus
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the stratus handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 2 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=stratus
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
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
Please take a closer look at 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 get_option() in wp-content/plugins/stratus/wp-stratus.php:33
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There are user-side issues you should fix
- > GET request to /wp-admin/options-general.php?page=stratus
- > Network (severe)
https://stratus.soundcloud.com/stratus.js?ver=6.3.1 - Failed to load resource: net::ERR_NAME_NOT_RESOLVED
- > GET request to /wp-admin/options-general.php?page=stratus
- > Network (severe)
https://stratus.soundcloud.com/images/logo.png - Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that require attention:
- Screenshots: These screenshots do not have images: #1 (M83 - [ilovem83.com](http://ilovem83.com)), #2 (The Vaccines - [thevaccines.co.uk](http://thevaccines.co.uk)), #3 (Rokysopp - [rokysopp.com](http://rokysopp.com)), #4 (School of Seven Bells - [sviib.com](http://sviib.com))
stratus/wp-stratus.php 85% from 13 tests
The main file in "Stratus" v. 1.0.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("stratus.php" instead of "wp-stratus.php")
- Description: Keep the plugin description shorter than 140 characters (currently 204 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Success! There were no dangerous files found in this plugin63 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 34 | 25 | 63 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.38 |
| 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 | 5 | |
| ▷ Named functions | 5 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 5 | |
| ▷ Global constants | 5 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
4 PNG files occupy 1.15MB with 0.70MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 314.18KB | 125.09KB | ▼ 60.19% |
| screenshot-3.png | 284.52KB | 135.39KB | ▼ 52.41% |
| screenshot-4.png | 255.07KB | 94.86KB | ▼ 62.81% |
| screenshot-2.png | 327.44KB | 109.55KB | ▼ 66.54% |