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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.01MB] [CPU: ▼7.27ms] Passed 4 tests
Server-side resources used by Sweet Sharmin Preloader
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 38.10 ▼3.65 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 50.54 ▼10.23 |
| Posts /wp-admin/edit.php | 3.37 ▲0.00 | 46.05 ▼2.40 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.00 | 79.26 ▼12.79 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.00 | 35.06 ▲1.61 |
Server storage [IO: ▲0.11MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 8 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| can_compress_scripts |
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Sweet Sharmin Preloader: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,903 ▲117 | 13.51 ▼0.98 | 9.82 ▲7.88 | 42.18 ▼2.30 |
| Dashboard /wp-admin | 2,195 ▲18 | 5.49 ▼0.18 | 98.90 ▲12.02 | 41.45 ▼2.57 |
| Posts /wp-admin/edit.php | 2,100 ▲3 | 1.99 ▲0.02 | 33.93 ▼4.72 | 36.23 ▼3.22 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.02 ▼0.62 | 643.72 ▼14.26 | 50.57 ▼4.19 |
| Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.19 ▲0.03 | 102.25 ▼3.46 | 48.34 ▲1.22 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_recent-comments
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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Almost there! Just fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/sweet-sharmin-preloader/sweet_sharmin_preloader.php:14
- > 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 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that require attention:
- Screenshots: Screenshot #1 (Screenshot 1) image not found
- Contributors: Plugin contributors field is missing
sweet-sharmin-preloader/sweet_sharmin_preloader.php 92% from 13 tests
The entry point to "Sweet Sharmin Preloader" version 1.0 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("sweet-sharmin-preloader.php" instead of "sweet_sharmin_preloader.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
No dangerous file extensions were detected48 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 4 | 12 | 29 |
| CSS | 1 | 1 | 0 | 19 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.00 |
| 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
3 PNG files occupy 0.07MB with 0.05MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/banner-772x250.png | 43.34KB | 18.81KB | ▼ 56.58% |
| images/bg.png | 1.36KB | 0.34KB | ▼ 74.93% |
| assets/Screenshot-1.png | 30.86KB | 9.55KB | ▼ 69.06% |