Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.99ms] Passed 4 tests
Server-side resources used by Football Preloader
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 51.38 ▲13.87 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 52.05 ▼12.43 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 51.17 ▼2.95 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 135.86 ▲26.17 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 31.07 ▼10.43 |
Server storage [IO: ▲0.29MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_recent-posts |
| can_compress_scripts |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Football Preloader
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,822 ▲61 | 14.37 ▼0.36 | 2.55 ▲0.88 | 48.80 ▲6.32 |
| Dashboard /wp-admin | 2,189 ▲9 | 5.60 ▲0.05 | 125.06 ▲29.86 | 58.89 ▲19.62 |
| Posts /wp-admin/edit.php | 2,103 ▲6 | 1.95 ▼0.08 | 43.14 ▲5.71 | 40.21 ▲8.33 |
| Add New Post /wp-admin/post-new.php | 1,409 ▼119 | 17.93 ▼5.08 | 796.46 ▲119.12 | 63.10 ▲3.51 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.22 ▼0.02 | 103.86 ▼14.15 | 42.18 ▼11.32 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, 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 fix 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 add_action() in wp-content/plugins/football-preloader/football-loading.php:23
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 90% 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
Attributes that need to be fixed:
- Screenshots: Please a description for screenshot #1 in football-preloader/assets to your readme.txt
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== football-preloader ===)
football-preloader/football-loading.php 92% from 13 tests
"Football Preloader" version 1.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
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 ("football-preloader.php" instead of "football-loading.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
Success! There were no dangerous files found in this plugin80 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 1 | 3 | 0 | 55 |
| PHP | 1 | 9 | 12 | 25 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
| 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 | 3 | |
| ▷ Named functions | 3 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.29MB with 0.22MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| css/football.png | 263.58KB | 82.57KB | ▼ 68.67% |
| football.png | 30.43KB | 4.83KB | ▼ 84.11% |