Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▲1.18ms] Passed 4 tests
Server-side resources used by FCF-Pay
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.01 | 36.87 ▼2.98 |
Dashboard /wp-admin | 3.32 ▲0.02 | 52.44 ▲4.33 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 49.39 ▲2.32 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 93.50 ▲6.33 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 35.79 ▲1.05 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 24 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_recent-posts |
theysaidso_admin_options |
db_upgraded |
can_compress_scripts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
FCF-Pay: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.23 ▼1.17 | 1.73 ▼0.07 | 39.95 ▼3.83 |
Dashboard /wp-admin | 2,209 ▲21 | 5.91 ▲0.05 | 110.15 ▼7.49 | 41.21 ▼1.40 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 1.99 ▼0.02 | 39.43 ▲3.87 | 36.35 ▼0.51 |
Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 23.17 ▲0.12 | 626.28 ▼11.70 | 52.07 ▼3.73 |
Media Library /wp-admin/upload.php | 1,391 ▲9 | 4.29 ▲0.00 | 95.29 ▼3.57 | 40.77 ▼3.54 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_recent-posts
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
Good news, no errors were detected
SRP 50% from 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
The following issues need your attention
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/fcf-pay-payment-gateway/core/includes/classes/class-fcf-pay-order-paid.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/fcf-pay-payment-gateway/core/includes/classes/class-fcf-pay-order-status.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Please fix the following attributes:
- Requires php: The plugin version is formatted incorrectly
- Donate link: Invalid URI found ("")
fcf-pay-payment-gateway/fcf-pay.php 85% from 13 tests
The entry point to "FCF-Pay" version 1.1.2 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Main file name: It is recommended to name the main PHP file as the plugin slug ("fcf-pay-payment-gateway.php" instead of "fcf-pay.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Everything looks great! No dangerous files found in this plugin804 lines of code in 14 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 10 | 219 | 360 | 764 |
JavaScript | 2 | 10 | 58 | 36 |
CSS | 2 | 1 | 6 | 4 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
Average class complexity | 13.25 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 30.00 |
Average method complexity | 3.28 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 26.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 1 | 12.50% |
Methods | 44 | |
▷ Static methods | 1 | 2.27% |
▷ Public methods | 41 | 93.18% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 3 | 6.82% |
Functions | 4 | |
▷ Named functions | 3 | 75.00% |
▷ Anonymous functions | 1 | 25.00% |
Constants | 7 | |
▷ Global constants | 7 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
1 PNG file occupies 0.02MB with 0.01MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
core/includes/assets/images/logo.png | 24.00KB | 10.34KB | ▼ 56.91% |