Benchmarks
Plugin footprint Passed 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.08MB] [CPU: ▼291.60ms] Passed 4 tests
Analyzing server-side resources used by sixa Container Block
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.68 ▲0.16 | 53.26 ▲0.34 |
| Dashboard /wp-admin | 3.52 ▲0.11 | 34.13 ▲1.30 |
| Posts /wp-admin/edit.php | 3.74 ▲0.10 | 37.05 ▲0.03 |
| Add New Post /wp-admin/post-new.php | 6.98 ▲0.00 | 93.14 ▼1,164.91 |
| Media Library /wp-admin/upload.php | 3.39 ▲0.09 | 24.04 ▼1.87 |
Server storage [IO: ▲0.97MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 126 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
sixa Container Block: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,763 ▲9 | 15.94 ▲0.13 | 6.31 ▼0.07 | 2.41 ▼0.23 |
| Dashboard /wp-admin | 2,895 ▲37 | 6.14 ▼0.12 | 117.54 ▼17.02 | 158.18 ▼0.57 |
| Posts /wp-admin/edit.php | 2,694 ▲3 | 3.23 ▲0.00 | 63.06 ▲1.55 | 139.78 ▲5.68 |
| Add New Post /wp-admin/post-new.php | 1,674 ▼43 | 16.80 ▼4.31 | 387.40 ▼110.16 | 154.73 ▼3.01 |
| Media Library /wp-admin/upload.php | 1,695 ▼3 | 5.49 ▼0.01 | 138.02 ▼2.00 | 179.98 ▼7.57 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
This plugin's uninstaller ran successfully
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 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 4× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
require(): Failed opening required 'wp-content/plugins/sixa-container-block/vendor/sixach/wp-snippets/vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/sixa-container-block/vendor/sixach/wp-snippets/sixa-snippets.php on line 34
- > PHP Fatal error
require(): Failed opening required 'wp-content/plugins/sixa-container-block/trunk/vendor/sixach/wp-snippets/vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/sixa-container-block/trunk/vendor/sixach/wp-snippets/sixa-snippets.php on line 34
- > PHP Warning
require(wp-content/plugins/sixa-container-block/trunk/vendor/sixach/wp-snippets/vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/sixa-container-block/trunk/vendor/sixach/wp-snippets/sixa-snippets.php on line 34
- > PHP Warning
require(wp-content/plugins/sixa-container-block/vendor/sixach/wp-snippets/vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/sixa-container-block/vendor/sixach/wp-snippets/sixa-snippets.php on line 34
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
7 plugin tags: gutenberg, section, wrapper, block, group...
sixa-container-block/index.php 85% from 13 tests
The main file in "sixa Container Block" v. 1.1.3 serves as a complement to information provided in readme.txt and as the entry point to the plugin
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("sixa-container-block.php" instead of "index.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Everything looks great! No dangerous files found in this plugin4,376 lines of code in 49 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 41 | 805 | 2,502 | 3,595 |
| PO File | 1 | 98 | 160 | 295 |
| Markdown | 2 | 99 | 0 | 270 |
| JSON | 2 | 0 | 0 | 213 |
| CSS | 2 | 0 | 0 | 2 |
| JavaScript | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.44 |
| Average class complexity | 16.06 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 56.00 |
| Average method complexity | 3.28 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 26.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 10 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 62 | |
| ▷ Abstract classes | 8 | 12.90% |
| ▷ Concrete classes | 54 | 87.10% |
| ▷ Final classes | 10 | 18.52% |
| Methods | 400 | |
| ▷ Static methods | 200 | 50.00% |
| ▷ Public methods | 324 | 81.00% |
| ▷ Protected methods | 50 | 12.50% |
| ▷ Private methods | 26 | 6.50% |
| Functions | 20 | |
| ▷ Named functions | 2 | 10.00% |
| ▷ Anonymous functions | 18 | 90.00% |
| Constants | 24 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 24 | 100.00% |
| ▷ Public constants | 20 | 83.33% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
No PNG files were detected