Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.02MB] [CPU: ▼10.01ms] Passed 4 tests
Analyzing server-side resources used by WooCommerce AzamPay
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 41.12 ▲2.11 |
Dashboard /wp-admin | 3.32 ▲0.02 | 44.82 ▼4.78 |
Posts /wp-admin/edit.php | 3.38 ▲0.02 | 46.19 ▼1.49 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 80.94 ▼32.98 |
Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 33.88 ▼0.78 |
Server storage [IO: ▲0.66MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 14 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
theysaidso_admin_options |
db_upgraded |
widget_recent-comments |
widget_theysaidso_widget |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for WooCommerce AzamPay
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,821 ▲60 | 14.14 ▼0.21 | 2.04 ▲0.47 | 46.20 ▲3.85 |
Dashboard /wp-admin | 2,199 ▲22 | 5.49 ▼0.09 | 82.94 ▼9.36 | 40.23 ▲4.83 |
Posts /wp-admin/edit.php | 2,110 ▲13 | 1.97 ▼0.03 | 35.91 ▲0.04 | 33.20 ▼5.36 |
Add New Post /wp-admin/post-new.php | 1,533 ▲4 | 23.70 ▲0.38 | 641.54 ▼17.59 | 63.22 ▼2.71 |
Media Library /wp-admin/upload.php | 1,404 ▲1 | 4.16 ▼0.03 | 96.02 ▼2.90 | 41.21 ▼3.14 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/azampay/includes/class-woo-azampay-gateway.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% 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 require attention:
- Tags: Too many tags (12 tag instead of maximum 10); only the first 5 tags are used in your directory listing
- Screenshots: Please add images for these screenshots: #1 (The AzamPay Gateway settings screen is used to configure the main Azampay gateway.), #2 (Checkout page that offers a range of payment methods such as local and alternative payment methods.)
azampay/woocommerce-azampay.php 77% from 13 tests
The main PHP script in "WooCommerce AzamPay" version 1.0.5 is automatically included on every request by WordPress
The following require your attention:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Requires at least: The required version number must match the one declared in readme.txt ("6.0" instead of "6.0.0")
- Main file name: It is recommended to name the main PHP file as the plugin slug ("azampay.php" instead of "woocommerce-azampay.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Success! There were no dangerous files found in this plugin906 lines of code in 8 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 200 | 210 | 743 |
CSS | 1 | 16 | 0 | 78 |
JavaScript | 1 | 10 | 0 | 73 |
SVG | 4 | 0 | 0 | 12 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.43 |
Average class complexity | 107.00 |
▷ Minimum class complexity | 107.00 |
▷ Maximum class complexity | 107.00 |
Average method complexity | 6.30 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 21.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 | 20 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 16 | 80.00% |
▷ Protected methods | 1 | 5.00% |
▷ Private methods | 3 | 15.00% |
Functions | 8 | |
▷ Named functions | 8 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/public/images/logo.png | 5.56KB | 2.95KB | ▼ 46.97% |