Benchmarks
Plugin footprint Passed 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 gracefully, with no errors
Server metrics [RAM: ▼0.02MB] [CPU: ▼301.67ms] Passed 4 tests
Analyzing server-side resources used by Accept Qpay payments Using Contact form 7
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.52 ▲0.01 | 55.50 ▲4.91 |
Dashboard /wp-admin | 3.41 ▲0.00 | 33.74 ▲0.29 |
Posts /wp-admin/edit.php | 3.64 ▲0.01 | 38.17 ▲2.49 |
Add New Post /wp-admin/post-new.php | 6.88 ▼0.09 | 92.58 ▼1,208.09 |
Media Library /wp-admin/upload.php | 3.29 ▲0.00 | 24.73 ▼1.36 |
All QPay Payment Details /wp-admin/edit.php?post_type=cfqpzw_data | 3.18 | 19.24 |
Server storage [IO: ▲0.89MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 28 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
An overview of browser requirements for Accept Qpay payments Using Contact form 7
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,795 ▲73 | 15.90 ▼0.11 | 6.41 ▲0.46 | 2.46 ▼0.16 |
Dashboard /wp-admin | 2,895 ▲37 | 6.11 ▼0.05 | 115.29 ▼16.24 | 156.02 ▼4.93 |
Posts /wp-admin/edit.php | 2,688 ▼3 | 3.24 ▲0.01 | 63.72 ▼2.21 | 140.35 ▼7.31 |
Add New Post /wp-admin/post-new.php | 1,710 ▲13 | 21.12 ▲3.82 | 429.58 ▼1.73 | 154.52 ▼5.42 |
Media Library /wp-admin/upload.php | 1,698 ▼0 | 5.48 ▼0.05 | 143.58 ▲4.24 | 188.44 ▼1.56 |
All QPay Payment Details /wp-admin/edit.php?post_type=cfqpzw_data | 28 | 0.94 | 0.04 | 16.94 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The plugin uninstalled completely, with no zombie files or tables
Smoke tests 50% from 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)
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'WPCF7_ContactForm' not found in wp-content/plugins/accept-qpay-payments-using-contact-form-7/inc/admin/template/cf7qpay.template.php:14
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
These are user-side errors you should fix
- > GET request to /wp-admin/edit.php?post_type=cfqpzw_data
- > Network (severe)
wp-admin/edit.php?post_type=cfqpzw_data - Failed to load resource: the server responded with a status of 500 (Internal Server Error)
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
4 plugin tags: qpay, payment gateway, wordpress, contact form 7
accept-qpay-payments-using-contact-form-7/accept-qpay-payments-using-contact-form-7.php Passed 13 tests
The primary PHP file in "Accept Qpay payments Using Contact form 7" version 1.1 is used by WordPress to initiate all plugin functionality
96 characters long description:
This plugin will integrate QPay payment gateway for making your payments through Contact Form 7.
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
Good job! No executable or dangerous file extensions detected7,906 lines of code in 22 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 8 | 1,326 | 375 | 5,197 |
PHP | 10 | 447 | 680 | 2,115 |
CSS | 4 | 72 | 3 | 594 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.55 |
Average class complexity | 35.50 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 191.00 |
Average method complexity | 5.76 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 61.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 58 | |
▷ Static methods | 1 | 1.72% |
▷ Public methods | 58 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 8 | |
▷ Named functions | 1 | 12.50% |
▷ Anonymous functions | 7 | 87.50% |
Constants | 11 | |
▷ Global constants | 11 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.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
4 PNG files occupy 0.43MB with 0.25MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/screenshot-4.png | 73.28KB | 32.03KB | ▼ 56.29% |
assets/images/screenshot-2.png | 109.54KB | 49.49KB | ▼ 54.82% |
assets/images/screenshot-3.png | 49.70KB | 24.71KB | ▼ 50.28% |
assets/images/screenshot-1.png | 207.21KB | 59.32KB | ▼ 71.37% |