Benchmarks
Plugin footprint 83% from 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.01MB] [CPU: ▼5.46ms] Passed 4 tests
Analyzing server-side resources used by Opayo Direct Gateway for Gravity Forms
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 35.11 ▼4.42 |
Dashboard /wp-admin | 3.31 ▲0.01 | 45.11 ▼3.13 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 48.07 ▼8.69 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 92.49 ▼1.85 |
Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 36.69 ▼5.60 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 12 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_recent-comments |
widget_recent-posts |
db_upgraded |
can_compress_scripts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for Opayo Direct Gateway for Gravity Forms
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.53 ▲0.16 | 1.54 ▼0.14 | 36.55 ▼7.62 |
Dashboard /wp-admin | 2,189 ▲15 | 5.62 ▲0.09 | 92.81 ▲5.81 | 41.20 ▼1.45 |
Posts /wp-admin/edit.php | 2,103 ▼0 | 2.02 ▲0.01 | 38.54 ▼2.88 | 35.90 ▼1.36 |
Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.14 ▼0.13 | 700.30 ▲93.21 | 59.95 ▲4.22 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.20 ▲0.02 | 99.32 ▼4.98 | 41.09 ▼4.78 |
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
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
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
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
Please fix the following items
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/sagepay-direct-gateway-for-gravity-forms/class-gf-sagepay-direct.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/sagepay-direct-gateway-for-gravity-forms/sagepay-direct.php:22
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
8 plugin tags: gravityforms, opayo direct, payment gateway, credit card, opayo go...
sagepay-direct-gateway-for-gravity-forms/sagepay-direct.php 85% from 13 tests
The main PHP file in "Opayo Direct Gateway for Gravity Forms" ver. 1.0.2 adds more information about the plugin and also serves as the entry point for this plugin
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("sagepay-direct-gateway-for-gravity-forms.php" instead of "sagepay-direct.php")
- 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
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Everything looks great! No dangerous files found in this plugin903 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 334 | 79 | 903 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.29 |
Average class complexity | 58.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 114.00 |
Average method complexity | 4.45 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 34.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 33 | |
▷ Static methods | 4 | 12.12% |
▷ Public methods | 25 | 75.76% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 8 | 24.24% |
Functions | 1 | |
▷ Named functions | 1 | 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
PNG files should be compressed to save space and minimize bandwidth usage
7 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/tick.png | 0.52KB | 0.52KB | 0.00% |
images/active1.png | 0.71KB | 0.63KB | ▼ 11.28% |
images/stop.png | 0.68KB | 0.78KB | 0.00% |
images/add.png | 3.37KB | 0.66KB | ▼ 80.54% |
images/remove.png | 3.32KB | 0.62KB | ▼ 81.33% |