Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▼1.74MB] [CPU: ▼55.89ms] Passed 4 tests
Server-side resources used by BlueLevel 3D CSSProgress
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.28 ▼1.23 | 8.72 ▼34.38 |
Dashboard /wp-admin | 2.33 ▼1.06 | 10.06 ▼54.49 |
Posts /wp-admin/edit.php | 2.33 ▼1.07 | 10.65 ▼44.94 |
Add New Post /wp-admin/post-new.php | 2.32 ▼3.61 | 11.29 ▼89.74 |
Media Library /wp-admin/upload.php | 2.33 ▼0.95 | 10.96 ▼30.26 |
Server storage [IO: ▲0.06MB] [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 |
---|
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for BlueLevel 3D CSSProgress
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,874 ▲88 | 13.43 ▼1.13 | 8.43 ▲6.40 | 43.87 ▲0.82 |
Dashboard /wp-admin | 2,197 ▲17 | 5.63 ▼0.02 | 91.28 ▼1.13 | 40.33 ▼0.78 |
Posts /wp-admin/edit.php | 2,102 ▼1 | 1.97 ▲0.02 | 34.97 ▼3.31 | 34.34 ▼0.34 |
Add New Post /wp-admin/post-new.php | 1,538 ▲12 | 18.20 ▼4.83 | 637.56 ▼35.68 | 71.55 ▲21.89 |
Media Library /wp-admin/upload.php | 1,399 ▲2 | 4.20 ▲0.09 | 103.56 ▼8.48 | 44.67 ▲2.01 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- This plugin did not uninstall without warnings or errors
- > User notice in wp-includes/functions.php+5905
Function wp_register_style 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 BL_CSSP handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting 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 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
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/bluelevel-3d-cssprogress-bar/index.php:19
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
10 plugin tags: progress, light, plugins, css, progress bar...
bluelevel-3d-cssprogress-bar/index.php 85% from 13 tests
The principal PHP file in "BlueLevel 3D CSSProgress" v. 1.0 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Description: Keep the plugin description shorter than 140 characters (currently 150 characters long)
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("bluelevel-3d-cssprogress-bar.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
There were no executable files found in this plugin66 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 18 | 19 | 64 |
CSS | 1 | 0 | 0 | 1 |
JavaScript | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for 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 | 5 | |
▷ Named functions | 5 | 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
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
tinymce/mce.png | 1.50KB | 0.73KB | ▼ 50.98% |