Benchmarks
Plugin footprint 83% from 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 gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼11.42ms] Passed 4 tests
This is a short check of server-side resources used by Offline Updater
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.01 | 39.38 ▼0.91 |
| Dashboard /wp-admin | 3.32 ▼0.02 | 47.01 ▼19.15 |
| Posts /wp-admin/edit.php | 3.37 ▲0.02 | 45.08 ▼4.35 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 82.07 ▼21.26 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 33.57 ▲0.44 |
| Offline Updater /wp-admin/index.php?page=offline-updater | 3.22 | 30.44 |
Server storage [IO: ▲0.30MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Offline Updater
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲33 | 13.27 ▼0.98 | 1.82 ▼0.24 | 44.42 ▲1.92 |
| Dashboard /wp-admin | 2,210 ▲19 | 5.79 ▲0.89 | 97.70 ▼6.80 | 40.58 ▲0.61 |
| Posts /wp-admin/edit.php | 2,096 ▲4 | 1.99 ▼0.00 | 35.12 ▼3.18 | 32.15 ▼1.51 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲2 | 23.10 ▼0.11 | 659.71 ▼43.41 | 52.66 ▼0.16 |
| Media Library /wp-admin/upload.php | 1,392 ▲7 | 4.21 ▼0.05 | 94.48 ▼13.21 | 41.94 ▼0.51 |
| Offline Updater /wp-admin/index.php?page=offline-updater | 779 | 2.02 | 24.17 | 27.20 |
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
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
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 take a closer look at the following
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function is_multisite() in wp-content/plugins/offline-updater/offline-updater.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that need to be fixed:
- Screenshots: Screenshot #1 (setting) image not found
offline-updater/offline-updater.php 92% from 13 tests
The primary PHP file in "Offline Updater" version 1.3 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Description: Please don't use more than 140 characters for the plugin description (currently 204 characters long)
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
Good job! No executable or dangerous file extensions detected70 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 9 | 8 | 70 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.44 |
| Average class complexity | 15.00 |
| ▷ Minimum class complexity | 15.00 |
| ▷ Maximum class complexity | 15.00 |
| Average method complexity | 5.67 |
| ▷ Minimum method complexity | 2.00 |
| ▷ Maximum method complexity | 13.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 | 3 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 3 | 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 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.29MB with 0.29MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| (invalid) screenshot-1.png | 301.01KB | 0.00KB | ▼ 100.00% |