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.04MB] [CPU: ▼6.09ms] Passed 4 tests
Analyzing server-side resources used by Instapago Payment Gateway for WooCommerce
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.04 | 42.92 ▲0.57 |
Dashboard /wp-admin | 3.34 ▲0.04 | 51.99 ▼2.02 |
Posts /wp-admin/edit.php | 3.39 ▲0.04 | 50.89 ▲1.25 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.04 | 86.30 ▼17.01 |
Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 34.28 ▼5.89 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 22 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_recent-posts |
can_compress_scripts |
widget_theysaidso_widget |
db_upgraded |
widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for Instapago Payment Gateway for WooCommerce
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲29 | 14.74 ▲0.16 | 1.87 ▼0.00 | 46.75 ▲1.74 |
Dashboard /wp-admin | 2,206 ▲15 | 4.84 ▼1.06 | 111.36 ▲1.60 | 42.56 ▼0.49 |
Posts /wp-admin/edit.php | 2,089 ▼3 | 2.03 ▲0.06 | 37.94 ▼3.65 | 31.96 ▼3.36 |
Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 23.11 ▼0.07 | 622.69 ▼52.39 | 56.09 ▼0.61 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.21 ▲0.09 | 99.26 ▼15.71 | 42.67 ▼6.51 |
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
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- can_compress_scripts
- 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 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following items
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/instapago/includes/admin-options.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/instapago/includes/payment-fields.php:21
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
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
These attributes need your attention:
- Screenshots: A description for screenshot #4 is missing in instapago/assets to your readme.txt
- Tags: Please delete some tags, you are using 11 tag instead of maximum 10
instapago/Instapago.php 85% from 13 tests
"Instapago Payment Gateway for WooCommerce" version 7.0.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Description: Please don't use more than 140 characters for the plugin description (currently 363 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("instapago.php" instead of "Instapago.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Good job! No executable or dangerous file extensions detected680 lines of code in 12 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 41 | 122 | 376 |
Sass | 1 | 5 | 0 | 90 |
CSS | 2 | 20 | 22 | 86 |
HTML | 2 | 4 | 5 | 82 |
JavaScript | 2 | 0 | 0 | 37 |
Markdown | 1 | 7 | 0 | 9 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.15 |
Average class complexity | 10.00 |
▷ Minimum class complexity | 10.00 |
▷ Maximum class complexity | 10.00 |
Average method complexity | 2.12 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 7.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 | 8 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 8 | 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.05MB with 0.01MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/instapago-visa-mastercard.png | 2.64KB | 2.66KB | 0.00% |
assets/images/instapago-gateway.png | 1.16KB | 1.17KB | 0.00% |
assets/images/instapago.png | 47.56KB | 9.86KB | ▼ 79.27% |