Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.48MB] [CPU: ▼4.29ms] Passed 4 tests
Analyzing server-side resources used by Woo Layout Editor
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.00 ▲0.54 | 45.41 ▲3.43 |
| Dashboard /wp-admin | 3.82 ▲0.51 | 53.05 ▼1.77 |
| Posts /wp-admin/edit.php | 3.87 ▲0.51 | 53.84 ▼1.52 |
| Add New Post /wp-admin/post-new.php | 6.34 ▲0.45 | 102.04 ▼17.30 |
| Media Library /wp-admin/upload.php | 3.68 ▲0.45 | 43.81 ▲8.45 |
| Layout Editor /wp-admin/admin.php?page=my-custom-submenu-page | 3.65 | 40.25 |
Server storage [IO: ▲2.11MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 52 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-comments |
| db_upgraded |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| woolayedtil_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Woo Layout Editor
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.31 ▼0.04 | 1.72 ▼0.39 | 38.82 ▼2.05 |
| Dashboard /wp-admin | 2,192 ▲15 | 5.65 ▲0.01 | 91.56 ▼4.91 | 41.92 ▲2.21 |
| Posts /wp-admin/edit.php | 2,100 ▼3 | 2.02 ▲0.03 | 38.38 ▼3.81 | 36.03 ▲1.53 |
| Add New Post /wp-admin/post-new.php | 1,525 ▼23 | 21.87 ▲3.47 | 640.45 ▲13.09 | 63.07 ▼4.86 |
| Media Library /wp-admin/upload.php | 1,397 ▼3 | 4.23 ▲0.01 | 94.98 ▼12.37 | 41.18 ▼7.08 |
| Layout Editor /wp-admin/admin.php?page=my-custom-submenu-page | 1,829 | 3.18 | 64.96 | 44.68 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests 50% 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)
Good news, no errors were detected
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
Please fix the following
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/woo-layout-editor/woo-product-editor.php
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-layout-editor/shop_layout.php:75
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-layout-editor/shop_products_layout.php:69
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-layout-editor/product_layout.php:71
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Screenshots: Screenshot #1 (Woo Layout Editor in action) image not found
woo-layout-editor/woo-product-editor.php 85% from 13 tests
The main PHP script in "Woo Layout Editor" version 1.5.4 is automatically included on every request by WordPress
You should first fix the following items:
- Domain Path: The domain path folder was not found ("/languages")
- Main file name: The principal plugin file should be the same as the plugin slug ("woo-layout-editor.php" instead of "woo-product-editor.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Good job! No executable or dangerous file extensions detected13,460 lines of code in 43 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| SVG | 1 | 0 | 0 | 2,671 |
| CSS | 3 | 41 | 26 | 2,624 |
| PHP | 6 | 460 | 570 | 2,405 |
| JavaScript | 5 | 380 | 395 | 2,234 |
| Sass | 14 | 34 | 34 | 1,768 |
| LESS | 14 | 34 | 44 | 1,758 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.39 |
| Average class complexity | 163.50 |
| ▷ Minimum class complexity | 130.00 |
| ▷ Maximum class complexity | 197.00 |
| Average method complexity | 4.82 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 57.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 85 | |
| ▷ Static methods | 1 | 1.18% |
| ▷ Public methods | 69 | 81.18% |
| ▷ Protected methods | 16 | 18.82% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 54 | |
| ▷ Named functions | 54 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 21 | |
| ▷ Global constants | 21 | 100.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
There were not PNG files found in your plugin