Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.60MB] [CPU: ▲0.94ms] Passed 4 tests
Analyzing server-side resources used by MyBookProgress by Stormhill Media
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.12 ▲0.66 | 48.31 ▲6.00 |
Dashboard /wp-admin | 3.93 ▲0.63 | 48.70 ▼0.82 |
Posts /wp-admin/edit.php | 3.98 ▲0.63 | 52.70 ▲7.52 |
Add New Post /wp-admin/post-new.php | 6.47 ▲0.59 | 89.11 ▼5.49 |
Media Library /wp-admin/upload.php | 3.79 ▲0.56 | 40.49 ▲4.08 |
Server storage [IO: ▲1.46MB] [DB: ▲0.01MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 109 new files
Database: 1 new table, 9 new options
New tables |
---|
wp_mbp_progress |
New WordPress options |
---|
db_upgraded |
widget_recent-comments |
can_compress_scripts |
mbp_settings |
theysaidso_admin_options |
widget_recent-posts |
widget_theysaidso_widget |
widget_mbp_widget |
mbp_tracking_data |
Browser metrics Passed 4 tests
MyBookProgress by Stormhill Media: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,931 ▲196 | 13.62 ▼0.97 | 8.13 ▲6.14 | 37.63 ▼14.94 |
Dashboard /wp-admin | 2,219 ▲34 | 5.88 ▲0.92 | 99.42 ▼16.82 | 38.81 ▼6.60 |
Posts /wp-admin/edit.php | 2,107 ▲18 | 2.10 ▲0.10 | 40.57 ▲4.75 | 33.32 ▼0.66 |
Add New Post /wp-admin/post-new.php | 1,640 ▲107 | 22.97 ▼0.08 | 620.84 ▼33.68 | 58.39 ▲2.79 |
Media Library /wp-admin/upload.php | 1,407 ▲19 | 4.17 ▼0.01 | 98.84 ▲4.00 | 42.60 ▲1.77 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- The uninstall procedure failed, leaving 1 table in the database
- wp_mbp_progress
- The uninstall procedure has failed, leaving 9 options in the database
- widget_recent-comments
- mbp_settings
- widget_recent-posts
- can_compress_scripts
- widget_mbp_widget
- mbp_tracking_data
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
Smoke tests 50% 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 0% 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 fix the following
- 8× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/mybookprogress/includes/templates/progress_types/percent_display.php
- > /wp-content/plugins/mybookprogress/includes/templates/progress_types/percent_editor.php
- > /wp-content/plugins/mybookprogress/includes/templates/book_progress/overview_book.php
- > /wp-content/plugins/mybookprogress/includes/templates/book_setup/phase_editor.php
- > /wp-content/plugins/mybookprogress/includes/templates/book_progress/book_tabs.php
- > /wp-content/plugins/mybookprogress/includes/templates/book_progress/progress_header.php
- > /wp-content/plugins/mybookprogress/includes/templates/book_progress/book_progress.php
- > /wp-content/plugins/mybookprogress/includes/templates/book_progress/progress_more.php
- 49× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/mybookprogress/includes/templates/book_progress/progress_delete_confirm.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/mybookprogress/includes/templates/book_setup/mybooktable_step.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/mybookprogress/includes/templates/help/search.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/mybookprogress/includes/templates/book_setup/display_step.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/mybookprogress/includes/templates/book_setup/phase_details.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/mybookprogress/includes/functions.php:355
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/mybookprogress/includes/templates/upgrade_tab/upgrade_tab.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/mybookprogress/includes/templates/book_setup/phase_template.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/mybookprogress/includes/templates/help/enable_tracking_modal.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/mybookprogress/includes/functions.php:355
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need to be fixed:
- Tags: You are using too many tags: 12 tag instead of maximum 10
mybookprogress/mybookprogress.php 92% from 13 tests
"MyBookProgress by Stormhill Media" version 1.0.7's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Description: Keep the plugin description shorter than 140 characters (currently 167 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Everything looks great! No dangerous files found in this plugin9,533 lines of code in 75 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 10 | 743 | 193 | 5,163 |
PHP | 57 | 400 | 78 | 3,212 |
CSS | 8 | 181 | 100 | 1,158 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.32 |
Average class complexity | 17.00 |
▷ Minimum class complexity | 17.00 |
▷ Maximum class complexity | 17.00 |
Average method complexity | 4.20 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 11.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 5 | |
▷ Static methods | 1 | 20.00% |
▷ Public methods | 5 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 149 | |
▷ Named functions | 149 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 2 | |
▷ Global constants | 2 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
22 PNG files occupy 0.65MB with 0.28MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
img/admin/speech2.png | 36.55KB | 18.68KB | ▼ 48.90% |
img/upgrade/nudges.png | 41.62KB | 13.76KB | ▼ 66.94% |
img/admin/default_avatar.png | 0.63KB | 0.48KB | ▼ 23.22% |
img/frontend/nudge_nudged.png | 1.32KB | 1.25KB | ▼ 5.33% |
img/upgrade/email-updates.png | 104.58KB | 29.64KB | ▼ 71.66% |