Benchmarks
Plugin footprint 65% 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.26MB] [CPU: ▲0.28ms] Passed 4 tests
Analyzing server-side resources used by Progress Tracker
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.86 ▲0.39 | 49.34 ▲0.23 |
Dashboard /wp-admin | 3.54 ▲0.24 | 68.03 ▲0.41 |
Posts /wp-admin/edit.php | 3.66 ▲0.30 | 53.99 ▲1.30 |
Add New Post /wp-admin/post-new.php | 6.15 ▲0.26 | 98.71 ▼0.82 |
Media Library /wp-admin/upload.php | 3.47 ▲0.23 | 43.02 ▲4.14 |
Progress Tracker /wp-admin/tools.php?page=ptracker-settings | 3.44 | 40.85 |
Server storage [IO: ▲0.34MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 35 new files
Database: 1 new table, 8 new options
New tables |
---|
wp_as_progress_tracker_users |
New WordPress options |
---|
widget_recent-posts |
widget_ptracker_widget |
as_progress_tracker_ops |
widget_recent-comments |
theysaidso_admin_options |
widget_theysaidso_widget |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
Progress Tracker: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,936 ▲175 | 13.46 ▼0.71 | 9.29 ▲7.45 | 46.05 ▼0.97 |
Dashboard /wp-admin | 2,196 ▲19 | 5.62 ▲0.08 | 90.83 ▼10.41 | 41.64 ▼0.28 |
Posts /wp-admin/edit.php | 2,104 ▲4 | 2.16 ▲0.18 | 37.10 ▲0.42 | 36.48 ▼0.96 |
Add New Post /wp-admin/post-new.php | 1,536 ▲10 | 23.12 ▲0.04 | 661.61 ▼13.56 | 66.29 ▲5.41 |
Media Library /wp-admin/upload.php | 1,404 ▲7 | 4.26 ▲0.05 | 101.64 ▼9.98 | 46.16 ▼3.13 |
Progress Tracker /wp-admin/tools.php?page=ptracker-settings | 1,476 | 2.22 | 45.92 | 60.85 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- Zombie tables were found after uninstall: 1 table
- wp_as_progress_tracker_users
- This plugin did not uninstall successfully, leaving 8 options in the database
- widget_ptracker_widget
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- as_progress_tracker_ops
- can_compress_scripts
- widget_recent-posts
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
These errors were triggered by the plugin
- > GET request to /wp-admin/tools.php?page=ptracker-settings
- > Notice in wp-content/plugins/progress-tracker/settings-tabs.php+217
Trying to get property 'ID' of non-object
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
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/progress-tracker/progress-tracker.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 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
4 plugin tags: academic, progression, pages, progress
progress-tracker/progress-tracker.php Passed 13 tests
The entry point to "Progress Tracker" version 0.9.3 is a PHP file that has certain tags in its header comment area
81 characters long description:
Keep track of your progress through a site, allowing you to mark pages as 'read'.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected6,802 lines of code in 18 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 6 | 106 | 44 | 3,344 |
JavaScript | 4 | 346 | 180 | 1,751 |
PHP | 8 | 598 | 225 | 1,707 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.29 |
Average class complexity | 36.00 |
▷ Minimum class complexity | 8.00 |
▷ Maximum class complexity | 60.00 |
Average method complexity | 4.18 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 49.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 4 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 4 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 44 | |
▷ Static methods | 11 | 25.00% |
▷ Public methods | 44 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 4 | |
▷ Named functions | 4 | 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 Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
15 PNG files occupy 0.09MB with 0.04MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/buttons/button1_next.png | 5.12KB | 2.69KB | ▼ 47.55% |
images/buttons/button2_back.png | 5.09KB | 2.65KB | ▼ 47.99% |
css/images/slidebutton-red.png | 2.95KB | 2.06KB | ▼ 30.35% |
images/buttons/button3_back.png | 8.60KB | 4.28KB | ▼ 50.27% |
css/images/slidebutton-green.png | 2.72KB | 2.03KB | ▼ 25.47% |