Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.56MB] [CPU: ▲4.82ms] 75% from 4 tests
Analyzing server-side resources used by FacturaONE para WooCommerce
Please fix the following
- CPU: Try to keep total CPU usage under 500.00ms (currently 523.69ms on /wp-admin/admin.php?page=WPFacturaOne)
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.08 ▲0.61 | 45.62 ▲7.57 |
Dashboard /wp-admin | 3.90 ▲0.59 | 52.34 ▲1.00 |
Posts /wp-admin/edit.php | 3.95 ▲0.59 | 52.82 ▲3.99 |
Add New Post /wp-admin/post-new.php | 6.42 ▲0.53 | 102.89 ▲18.97 |
Media Library /wp-admin/upload.php | 3.76 ▲0.52 | 40.18 ▲6.70 |
FacturaONE /wp-admin/admin.php?page=WPFacturaOne | 4.29 | 523.69 |
Server storage [IO: ▲1.36MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 36 new files
Database: 1 new table, 16 new options
New tables |
---|
wp_fone_item_clients |
New WordPress options |
---|
FacturaONE_pers_agotado |
can_compress_scripts |
FacturaONE_preciosusuariosregistrados |
FacturaONE_version |
theysaidso_admin_options |
FONE_OcultaProductosNOIMAGEN |
FacturaONE_backorder_message |
FacturaONE_updatedver |
widget_recent-comments |
FacturaONE_conexionSSL |
... |
Browser metrics Passed 4 tests
A check of browser resources used by FacturaONE para WooCommerce
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,792 ▲30 | 14.23 ▼0.18 | 1.70 ▲0.06 | 43.00 ▲3.76 |
Dashboard /wp-admin | 2,197 ▲23 | 5.62 ▼0.02 | 93.15 ▼6.23 | 34.26 ▼11.30 |
Posts /wp-admin/edit.php | 2,102 ▲2 | 1.94 ▼0.09 | 39.58 ▼3.37 | 30.86 ▼5.98 |
Add New Post /wp-admin/post-new.php | 1,538 ▲12 | 23.24 ▲0.08 | 666.50 ▲61.78 | 54.81 ▲4.29 |
Media Library /wp-admin/upload.php | 1,402 ▼1 | 4.15 ▼0.07 | 98.15 ▼3.12 | 39.68 ▼4.19 |
FacturaONE /wp-admin/admin.php?page=WPFacturaOne | 1,501 | 2.48 | 41.41 | 35.20 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- The plugin did not uninstall successfully, leaving 1 table in the database
- wp_fone_item_clients
- The uninstall procedure has failed, leaving 16 options in the database
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- FacturaONE_pers_agotado
- widget_recent-comments
- FacturaONE_updatedver
- widget_recent-posts
- FacturaONE_preciosusuariosregistrados
- FacturaONE_version
- FacturaONE_ajax_cicle
- ...
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not 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 fix the following items
- 16× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-facturaone/FONE_custom_products.php:3
- > PHP Notice
Undefined index: action in wp-content/plugins/wp-facturaone/update_stock.php on line 64
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-facturaone/FONE_custom_users.php:3
- > PHP Notice
Undefined index: action in wp-content/plugins/wp-facturaone/update_stock.php on line 79
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/wp-facturaone/FONE_custom_tarifas.php:3
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/wp-facturaone/FONE_subcategories.php:2
- > PHP Notice
Undefined index: action in wp-content/plugins/wp-facturaone/update_users.php on line 20
- > PHP Fatal error
Uncaught Error: Call to undefined function did_action() in wp-content/plugins/wp-facturaone/class-tgm-plugin-activation.php:2110
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-facturaone/FONE_custom_products.php:3
- > PHP Notice
Undefined index: action in wp-content/plugins/wp-facturaone/update_users.php on line 2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that require attention:
- Contributors: Plugin contributors field is missing
wp-facturaone/wp-facturaone.php Passed 13 tests
The main file in "FacturaONE para WooCommerce" v. 3.13 serves as a complement to information provided in readme.txt and as the entry point to the plugin
82 characters long description:
La forma más fácil de trabajar con tu tienda online desde nuestro ERP FACTURAONE
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected9,191 lines of code in 28 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 18 | 912 | 2,354 | 5,988 |
JavaScript | 6 | 497 | 187 | 2,045 |
CSS | 4 | 50 | 5 | 1,158 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.43 |
Average class complexity | 36.20 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 206.00 |
Average method complexity | 3.84 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 34.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 10 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 10 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 124 | |
▷ Static methods | 5 | 4.03% |
▷ Public methods | 101 | 81.45% |
▷ Protected methods | 23 | 18.55% |
▷ Private methods | 0 | 0.00% |
Functions | 142 | |
▷ Named functions | 141 | 99.30% |
▷ Anonymous functions | 1 | 0.70% |
Constants | 3 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 3 | 100.00% |
▷ Public constants | 3 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
4 PNG files occupy 0.35MB with 0.23MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/plug_image.png | 170.97KB | 40.48KB | ▼ 76.32% |
assets/plugimage.png | 170.97KB | 40.48KB | ▼ 76.32% |
assets/btncancel.png | 5.79KB | 2.72KB | ▼ 53.04% |
assets/icon-256x256.png | 10.66KB | 4.93KB | ▼ 53.79% |