Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼7.01ms] Passed 4 tests
Server-side resources used by edxaPay
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 39.35 ▼1.24 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 59.63 ▼5.80 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 48.62 ▼1.77 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 82.27 ▼19.23 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 35.70 ▲0.81 |
Server storage [IO: ▲0.31MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 6 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
edxaPay: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲29 | 13.34 ▼1.06 | 1.77 ▼0.28 | 43.76 ▲0.64 |
| Dashboard /wp-admin | 2,203 ▲15 | 4.86 ▼0.99 | 101.68 ▼16.95 | 39.94 ▼3.46 |
| Posts /wp-admin/edit.php | 2,086 ▼3 | 2.00 ▲0.01 | 32.55 ▼4.30 | 35.95 ▲3.79 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼7 | 17.44 ▼5.82 | 691.44 ▲79.85 | 56.70 ▼4.75 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.19 ▼0.02 | 93.02 ▼7.52 | 41.48 ▼1.13 |
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
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
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
Good news, no errors were detected
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
Please take a closer look at the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/edxapay-for-woocommerce/src/edxapay.php:6
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
5 plugin tags: ewallet, touch n go, malaysia, payment gateway, online banking
edxapay-for-woocommerce/index.php 92% from 13 tests
The primary PHP file in "edxaPay" version 1.0.3 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("edxapay-for-woocommerce.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Success! There were no dangerous files found in this plugin203 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 63 | 29 | 203 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.57 |
| Average class complexity | 36.00 |
| ▷ Minimum class complexity | 36.00 |
| ▷ Maximum class complexity | 36.00 |
| Average method complexity | 6.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 27.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 | 7 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 7 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 4 | |
| ▷ Named functions | 4 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
3 PNG files occupy 0.30MB with 0.21MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| src/assets/mini.png | 57.20KB | 19.88KB | ▼ 65.25% |
| src/assets/wide.png | 120.80KB | 33.41KB | ▼ 72.34% |
| src/assets/tall.png | 129.66KB | 33.13KB | ▼ 74.45% |