Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼6.48ms] Passed 4 tests
Analyzing server-side resources used by Takepayments Mercury Payment Gateway
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 34.84 ▼8.02 |
Dashboard /wp-admin | 3.31 ▲0.01 | 47.07 ▼3.78 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.41 ▼6.13 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 95.26 ▼8.00 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 38.52 ▲0.96 |
Server storage [IO: ▲0.30MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 29 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
theysaidso_admin_options |
db_upgraded |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Takepayments Mercury Payment Gateway
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,792 ▲31 | 14.38 ▼0.26 | 1.71 ▼0.11 | 46.24 ▲1.94 |
Dashboard /wp-admin | 2,201 ▲21 | 5.62 ▼0.14 | 87.35 ▼1.84 | 43.34 ▼0.95 |
Posts /wp-admin/edit.php | 2,103 ▼0 | 2.06 ▲0.01 | 40.78 ▼2.56 | 38.66 ▲2.66 |
Add New Post /wp-admin/post-new.php | 1,561 ▲35 | 23.15 ▲5.49 | 602.22 ▼108.96 | 50.84 ▼4.04 |
Media Library /wp-admin/upload.php | 1,403 ▲6 | 4.23 ▲0.02 | 101.54 ▼14.09 | 43.29 ▼6.72 |
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
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% 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
The following issues need your attention
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'Automattic\\WooCommerce\\Blocks\\Payments\\Integrations\\AbstractPaymentMethodType' not found in wp-content/plugins/takepayments-ipp-payment-gateway/classes/class-payment-block.php:9
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that need to be fixed:
- Screenshots: Add images for these screenshots: #1 (Appearance of Takepayments Mercury gateway.), #2 (Takepayments Logo)
takepayments-ipp-payment-gateway/takepayments-mercury-init.php 85% from 13 tests
The entry point to "Takepayments Mercury Payment Gateway" version 1.0.1 is a PHP file that has certain tags in its header comment area
Please take the time to 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
- Main file name: Name the main plugin file the same as the plugin slug ("takepayments-ipp-payment-gateway.php" instead of "takepayments-mercury-init.php")
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
Good job! No executable or dangerous file extensions detected2,680 lines of code in 17 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 11 | 105 | 208 | 2,294 |
CSS | 2 | 25 | 25 | 231 |
SVG | 2 | 0 | 0 | 112 |
JavaScript | 2 | 0 | 0 | 43 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.28 |
Average class complexity | 13.67 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 31.00 |
Average method complexity | 2.97 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 13.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 6 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 6 | 100.00% |
▷ Final classes | 1 | 16.67% |
Methods | 37 | |
▷ Static methods | 1 | 2.70% |
▷ Public methods | 30 | 81.08% |
▷ Protected methods | 7 | 18.92% |
▷ Private methods | 0 | 0.00% |
Functions | 13 | |
▷ Named functions | 6 | 46.15% |
▷ Anonymous functions | 7 | 53.85% |
Constants | 4 | |
▷ Global constants | 3 | 75.00% |
▷ Class constants | 1 | 25.00% |
▷ Public constants | 1 | 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
10 PNG files occupy 0.19MB with 0.09MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/tp_logo.png | 3.57KB | 2.23KB | ▼ 37.66% |
public/images/TP_Card_Logos_[Horiz]_AMEX_Full_Colour.png | 29.14KB | 15.45KB | ▼ 46.97% |
assets/Screenshot-2.png | 17.65KB | 7.04KB | ▼ 60.12% |
assets/Screenshot-1.png | 43.08KB | 16.36KB | ▼ 62.02% |
public/images/icon-128x128.png | 3.95KB | 2.32KB | ▼ 41.38% |