Benchmarks
Plugin footprint 82% 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: ▲4.61MB] [CPU: ▲24.46ms] 75% from 4 tests
This is a short check of server-side resources used by WP STAGING WordPress Backup Plugin - Migration Backup Restore
Please take the time to fix the following items
- CPU: Total CPU usage must kept under 500.00ms (currently 534.54ms on /wp-admin/admin.php?page=wpstg-tools)
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 7.37 ▲3.91 | 63.53 ▲25.59 |
| Dashboard /wp-admin | 8.15 ▲4.81 | 81.27 ▲20.95 |
| Posts /wp-admin/edit.php | 8.20 ▲4.85 | 86.71 ▲41.23 |
| Add New Post /wp-admin/post-new.php | 10.76 ▲4.87 | 109.75 ▲15.53 |
| Media Library /wp-admin/upload.php | 8.09 ▲4.86 | 71.12 ▲35.76 |
| Backup & Migration /wp-admin/admin.php?page=wpstg_backup | 8.21 | 71.18 |
| System Info /wp-admin/admin.php?page=wpstg-tools | 8.76 | 534.54 |
| Staging Sites /wp-admin/admin.php?page=wpstg_clone | 8.21 | 64.23 |
| Get WP Staging Pro /wp-admin/admin.php?page=wpstg-welcome | 8.16 | 59.68 |
| Settings /wp-admin/admin.php?page=wpstg-settings | 8.36 | 66.03 |
Server storage [IO: ▲7.08MB] [DB: ▲0.00MB] 67% from 3 tests
Analyzing filesystem and database footprints of this plugin
It is recommended to fix the following issues
- Illegal file modification detected: 1 file (10.82KB) outside of "wp-content/plugins/wp-staging/" and "wp-content/uploads/"
- (new file) wp-content/mu-plugins/wp-staging-optimizer.php
Filesystem: 901 new files
Database: no new tables, 14 new options
| New WordPress options |
|---|
| wpstg_installDate |
| can_compress_scripts |
| wpstg_free_upgrade_date |
| db_upgraded |
| widget_recent-posts |
| wpstg_settings |
| theysaidso_admin_options |
| wpstg_free_install_date |
| wpstg_missing_cloneName_routine_executed |
| wpstg_access_token |
| ... |
Browser metrics Passed 4 tests
WP STAGING WordPress Backup Plugin - Migration Backup Restore: 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,915 ▲153 | 14.33 ▲0.08 | 1.91 ▲0.16 | 38.41 ▼6.12 |
| Dashboard /wp-admin | 2,287 ▲109 | 5.51 ▼0.21 | 94.40 ▼15.04 | 39.40 ▼0.15 |
| Posts /wp-admin/edit.php | 2,199 ▲99 | 2.03 ▲0.01 | 41.97 ▲3.09 | 36.01 ▼0.11 |
| Add New Post /wp-admin/post-new.php | 1,558 ▲32 | 23.24 ▼0.28 | 671.55 ▲71.59 | 56.84 ▲9.25 |
| Media Library /wp-admin/upload.php | 1,496 ▲99 | 4.16 ▼0.01 | 99.58 ▲6.02 | 40.58 ▼1.01 |
| Backup & Migration /wp-admin/admin.php?page=wpstg_backup | 2,878 | 2.17 | 46.44 | 101.38 |
| System Info /wp-admin/admin.php?page=wpstg-tools | 1,331 | 2.09 | 36.94 | 60.46 |
| Staging Sites /wp-admin/admin.php?page=wpstg_clone | 1,581 | 2.08 | 32.06 | 46.57 |
| Get WP Staging Pro /wp-admin/admin.php?page=wpstg-welcome | 969 | 2.07 | 33.11 | 41.22 |
| Settings /wp-admin/admin.php?page=wpstg-settings | 1,675 | 2.07 | 30.11 | 40.09 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- This plugin did not uninstall successfully, leaving 14 options in the database
- db_upgraded
- wpstg_version
- wpstg_access_token
- wpstg_free_install_date
- wpstg_version_upgraded_from
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- wpstg_free_upgrade_date
- widget_recent-comments
- ...
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following items
- 5× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/wp-staging/vendor_wpstg/lucatume/di52/test-constructor.php
- > /wp-content/plugins/wp-staging/Backend/views/backup/modal/download.php
- > /wp-content/plugins/wp-staging/Frontend/views/header.php
- > /wp-content/plugins/wp-staging/Frontend/views/footer.php
- > /wp-content/plugins/wp-staging/Backend/views/clone/single-site/index.php
- 499× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'WPStaging\\Vendor\\Monolog\\Handler\\AbstractHandler' not found in wp-content/plugins/wp-staging/vendor_wpstg/monolog/monolog/src/Monolog/Handler/BufferHandler.php:24
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_kses_post() in wp-content/plugins/wp-staging/Backend/views/_main/contact-us-pro.php:15
- > PHP Fatal error
Uncaught Error: Class 'WPStaging\\Backup\\Task\\RestoreFileHandlers\\RestoreFileHandler' not found in wp-content/plugins/wp-staging/Backup/Task/RestoreFileHandlers/MoveHandler.php:5
- > PHP Fatal error
Trait 'WPStaging\\Framework\\Traits\\ResourceTrait' not found in wp-content/plugins/wp-staging/Framework/Assets/Assets.php on line 15
- > PHP Warning
require_once(WPSTG_PLUGIN_DIRBackend/views/backup/modal/progress.php): failed to open stream: No such file or directory in wp-content/plugins/wp-staging/Backend/views/clone/ajax/delete-confirmation.php on line 11
- > PHP Fatal error
Uncaught Error: Class 'WPStaging\\Framework\\Component\\AbstractTemplateComponent' not found in wp-content/plugins/wp-staging/Backup/Ajax/Parts.php:15
- > PHP Warning
Use of undefined constant WPSTG_PLUGIN_DIR - assumed 'WPSTG_PLUGIN_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-staging/Backend/views/clone/ajax/update.php on line 8
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/wp-staging/Backend/views/notices/table-tmp-prefix-conflict-notice.php:10
- > PHP Fatal error
Uncaught Error: Interface 'WPStaging\\Vendor\\lucatume\\DI52\\Builders\\BuilderInterface' not found in wp-content/plugins/wp-staging/vendor_wpstg/lucatume/di52/src/Builders/ClosureBuilder.php:17
- > PHP Fatal error
Uncaught Error: Class 'WPStaging\\Framework\\DependencyResolver\\Exceptions\\ResolveException' not found in wp-content/plugins/wp-staging/Framework/DependencyResolver/Exceptions/CircularReferenceException.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that require attention:
- Requires at least: Version format is invalid
- Screenshots: Please a description for screenshot #8 in wp-staging/assets to your readme.txt
wp-staging/wp-staging.php 92% from 13 tests
"WP STAGING WordPress Backup Plugin - Migration Backup Restore" version 3.1.3's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please take the time to fix the following:
- Requires at least: Please use periods and digits for the required version (ex. "7.0" instead of "3.6+")
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Everything looks great! No dangerous files found in this plugin76,985 lines of code in 849 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 781 | 11,210 | 29,152 | 59,619 |
| JavaScript | 24 | 546 | 1,427 | 10,771 |
| CSS | 11 | 831 | 68 | 4,727 |
| PO File | 4 | 441 | 472 | 1,137 |
| SVG | 23 | 0 | 1 | 426 |
| make | 1 | 24 | 10 | 232 |
| XML | 2 | 2 | 1 | 36 |
| Markdown | 1 | 11 | 0 | 18 |
| Dockerfile | 1 | 8 | 0 | 10 |
| HTML | 1 | 1 | 0 | 9 |
PHP code 50% from 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Please tend to the following items
- Cyclomatic complexity of methods has to be reduced to less than 100 (currently 179)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.39 |
| Average class complexity | 12.45 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 179.00 |
| Average method complexity | 2.69 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 179.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 127 | |
| Interfaces | 53 | |
| Traits | 28 | |
| Classes | 555 | |
| ▷ Abstract classes | 40 | 7.21% |
| ▷ Concrete classes | 515 | 92.79% |
| ▷ Final classes | 26 | 5.05% |
| Methods | 4,411 | |
| ▷ Static methods | 366 | 8.30% |
| ▷ Public methods | 3,264 | 74.00% |
| ▷ Protected methods | 614 | 13.92% |
| ▷ Private methods | 533 | 12.08% |
| Functions | 332 | |
| ▷ Named functions | 153 | 46.08% |
| ▷ Anonymous functions | 179 | 53.92% |
| Constants | 439 | |
| ▷ Global constants | 85 | 19.36% |
| ▷ Class constants | 354 | 80.64% |
| ▷ Public constants | 354 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
6 PNG files occupy 0.10MB with 0.05MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/img/admin_dashboard.png | 6.43KB | 4.11KB | ▼ 36.10% |
| assets/img/wp-staging-logo-256x256.png | 11.12KB | 5.79KB | ▼ 47.91% |
| assets/img/logo-white-transparent.png | 8.27KB | 5.88KB | ▼ 28.87% |
| assets/img/wp-staging274x463-1.png | 68.68KB | 29.92KB | ▼ 56.44% |
| assets/img/wpstaging-icon.png | 2.41KB | 1.13KB | ▼ 53.04% |