Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼9.25ms] Passed 4 tests
Server-side resources used by Fygaro WC Plugin
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.01 | 42.44 ▼1.67 |
Dashboard /wp-admin | 3.32 ▼0.03 | 49.76 ▼17.79 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.03 ▼2.04 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 94.66 ▼15.51 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 34.29 ▼0.56 |
Server storage [IO: ▲0.83MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 24 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
widget_recent-comments |
widget_theysaidso_widget |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Fygaro WC Plugin
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,790 ▲18 | 14.35 ▼0.03 | 1.63 ▼0.28 | 42.20 ▼1.60 |
Dashboard /wp-admin | 2,195 ▲21 | 5.58 ▼0.06 | 88.19 ▼9.00 | 36.92 ▼6.84 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 2.01 ▲0.02 | 36.35 ▼4.18 | 34.83 ▼1.27 |
Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.02 ▼0.22 | 673.09 ▼53.57 | 49.08 ▼10.22 |
Media Library /wp-admin/upload.php | 1,397 ▼3 | 4.19 ▲0.01 | 98.30 ▼3.06 | 45.28 ▲2.64 |
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
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- 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
Good news, no errors were detected
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
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Class 'Automattic\\WooCommerce\\Blocks\\Payments\\Integrations\\AbstractPaymentMethodType' not found in wp-content/plugins/fygaro/includes/blocks/class-wc-fygaro-payments-blocks.php:9
- > 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 83% from 29 tests
readme.txt 94% 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 to be fixed:
- Screenshots: Add an image for screenshot #1 (Fygaro WooCommerce Plugin)
fygaro/woocommerce-gateway-fygaro.php 69% from 13 tests
"Fygaro WC Plugin" version 0.0.8's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("fygaro.php" instead of "woocommerce-gateway-fygaro.php")
- Domain Path: The domain path points to a folder that does not exist ("/i18n/languages/")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Requires at least: Required version must match the one declared in readme.txt ("4.7" instead of "4.2")
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 plugin19,532 lines of code in 20 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JSON | 2 | 0 | 0 | 18,725 |
PHP | 5 | 130 | 246 | 424 |
JavaScript | 5 | 26 | 14 | 181 |
SVG | 4 | 0 | 3 | 88 |
CSS | 1 | 13 | 3 | 43 |
XML | 1 | 7 | 6 | 42 |
Bourne Shell | 1 | 4 | 3 | 21 |
Markdown | 1 | 4 | 0 | 8 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.24 |
Average class complexity | 13.00 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 33.00 |
Average method complexity | 3.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 17.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 3 | 100.00% |
▷ Final classes | 1 | 33.33% |
Methods | 18 | |
▷ Static methods | 6 | 33.33% |
▷ Public methods | 18 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 2 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 2 | 100.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
3 PNG files occupy 0.16MB with 0.13MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/fygaro.png | 43.20KB | 21.17KB | ▼ 51.00% |
assets/images/tasa_cero.png | 60.83KB | 3.60KB | ▼ 94.08% |
assets/images/mini_cuotas.png | 57.69KB | 3.70KB | ▼ 93.59% |