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.00MB] [CPU: ▼6.54ms] Passed 4 tests
Analyzing server-side resources used by EveryPay Payment Gateway for WooCommerce
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 39.44 ▼4.77 |
| Dashboard /wp-admin | 3.32 ▼0.02 | 49.39 ▼16.48 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 53.36 ▼3.75 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 111.83 ▲2.93 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 35.89 ▼1.16 |
Server storage [IO: ▲2.43MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 29 new files
Database: 2 new tables, 6 new options
| New tables |
|---|
| wp_everypay_tokenization |
| wp_everypay_logging |
| New WordPress options |
|---|
| db_upgraded |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
| widget_theysaidso_widget |
| widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for EveryPay Payment Gateway for WooCommerce
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,797 ▲51 | 14.38 ▲0.23 | 1.63 ▼0.10 | 42.92 ▼2.00 |
| Dashboard /wp-admin | 2,203 ▲26 | 5.57 ▲0.03 | 91.55 ▼7.03 | 45.57 ▲1.20 |
| Posts /wp-admin/edit.php | 2,108 ▲5 | 1.99 ▼0.04 | 39.24 ▼1.58 | 40.91 ▲4.14 |
| Add New Post /wp-admin/post-new.php | 1,544 ▲18 | 18.06 ▼4.94 | 595.33 ▼23.76 | 68.11 ▲13.63 |
| Media Library /wp-admin/upload.php | 1,405 ▲5 | 4.15 ▼0.02 | 99.23 ▼11.60 | 48.71 ▲1.50 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
These items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
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 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 81% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
These attributes need to be fixed:
- Contributors: The plugin contributors field is not present
- Screenshots: These screenshots have no corresponding images in /assets: #1 (EveryPay Payment Gateway plugin activation.), #2 (EveryPay Payment Gateway in WooCommerce payment methods), #3 (EveryPay Payment Gateway settings in WooCommerce), #4 (Everypay Payment Gateway 3ds2 iframe)
- Tags: There are too many tags (18 tag instead of maximum 10)
everypay-payment-gateway/everypay-payment-gateway.php Passed 13 tests
The entry point to "EveryPay Payment Gateway for WooCommerce" version 3.5 is a PHP file that has certain tags in its header comment area
107 characters long description:
This plugin adds a payment option in WooCommerce for customers to pay with their Credit Cards Via Everypay.
Code Analysis Passed 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
Success! There were no dangerous files found in this plugin1,534 lines of code in 19 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 10 | 193 | 154 | 795 |
| JavaScript | 6 | 88 | 7 | 424 |
| CSS | 2 | 12 | 10 | 275 |
| Markdown | 1 | 17 | 0 | 40 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| Average class complexity | 9.22 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 29.00 |
| Average method complexity | 2.35 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 12.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 9 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 9 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 55 | |
| ▷ Static methods | 8 | 14.55% |
| ▷ Public methods | 46 | 83.64% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 9 | 16.36% |
| Functions | 4 | |
| ▷ Named functions | 4 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 5 | |
| ▷ Global constants | 5 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
6 PNG files occupy 1.03MB with 0.73MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| wp_org_assets/Screenshot-1.png | 128.23KB | 36.42KB | ▼ 71.60% |
| wp_org_assets/Screenshot-3.png | 146.54KB | 46.41KB | ▼ 68.33% |
| images/everypay.png | 580.37KB | 67.04KB | ▼ 88.45% |
| wp_org_assets/Screenshot-2.png | 124.17KB | 37.48KB | ▼ 69.81% |
| wp_org_assets/Screenshot-4.png | 71.50KB | 30.28KB | ▼ 57.65% |