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.04MB] [CPU: ▼298.39ms] Passed 4 tests
A check of server-side resources used by Content Progress
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.53 ▲0.02 | 55.91 ▲4.69 |
| Dashboard /wp-admin | 3.50 ▲0.09 | 31.83 ▼2.87 |
| Posts /wp-admin/edit.php | 3.72 ▲0.08 | 36.11 ▼0.76 |
| Add New Post /wp-admin/post-new.php | 6.96 ▼0.01 | 98.31 ▼1,188.27 |
| Media Library /wp-admin/upload.php | 3.38 ▲0.09 | 25.00 ▼1.65 |
| Content Progress /wp-admin/options-general.php?page=content-progress/content-progress.php | 3.38 | 24.62 |
Server storage [IO: ▲0.18MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 39 new files
Database: no new tables, 2 new options
| New WordPress options |
|---|
| cp_version |
| cp_statuses |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Content Progress
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,771 ▲17 | 15.89 ▼0.19 | 5.74 ▼0.18 | 2.39 ▼0.15 |
| Dashboard /wp-admin | 2,914 ▲53 | 6.12 ▼0.02 | 116.79 ▼24.09 | 156.56 ▼12.84 |
| Posts /wp-admin/edit.php | 2,782 ▲91 | 3.37 ▲0.13 | 62.21 ▼1.90 | 138.42 ▼2.95 |
| Add New Post /wp-admin/post-new.php | 1,746 ▲27 | 17.86 ▼4.55 | 433.52 ▲6.84 | 172.25 ▲15.30 |
| Media Library /wp-admin/upload.php | 1,703 ▲8 | 5.57 ▲0.02 | 134.08 ▲0.42 | 186.20 ▼2.89 |
| Content Progress /wp-admin/options-general.php?page=content-progress/content-progress.php | 2,090 | 3.87 | 103.74 | 208.08 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 2 options
- cp_version
- cp_statuses
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following items
- 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/content-progress/content-progress.php:32
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Please fix the following attributes:
- Tags: Please reduce the number of tags, currently 12 tag instead of maximum 10
content-progress/content-progress.php Passed 13 tests
The main PHP file in "Content Progress" ver. 1.3.13 adds more information about the plugin and also serves as the entry point for this plugin
106 characters long description:
Adds a column to each post/page or custom post type indicating whether content has been added to the page.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Success! There were no dangerous files found in this plugin1,088 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 75 | 44 | 649 |
| PO File | 5 | 163 | 168 | 373 |
| CSS | 1 | 10 | 0 | 43 |
| JavaScript | 1 | 3 | 8 | 23 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.36 |
| 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 | 33 | |
| ▷ Named functions | 33 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
21 PNG files occupy 0.05MB with 0.01MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/idea.png | 2.15KB | 1.61KB | ▼ 25.10% |
| images/incomplete.png | 1.05KB | 0.87KB | ▼ 17.69% |
| screenshot-1.png | 19.77KB | 19.82KB | 0.00% |
| images/questions.png | 2.30KB | 1.75KB | ▼ 24.03% |
| images/star.png | 1.71KB | 1.52KB | ▼ 10.91% |