Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.47ms] Passed 4 tests
Server-side resources used by ExpressPay Woocommerce Payment Gateway
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 35.48 ▼4.59 |
Dashboard /wp-admin | 3.31 ▲0.00 | 45.18 ▼6.34 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 45.61 ▼2.69 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 83.31 ▼8.25 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.30 ▲2.01 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
ExpressPay Woocommerce Payment Gateway: an overview of browser usage
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲90 | 13.23 ▼1.17 | 1.83 ▲0.26 | 40.80 ▼4.33 |
Dashboard /wp-admin | 2,206 ▲15 | 5.76 ▲0.70 | 97.38 ▼4.90 | 38.70 ▼2.71 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.04 ▼0.01 | 38.65 ▼1.58 | 34.36 ▼1.80 |
Add New Post /wp-admin/post-new.php | 1,514 ▼0 | 17.49 ▲0.02 | 634.41 ▼34.24 | 49.64 ▲0.45 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.18 ▲0.03 | 96.64 ▼3.85 | 41.74 ▼2.49 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
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
The SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Attributes that need to be fixed:
- Tags: Too many tags (13 tag instead of maximum 10); only the first 5 tags are used in your directory listing
woocommerce-expresspay-payment-gateway/expresspay-woocommere-gateway.php 92% from 13 tests
The entry point to "ExpressPay Woocommerce Payment Gateway" version 2.0.0 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("woocommerce-expresspay-payment-gateway.php" instead of "expresspay-woocommere-gateway.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Everything looks great! No dangerous files found in this plugin366 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 47 | 17 | 348 |
JavaScript | 1 | 0 | 0 | 18 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.19 |
Average class complexity | 31.00 |
▷ Minimum class complexity | 31.00 |
▷ Maximum class complexity | 31.00 |
Average method complexity | 3.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 14.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 15 | |
▷ Static methods | 4 | 26.67% |
▷ Public methods | 14 | 93.33% |
▷ Protected methods | 1 | 6.67% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 1 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 0 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 compressed PNG file occupies 0.01MB
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/logo.png | 6.67KB | 6.83KB | 0.00% |