Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.07MB] [CPU: ▼152.47ms] Passed 4 tests
A check of server-side resources used by Reading progressbar
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.86 ▲0.13 | 41.44 ▲16.55 |
Dashboard /wp-admin | 3.13 ▲0.07 | 52.79 ▼9.52 |
Posts /wp-admin/edit.php | 3.21 ▲0.10 | 53.07 ▼5.49 |
Add New Post /wp-admin/post-new.php | 5.48 ▲0.05 | 97.19 ▼587.03 |
Media Library /wp-admin/upload.php | 3.07 ▲0.06 | 37.08 ▼7.85 |
Reading progressbar /wp-admin/options-general.php?page=reading-progressbar | 3.04 | 33.29 |
Server storage [IO: ▲0.56MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 23 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for Reading progressbar
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,725 ▲119 | 16.20 ▲0.66 | 14.17 ▲1.97 | 52.94 ▼10.00 |
Dashboard /wp-admin | 2,989 ▲61 | 6.53 ▲0.49 | 144.89 ▼47.06 | 118.81 ▼7.79 |
Posts /wp-admin/edit.php | 2,761 ▲22 | 2.79 ▲0.08 | 70.16 ▼8.33 | 96.81 ▼10.22 |
Add New Post /wp-admin/post-new.php | 1,643 ▼40 | 22.18 ▲6.49 | 294.68 ▼124.17 | 139.25 ▲21.57 |
Media Library /wp-admin/upload.php | 1,833 ▲26 | 5.35 ▲0.33 | 132.44 ▼52.49 | 123.72 ▼19.92 |
Reading progressbar /wp-admin/options-general.php?page=reading-progressbar | 1,611 | 2.93 | 86.69 | 84.23 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Uninstaller ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not 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
The following issues need your attention
- 2× 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/reading-progress-bar/public/rp-public.php:51
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/reading-progress-bar/admin/rp-admin.php:21
- > 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, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Please fix the following attributes:
- Tags: There are too many tags (12 tag instead of maximum 10)
reading-progress-bar/reading-progressbar.php 92% from 13 tests
"Reading progressbar" version 1.3's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("reading-progress-bar.php" instead of "reading-progressbar.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 detected511 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 49 | 87 | 288 |
PO File | 2 | 51 | 53 | 160 |
JavaScript | 2 | 11 | 6 | 50 |
CSS | 1 | 0 | 3 | 13 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.37 |
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 | 15 | |
▷ Named functions | 15 | 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 50% from 2 tests
Image compression 50% from 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
6 PNG files occupy 0.51MB with 0.34MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-1.png | 135.10KB | 36.91KB | ▼ 72.68% |
assets/icon-128x128.png | 5.41KB | 1.91KB | ▼ 64.70% |
assets/banner-772x250.png | 21.09KB | 8.28KB | ▼ 60.73% |
assets/icon-256x256.png | 7.96KB | 2.83KB | ▼ 64.41% |
assets/screenshot-2.png | 318.16KB | 87.64KB | ▼ 72.45% |