Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▼1.96MB] [CPU: ▼53.00ms] Passed 4 tests
An overview of server-side resources used by SS Preloader
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.03 ▼1.43 | 3.84 ▼32.31 |
| Dashboard /wp-admin | 2.05 ▼1.26 | 5.83 ▼45.48 |
| Posts /wp-admin/edit.php | 2.05 ▼1.31 | 5.74 ▼40.59 |
| Add New Post /wp-admin/post-new.php | 2.05 ▼3.84 | 5.01 ▼93.62 |
| Media Library /wp-admin/upload.php | 2.05 ▼1.18 | 5.35 ▼28.87 |
Server storage [IO: ▲0.44MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 8 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_recent-posts |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| db_upgraded |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for SS Preloader
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,007 ▲272 | 14.94 ▲0.56 | 1.90 ▲0.41 | 48.11 ▲5.68 |
| Dashboard /wp-admin | 2,380 ▲192 | 6.64 ▲1.74 | 132.93 ▲28.97 | 40.22 ▼0.39 |
| Posts /wp-admin/edit.php | 2,289 ▲200 | 3.63 ▲1.62 | 53.52 ▲11.98 | 34.65 ▼2.98 |
| Add New Post /wp-admin/post-new.php | 1,547 ▲19 | 23.53 ▲0.38 | 653.22 ▲58.53 | 30.22 ▼26.24 |
| Media Library /wp-admin/upload.php | 1,428 ▲43 | 4.35 ▲0.14 | 81.46 ▼21.05 | 40.46 ▼4.84 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- The plugin did not uninstall gracefully
- > 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 JavaScript handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
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
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/ss-preloader/ss-preloader.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
5 plugin tags: prealoader, pre-loader, pre-loading, ss preloader, loader
ss-preloader/ss-preloader.php 92% from 13 tests
The main PHP script in "SS Preloader" version 1.0 is automatically included on every request by WordPress
Please make the necessary changes and fix the following:
- Description: Please don't use more than 140 characters for the plugin description (currently 338 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
No dangerous file extensions were detected117 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 100 | 21 | 106 |
| JavaScript | 2 | 0 | 3 | 11 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.16 |
| 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 | 7 | |
| ▷ Named functions | 7 | 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
3 PNG files occupy 0.42MB with 0.25MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-1.png | 5.11KB | 1.69KB | ▼ 66.88% |
| assets/banner-772x250..png | 413.08KB | 118.62KB | ▼ 71.28% |
| assets/icon-128x128.png | 6.96KB | 4.08KB | ▼ 41.42% |