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.01MB] [CPU: ▼7.96ms] Passed 4 tests
Server-side resources used by **RapidDive** BARCLAY ePDQ Payment Gateway
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 36.81 ▼0.39 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 45.25 ▼14.60 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 45.55 ▼1.68 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 80.65 ▼15.16 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.43 ▲2.68 |
Server storage [IO: ▲0.15MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 15 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| can_compress_scripts |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
**RapidDive** BARCLAY ePDQ 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,789 ▲28 | 14.28 ▼0.28 | 1.85 ▲0.16 | 43.69 ▲3.88 |
| Dashboard /wp-admin | 2,198 ▲27 | 5.61 ▲0.09 | 96.04 ▲7.27 | 40.91 ▼0.97 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.01 ▲0.05 | 34.97 ▲0.40 | 33.62 ▼6.69 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼2 | 23.61 ▲0.55 | 642.11 ▼31.25 | 51.55 ▼0.24 |
| Media Library /wp-admin/upload.php | 1,400 ▼3 | 4.18 ▼0.02 | 94.68 ▼8.21 | 41.81 ▼1.11 |
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
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
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
Looking good! No server-side errors or output on direct access of PHP files
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 93% from 29 tests
readme.txt Passed 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
5 plugin tags: woocommerce, ecommerce, payment gateway, barclay, epdq
catchtheweb-barclay-epdq-payment-gateway/index.php 85% from 13 tests
The entry point to "**RapidDive** BARCLAY ePDQ Payment Gateway" version 2.3.8 is a PHP file that has certain tags in its header comment area
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("catchtheweb-barclay-epdq-payment-gateway.php" instead of "index.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Everything looks great! No dangerous files found in this plugin1,444 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 136 | 278 | 1,369 |
| Markdown | 1 | 26 | 0 | 62 |
| JavaScript | 1 | 3 | 0 | 12 |
| YAML | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| Average class complexity | 14.50 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 48.00 |
| Average method complexity | 3.16 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 16.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 25 | |
| ▷ Static methods | 3 | 12.00% |
| ▷ Public methods | 20 | 80.00% |
| ▷ Protected methods | 1 | 4.00% |
| ▷ Private methods | 4 | 16.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 17 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 17 | 100.00% |
| ▷ Public constants | 17 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.03MB with 0.02MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/barclaycard_logo.png | 34.52KB | 16.74KB | ▼ 51.49% |