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
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼8.63ms] Passed 4 tests
A check of server-side resources used by WProgress
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 37.24 ▼11.66 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 42.25 ▼3.49 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 45.80 ▼2.28 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 83.48 ▼17.09 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.63 ▲2.28 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_recent-posts |
| db_upgraded |
| can_compress_scripts |
| widget_theysaidso_widget |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WProgress
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.59 ▼0.76 | 5.29 ▲3.69 | 40.89 ▲1.42 |
| Dashboard /wp-admin | 2,203 ▲15 | 5.83 ▼0.06 | 107.38 ▼8.57 | 37.70 ▼3.04 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.03 ▲0.02 | 40.21 ▲0.25 | 35.79 ▲1.24 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼19 | 17.80 ▼5.48 | 671.69 ▲86.39 | 61.12 ▲6.42 |
| Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.15 ▼0.02 | 107.35 ▲2.84 | 47.20 ▲1.82 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- 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
Good news, no errors were detected
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 take a closer look at the following
- 3× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/wprogress-bar/filters.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wprogress-bar/actions.php:9
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wprogress-bar/actions.php:9
- > 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)
No browser errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
3 plugin tags: posts, page, post
wprogress-bar/wprogress.php 92% from 13 tests
The main PHP script in "WProgress" version 0.1 is automatically included on every request by WordPress
It is important to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("wprogress-bar.php" instead of "wprogress.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
Good job! No executable or dangerous file extensions detected91 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 1 | 11 | 0 | 50 |
| CSS | 1 | 7 | 6 | 23 |
| PHP | 3 | 2 | 9 | 17 |
| Markdown | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.10 |
| 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 | 2 | |
| ▷ Named functions | 2 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
There were not PNG files found in your plugin