Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.04MB] [CPU: ▼5.12ms] Passed 4 tests
A check of server-side resources used by Flogger
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.06 | 43.16 ▲1.52 |
| Dashboard /wp-admin | 3.36 ▲0.01 | 46.41 ▼12.18 |
| Posts /wp-admin/edit.php | 3.41 ▲0.05 | 44.22 ▼0.91 |
| Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 80.78 ▼5.02 |
| Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 34.73 ▼2.35 |
| Exercises /wp-admin/edit-tags.php?taxonomy=floggerexercise | 3.27 | 33.47 |
Server storage [IO: ▲0.28MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| db_upgraded |
| widget_recent-posts |
| widget_theysaidso_widget |
| widget_recent-comments |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for Flogger
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲33 | 14.74 ▲0.32 | 2.25 ▲0.38 | 42.36 ▲1.13 |
| Dashboard /wp-admin | 2,213 ▲28 | 4.90 ▼0.96 | 112.66 ▲1.73 | 43.18 ▼2.63 |
| Posts /wp-admin/edit.php | 2,125 ▲39 | 2.01 ▼0.00 | 36.82 ▼0.67 | 31.19 ▼3.20 |
| Add New Post /wp-admin/post-new.php | 6,211 ▲4,678 | 18.84 ▼4.26 | 924.69 ▲216.03 | 55.99 ▼5.76 |
| Media Library /wp-admin/upload.php | 1,395 ▲7 | 4.21 ▲0.03 | 100.50 ▼2.29 | 44.76 ▼2.37 |
| Exercises /wp-admin/edit-tags.php?taxonomy=floggerexercise | 1,237 | 2.26 | 29.60 | 30.25 |
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 does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following
- 3× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/flogger/inc/taxonomy.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/flogger/inc/taxonomy.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/flogger/inc/post.php:5
- > 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 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need to be fixed:
- Screenshots: Add images for these screenshots: #1 (Adding and editing in the new post taxonomy Exercises), #2 (Adding tags and exercise amounts to your daily post), #3 (What your visitors see on your posts)
flogger/flogger.php Passed 13 tests
The main file in "Flogger" v. 1.0.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
28 characters long description:
Fitness logger for WordPress
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Good job! No executable or dangerous file extensions detected175 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 40 | 21 | 175 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.24 |
| Average class complexity | 10.50 |
| ▷ Minimum class complexity | 4.00 |
| ▷ Maximum class complexity | 17.00 |
| Average method complexity | 2.27 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 8.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 15 | |
| ▷ Static methods | 2 | 13.33% |
| ▷ Public methods | 15 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
3 PNG files occupy 0.27MB with 0.18MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-3.png | 44.36KB | 14.36KB | ▼ 67.62% |
| screenshot-1.png | 170.31KB | 59.43KB | ▼ 65.11% |
| screenshot-2.png | 62.72KB | 19.96KB | ▼ 68.17% |