Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.11MB] [CPU: ▲0.66ms] Passed 4 tests
Server-side resources used by Flutterwave Payments
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.60 ▲0.14 | 38.65 ▼1.38 |
| Dashboard /wp-admin | 3.44 ▲0.14 | 44.91 ▼4.83 |
| Posts /wp-admin/edit.php | 3.49 ▲0.13 | 49.42 ▲7.42 |
| Add New Post /wp-admin/post-new.php | 5.97 ▲0.08 | 97.64 ▲1.43 |
| Media Library /wp-admin/upload.php | 3.30 ▲0.07 | 40.23 ▲10.51 |
| Settings /wp-admin/admin.php?page=flutterwave-payments | 3.36 | 29.70 |
| Transactions /wp-admin/admin.php?page=flutterwave-payments-transactions | 3.29 | 30.16 |
Server storage [IO: ▲4.74MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 58 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_recent-comments |
| flw_rave_options |
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Flutterwave Payments
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,850 ▲93 | 13.20 ▼1.22 | 1.68 ▼0.19 | 39.69 ▼4.57 |
| Dashboard /wp-admin | 2,251 ▲66 | 5.84 ▲0.98 | 97.41 ▼15.18 | 69.35 ▲25.86 |
| Posts /wp-admin/edit.php | 2,136 ▲47 | 2.02 ▲0.01 | 40.22 ▲3.73 | 37.26 ▼1.45 |
| Add New Post /wp-admin/post-new.php | 1,712 ▲198 | 22.36 ▲4.79 | 726.12 ▲113.46 | 49.54 ▼2.75 |
| Media Library /wp-admin/upload.php | 1,430 ▲42 | 4.25 ▲0.14 | 97.07 ▲0.51 | 73.02 ▲30.87 |
| Settings /wp-admin/admin.php?page=flutterwave-payments | 1,361 | 2.16 | 23.08 | 43.41 |
| Transactions /wp-admin/admin.php?page=flutterwave-payments-transactions | 975 | 2.05 | 24.71 | 26.96 |
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
These items require your attention
- This plugin does not fully uninstall, leaving 7 options in the database
- flw_rave_options
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
- 5× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WP_REST_Controller' not found in wp-content/plugins/rave-payment-forms/includes/api/class-flw-webhook-rest-route.php:11
- > PHP Fatal error
Uncaught Error: Class 'Flutterwave\\WordPress\\Integrations\\AbstractService' not found in wp-content/plugins/rave-payment-forms/src/Integrations/ApiLayer/class-exchangerateservice.php:16
- > PHP Fatal error
Uncaught Error: Class 'Abstract_FLW_Shortcode' not found in wp-content/plugins/rave-payment-forms/includes/shortcodes/class-flw-shortcode-donation-form.php:12
- > PHP Fatal error
Uncaught Error: Class 'FLW_Payment_List' not found in wp-content/plugins/rave-payment-forms/views/payment-list-table.php:9
- > PHP Fatal error
Uncaught Error: Class 'WP_REST_Controller' not found in wp-content/plugins/rave-payment-forms/includes/api/class-flw-transaction-rest-route.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 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
Attributes that need to be fixed:
- Screenshots: No descriptions were found for these screenshots #6, #7 in rave-payment-forms/assets to your readme.txt
- Tags: Please delete some tags, you are using 12 tag instead of maximum 10
rave-payment-forms/rave-payment-forms.php 85% from 13 tests
This is the main PHP file of "Flutterwave Payments" version 1.0.7, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
It is important to fix the following:
- Requires at least: The required version number did not match the one declared in readme.txt ("4.4" instead of "5.2")
- Domain Path: You should use only dashes and lowercase characters for the domain path ("i18n/languages")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Success! There were no dangerous files found in this plugin3,329 lines of code in 44 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 26 | 561 | 1,324 | 2,350 |
| CSS | 3 | 140 | 9 | 535 |
| JavaScript | 9 | 45 | 40 | 300 |
| Markdown | 1 | 62 | 0 | 126 |
| SVG | 4 | 0 | 0 | 13 |
| Sass | 1 | 1 | 0 | 5 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| Average class complexity | 11.65 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 64.00 |
| Average method complexity | 2.38 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 19.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 5 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 20 | |
| ▷ Abstract classes | 2 | 10.00% |
| ▷ Concrete classes | 18 | 90.00% |
| ▷ Final classes | 9 | 50.00% |
| Methods | 150 | |
| ▷ Static methods | 33 | 22.00% |
| ▷ Public methods | 100 | 66.67% |
| ▷ Protected methods | 19 | 12.67% |
| ▷ Private methods | 31 | 20.67% |
| Functions | 1 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 1 | 100.00% |
| Constants | 13 | |
| ▷ Global constants | 6 | 46.15% |
| ▷ Class constants | 7 | 53.85% |
| ▷ Public constants | 7 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
6 PNG files occupy 0.05MB with 0.02MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/flw-lock4.png | 0.21KB | 0.17KB | ▼ 19.91% |
| assets/images/flutterwave-icon.png | 0.37KB | 0.27KB | ▼ 28.98% |
| assets/images/flutterwave.png | 46.14KB | 10.42KB | ▼ 77.42% |
| assets/images/flw-lock.png | 0.24KB | 0.22KB | ▼ 6.94% |
| assets/images/rave-icon.png | 0.51KB | 0.40KB | ▼ 21.48% |