Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼5.03ms] Passed 4 tests
A check of server-side resources used by Store Locator Widget
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.05 | 41.12 ▼3.68 |
Dashboard /wp-admin | 3.35 ▲0.04 | 56.40 ▼8.66 |
Posts /wp-admin/edit.php | 3.40 ▲0.04 | 55.06 ▲1.67 |
Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 87.76 ▼9.45 |
Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 39.19 ▲2.19 |
Server storage [IO: ▲0.38MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 10 new files
Database: 1 new table, 7 new options
New tables |
---|
wp_storelocatorwidget |
New WordPress options |
---|
widget_theysaidso_widget |
storelocatorwidget_db_version |
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Store Locator Widget
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲43 | 14.72 ▲0.44 | 2.20 ▲0.14 | 41.30 ▼4.26 |
Dashboard /wp-admin | 2,213 ▲33 | 5.67 ▲0.14 | 83.92 ▼8.58 | 72.20 ▲26.00 |
Posts /wp-admin/edit.php | 2,121 ▲18 | 1.99 ▲0.02 | 36.72 ▲1.11 | 35.45 ▼1.75 |
Add New Post /wp-admin/post-new.php | 1,568 ▲33 | 23.02 ▲4.81 | 719.48 ▲80.97 | 58.65 ▼13.56 |
Media Library /wp-admin/upload.php | 1,415 ▲15 | 4.25 ▲0.11 | 111.45 ▲5.11 | 70.98 ▲25.72 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- This plugin did not uninstall successfully, leaving 7 options in the database
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- storelocatorwidget_db_version
- theysaidso_admin_options
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP Passed 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
Everything seems fine, however this is by no means an exhaustive test
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 90% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need to be fixed:
- Tags: Too many tags (14 tag instead of maximum 10); only the first 5 tags are used in your directory listing
store-locator-widget/store-locator-widget.php 85% from 13 tests
"Store Locator Widget" version 20200131...'s primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please make the necessary changes and fix the following:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Version: The version number should only use digits and periods (ex. "1.0.3" instead of "20200131...")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected12,950 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 2 | 42 | 2,364 | 12,759 |
PHP | 3 | 62 | 37 | 170 |
Markdown | 1 | 12 | 0 | 21 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.21 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 14 | |
▷ Named functions | 14 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
2 PNG files occupy 0.03MB with 0.02MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/icon.png | 4.31KB | 1.28KB | ▼ 70.20% |
images/logo.png | 25.59KB | 7.72KB | ▼ 69.85% |