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 successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.17MB] [CPU: ▼9.67ms] Passed 4 tests
Server-side resources used by iNext Woo Pincode Checker
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.59 ▲0.13 | 39.43 ▼1.66 |
Dashboard /wp-admin | 3.53 ▲0.22 | 50.15 ▼4.86 |
Posts /wp-admin/edit.php | 3.58 ▲0.22 | 50.43 ▼12.43 |
Add New Post /wp-admin/post-new.php | 6.06 ▲0.18 | 86.11 ▼19.73 |
Media Library /wp-admin/upload.php | 3.38 ▲0.16 | 41.50 ▲6.20 |
Welcome /wp-admin/admin.php?page=inext-wpc-welcome | 3.40 | 34.90 |
Settings /wp-admin/admin.php?page=inext-wpc-settings | 3.49 | 40.75 |
Server storage [IO: ▲5.26MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 45 new files
Database: no new tables, 24 new options
New WordPress options |
---|
_inext_wpc_pincode_field_length |
_inext_wpc_pincode_field_error |
_inext_wpc_is_product_enabled |
theysaidso_admin_options |
_inext_wpc_pincode_field_label |
db_upgraded |
_inext_wpc_is_single_product_atc_btn_disabled |
_inext_wpc_pincode_field_placeholder_is_enabled |
_inext_wpc_pincode_field_success |
_inext_wpc_is_pincode_alphanumeric_enabled |
... |
Browser metrics Passed 4 tests
This is an overview of browser requirements for iNext Woo Pincode Checker
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,039 ▲304 | 19.99 ▲5.59 | 7.21 ▲4.85 | 42.01 ▼4.81 |
Dashboard /wp-admin | 2,326 ▲138 | 8.96 ▲4.05 | 139.66 ▲23.88 | 43.19 ▲3.13 |
Posts /wp-admin/edit.php | 2,206 ▲117 | 6.03 ▲4.03 | 62.44 ▲20.82 | 36.81 ▲4.66 |
Add New Post /wp-admin/post-new.php | 6,396 ▲4,852 | 26.97 ▲8.60 | 1,015.32 ▲395.84 | 38.10 ▼13.23 |
Media Library /wp-admin/upload.php | 1,500 ▲121 | 6.89 ▲2.70 | 138.40 ▲40.70 | 48.72 ▲3.26 |
Welcome /wp-admin/admin.php?page=inext-wpc-welcome | 1,009 | 5.78 | 42.56 | 61.50 |
Settings /wp-admin/admin.php?page=inext-wpc-settings | 1,435 | 5.59 | 65.57 | 55.19 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
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: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Everything seems fine, however this is by no means an exhaustive test
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 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need your attention:
- Tags: Too many tags (15 tag instead of maximum 10); only the first 5 tags are used in your directory listing
inext-woo-pincode-checker/inext-woo-pincode-checker.php 85% from 13 tests
"iNext Woo Pincode Checker" version 1.0.5's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
The following require your attention:
- Domain Path: The domain path folder was not found ("/languages")
- Description: Keep the plugin description shorter than 140 characters (currently 183 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected42,079 lines of code in 32 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 3 | 7,619 | 262 | 40,525 |
PHP | 23 | 247 | 153 | 1,335 |
JavaScript | 6 | 23 | 42 | 219 |
PHP code Passed 2 tests
This is a very shot 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.30 |
Average class complexity | 6.26 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 36.00 |
Average method complexity | 2.19 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 35.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 19 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 19 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 84 | |
▷ Static methods | 84 | 100.00% |
▷ Public methods | 67 | 79.76% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 17 | 20.24% |
Functions | 0 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 42 | |
▷ Global constants | 42 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
1 compressed PNG file occupies 0.00MB
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/frontend/img/location-marker.png | 1.99KB | 2.18KB | 0.00% |