Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.09MB] [CPU: ▼3.04ms] Passed 4 tests
An overview of server-side resources used by Blocks for Products
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.56 ▲0.10 | 42.44 ▲4.80 |
| Dashboard /wp-admin | 3.39 ▲0.09 | 45.14 ▼3.81 |
| Posts /wp-admin/edit.php | 3.51 ▲0.15 | 49.80 ▲6.15 |
| Add New Post /wp-admin/post-new.php | 5.97 ▲0.09 | 78.87 ▼18.10 |
| Media Library /wp-admin/upload.php | 3.31 ▲0.08 | 36.52 ▲4.96 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 16 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_recent-posts |
| can_compress_scripts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Blocks for Products: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.33 ▼0.02 | 1.71 ▲0.16 | 43.84 ▲6.45 |
| Dashboard /wp-admin | 2,203 ▲26 | 5.52 ▼0.08 | 85.02 ▼1.92 | 42.22 ▼0.45 |
| Posts /wp-admin/edit.php | 2,112 ▲9 | 1.96 ▼0.02 | 34.74 ▼6.54 | 32.70 ▲1.26 |
| Add New Post /wp-admin/post-new.php | 1,537 ▲11 | 23.41 ▲0.35 | 675.07 ▲48.53 | 57.31 ▼1.74 |
| Media Library /wp-admin/upload.php | 1,411 ▲17 | 4.19 ▼0.02 | 98.04 ▼4.27 | 41.18 ▼3.07 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Almost there! Just fix the following items
- 4× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/blocks-for-products/blocks-for-products.php
- > /wp-content/plugins/blocks-for-products/modules/dependence/includes/views/html-notice.php
- > /wp-content/plugins/blocks-for-products/modules/dependence/class-module-dependence.php
- > /wp-content/plugins/blocks-for-products/modules/woocommerce/class-module-woocommerce.php
- 3× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/blocks-for-products/modules/woocommerce/views/back-to-blocks.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/blocks-for-products/modules/woocommerce/views/new-editor.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/blocks-for-products/modules/woocommerce/views/editor.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
5 plugin tags: woocommerce, vizir, mariovalney, products, gutenberg
blocks-for-products/blocks-for-products.php 85% from 13 tests
"Blocks for Products" version 1.1.1's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
It is important to fix the following:
- Requires at least: The required version number must match the one declared in readme.txt ("4.7" instead of "3.6.5")
- Domain Path: The domain path folder does not exist ("/languages")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
No dangerous file extensions were detected396 lines of code in 12 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 9 | 117 | 264 | 355 |
| JavaScript | 2 | 2 | 0 | 21 |
| CSS | 1 | 2 | 0 | 20 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.42 |
| Average class complexity | 20.00 |
| ▷ Minimum class complexity | 6.00 |
| ▷ Maximum class complexity | 28.00 |
| Average method complexity | 3.04 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 13.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 28 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 20 | 71.43% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 8 | 28.57% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 9 | |
| ▷ Global constants | 7 | 77.78% |
| ▷ Class constants | 2 | 22.22% |
| ▷ Public constants | 2 | 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
There were not PNG files found in your plugin