Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.91MB] [CPU: ▼40.34ms] Passed 4 tests
Analyzing server-side resources used by WP Vagrantize
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 39.09 ▼3.20 |
| Dashboard /wp-admin | 3.04 ▼0.27 | 17.56 ▼32.86 |
| Posts /wp-admin/edit.php | 3.04 ▼0.32 | 19.64 ▼34.86 |
| Add New Post /wp-admin/post-new.php | 3.04 ▼2.85 | 19.50 ▼78.45 |
| Media Library /wp-admin/upload.php | 3.04 ▼0.19 | 17.85 ▼15.18 |
| WP Vagrantize /wp-admin/tools.php?page=wp-vagrantize | 3.04 | 14.78 |
Server storage [IO: ▲1.71MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 432 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for WP Vagrantize
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲47 | 13.16 ▼1.31 | 4.12 ▲1.92 | 39.88 ▼8.43 |
| Dashboard /wp-admin | 2,213 ▲25 | 4.86 ▼1.02 | 107.33 ▼2.88 | 41.16 ▼2.65 |
| Posts /wp-admin/edit.php | 2,096 ▲7 | 1.99 ▼0.03 | 39.72 ▲5.17 | 35.37 ▼1.66 |
| Add New Post /wp-admin/post-new.php | 1,538 ▼4 | 23.23 ▲5.05 | 631.84 ▲31.51 | 52.59 ▲0.77 |
| Media Library /wp-admin/upload.php | 1,395 ▲10 | 4.23 ▲0.02 | 94.24 ▼7.79 | 43.96 ▼0.72 |
| WP Vagrantize /wp-admin/tools.php?page=wp-vagrantize | 1,598 | 1.86 | 41.46 | 39.27 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- Uninstall procedure validation failed for this plugin
- > Warning in wp-content/plugins/wp-vagrantize/lib/composer/interconnectit/search-replace-db/srdb.class.php+854
"continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"?
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Smoke test failed, please fix the following
- 2 occurences, only the last one shown
- > GET request to /wp-admin/tools.php?page=wp-vagrantize
- > POST request to /wp-admin/admin-ajax.php
- > Warning in wp-content/plugins/wp-vagrantize/lib/composer/interconnectit/search-replace-db/srdb.class.php+854
"continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"?
SRP 0% 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
Please take a closer look at the following
- 7× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/wp-vagrantize/lib/composer/interconnectit/search-replace-db/srdb-tests/DataSetGenerator.php
- > /wp-content/plugins/wp-vagrantize/src/view/SettingsTable.php
- > /wp-content/plugins/wp-vagrantize/lib/composer/interconnectit/search-replace-db/srdb.cli.php
- > /wp-content/plugins/wp-vagrantize/lib/composer/mustangostang/spyc/examples/yaml-load.php
- > /wp-content/plugins/wp-vagrantize/lib/composer/mustangostang/spyc/php4/5to4.php
- > /wp-content/plugins/wp-vagrantize/lib/composer/interconnectit/search-replace-db/index.php
- > /wp-content/plugins/wp-vagrantize/lib/composer/codeless/logmore/buildsrc/logmore.php
- 34× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Warning
Use of undefined constant STDERR - assumed 'STDERR' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-vagrantize/lib/composer/interconnectit/search-replace-db/srdb.cli.php on line 136
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_url() in wp-content/plugins/wp-vagrantize/wp-vagrantize.php:12
- > PHP Notice
Undefined variable: data in wp-content/plugins/wp-vagrantize/src/view/SettingsTable.php on line 3
- > PHP Warning
fwrite() expects parameter 1 to be resource, string given in wp-content/plugins/wp-vagrantize/lib/composer/interconnectit/search-replace-db/srdb.cli.php on line 143
- > PHP Warning
Use of undefined constant STDERR - assumed 'STDERR' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-vagrantize/lib/composer/interconnectit/search-replace-db/srdb.cli.php on line 136
- > PHP Warning
Invalid argument supplied for foreach() in wp-content/plugins/wp-vagrantize/src/view/SettingsTable.php on line 3
- > PHP Warning
Use of undefined constant STDERR - assumed 'STDERR' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-vagrantize/lib/composer/interconnectit/search-replace-db/srdb.cli.php on line 136
- > PHP Warning
Use of undefined constant STDERR - assumed 'STDERR' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-vagrantize/lib/composer/interconnectit/search-replace-db/srdb.cli.php on line 143
- > PHP Warning
Use of undefined constant STDERR - assumed 'STDERR' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-vagrantize/lib/composer/interconnectit/search-replace-db/srdb.cli.php on line 136
- > PHP Fatal error
Uncaught PDOException: SQLSTATE[HY000] [1698] Access denied for user 'root'@'localhost' in wp-content/plugins/wp-vagrantize/lib/composer/interconnectit/search-replace-db/srdb-tests/charset-test.php:20
- > 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 97% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that need to be fixed:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Customizing settings of a virtual machine), #2 (Downloading a provisioning file as a ZIP)
wp-vagrantize/wp-vagrantize.php Passed 13 tests
This is the main PHP file of "WP Vagrantize" version 1.2.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
57 characters long description:
A smart way to reproduce your blog into the local machine
Code Analysis 5% from 3 tests
File types 0% from 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Please make sure to remedy the following
- Even if your plugin relies on executable files (for example a companion app), never distribute executable files with your plugin
- .awk - AWK Script in AWK
- ☣ wp-content/plugins/wp-vagrantize/lib/composer/codeless/logmore/buildsrc/extract.awk
- .awk - AWK Script in AWK
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 42 | 1,948 | 2,225 | 7,083 |
| ERB | 60 | 1,129 | 0 | 5,917 |
| Ruby | 205 | 1,155 | 2,837 | 5,355 |
| Markdown | 29 | 1,158 | 0 | 3,555 |
| XML | 3 | 50 | 0 | 1,535 |
| JSON | 17 | 1 | 0 | 818 |
| YAML | 14 | 108 | 100 | 350 |
| JavaScript | 1 | 31 | 0 | 228 |
| SQL | 3 | 26 | 10 | 151 |
| CSS | 1 | 6 | 3 | 81 |
| make | 2 | 16 | 5 | 73 |
| Bourne Shell | 1 | 19 | 0 | 68 |
| Perl | 1 | 11 | 0 | 30 |
| Bourne Again Shell | 1 | 5 | 0 | 28 |
| awk | 1 | 7 | 17 | 18 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.36 |
| Average class complexity | 21.32 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 227.00 |
| Average method complexity | 2.71 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 37.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 4 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 34 | |
| ▷ Abstract classes | 6 | 17.65% |
| ▷ Concrete classes | 28 | 82.35% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 401 | |
| ▷ Static methods | 36 | 8.98% |
| ▷ Public methods | 339 | 84.54% |
| ▷ Protected methods | 4 | 1.00% |
| ▷ Private methods | 58 | 14.46% |
| Functions | 15 | |
| ▷ Named functions | 7 | 46.67% |
| ▷ Anonymous functions | 8 | 53.33% |
| Constants | 34 | |
| ▷ Global constants | 19 | 55.88% |
| ▷ Class constants | 15 | 44.12% |
| ▷ Public constants | 15 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.23MB with 0.15MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 63.47KB | 27.70KB | ▼ 56.36% |
| screenshot-2.png | 174.14KB | 51.71KB | ▼ 70.31% |