Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼6.59ms] Passed 4 tests
This is a short check of server-side resources used by WP Safe Updates
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.03 | 45.64 ▼0.64 |
Dashboard /wp-admin | 3.33 ▼0.01 | 52.63 ▼13.00 |
Posts /wp-admin/edit.php | 3.38 ▲0.02 | 51.11 ▲0.21 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 88.37 ▼12.93 |
Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 39.37 ▲4.76 |
Server storage [IO: ▲0.69MB] [DB: ▲0.00MB] 67% from 3 tests
How much does this plugin use your filesystem and database?
It is recommended to fix the following issues
- Illegal file modification found: 1 file (1.94KB) outside of "wp-content/plugins/wp-safe-updates/" and "wp-content/uploads/"
- (new file) wp-content/db.php
Filesystem: 30 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
theysaidso_admin_options |
widget_recent-comments |
widget_theysaidso_widget |
db_upgraded |
widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for WP Safe Updates
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲3 | 14.14 ▼0.12 | 1.72 ▼0.36 | 43.23 ▼4.30 |
Dashboard /wp-admin | 2,192 ▲15 | 5.61 ▼0.01 | 96.63 ▲2.49 | 44.53 ▼0.33 |
Posts /wp-admin/edit.php | 2,097 ▼3 | 2.01 ▼0.01 | 33.68 ▼1.27 | 34.81 ▼6.45 |
Add New Post /wp-admin/post-new.php | 1,528 ▲2 | 23.24 ▲0.05 | 647.00 ▼22.54 | 49.00 ▼18.16 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.23 ▲0.07 | 100.27 ▼5.33 | 45.72 ▼0.87 |
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
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Warning
Use of undefined constant WP_CONTENT_DIR - assumed 'WP_CONTENT_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-safe-updates/wp-safe-updates.php on line 41
- > PHP Fatal error
Uncaught Error: Class 'wpdb' not found in wp-content/plugins/wp-safe-updates/db.php:18
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-safe-updates/wp-safe-updates.php:51
- > PHP Warning
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 Passed 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
3 plugin tags: updates, tested, safe
wp-safe-updates/wp-safe-updates.php Passed 13 tests
The principal PHP file in "WP Safe Updates" v. 1.2.2 is loaded by WordPress automatically on each request
75 characters long description:
Test WordPress plugin updates safely before applying them on the live site.
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
Good job! No executable or dangerous file extensions detected774 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 11 | 178 | 323 | 698 |
JSON | 4 | 0 | 0 | 44 |
Markdown | 1 | 20 | 0 | 32 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.43 |
Average class complexity | 17.71 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 44.00 |
Average method complexity | 3.29 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 52 | |
▷ Static methods | 15 | 28.85% |
▷ Public methods | 49 | 94.23% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 3 | 5.77% |
Functions | 3 | |
▷ Named functions | 2 | 66.67% |
▷ Anonymous functions | 1 | 33.33% |
Constants | 5 | |
▷ Global constants | 5 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
7 PNG files occupy 0.61MB with 0.37MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-1.png | 82.03KB | 23.83KB | ▼ 70.95% |
assets/icon-128x128.png | 7.41KB | 4.78KB | ▼ 35.46% |
assets/banner-1544x500.png | 112.47KB | 48.93KB | ▼ 56.50% |
assets/screenshot-3.png | 213.93KB | 59.40KB | ▼ 72.23% |
assets/screenshot-2.png | 146.09KB | 43.97KB | ▼ 69.90% |