Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.16MB] [CPU: ▼4.99ms] Passed 4 tests
Server-side resources used by Frontend Product Editor for WooCommerce
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.64 ▲0.18 | 44.56 ▲0.14 |
| Dashboard /wp-admin | 3.47 ▲0.13 | 54.05 ▼16.71 |
| Posts /wp-admin/edit.php | 3.59 ▲0.23 | 53.87 ▲4.78 |
| Add New Post /wp-admin/post-new.php | 6.06 ▲0.17 | 91.47 ▼8.15 |
| Media Library /wp-admin/upload.php | 3.40 ▲0.17 | 43.80 ▲6.53 |
Server storage [IO: ▲4.40MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 31 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Frontend Product Editor for WooCommerce
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.17 ▼0.21 | 1.66 ▼0.26 | 45.02 ▲2.71 |
| Dashboard /wp-admin | 2,195 ▲24 | 5.62 ▼0.04 | 88.52 ▼5.75 | 38.15 ▼6.50 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.02 ▲0.04 | 40.09 ▲3.31 | 37.24 ▼3.55 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲10 | 23.18 ▲0.17 | 626.70 ▼35.72 | 51.15 ▼9.96 |
| Media Library /wp-admin/upload.php | 1,397 ▼0 | 4.21 ▲0.03 | 101.86 ▲2.06 | 45.93 ▲0.50 |
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
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- db_upgraded
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
Even though everything seems fine, this is not an exhaustive test
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
Almost there! Just fix the following items
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Warning
Use of undefined constant WPVFPE_PATH - assumed 'WPVFPE_PATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/frontend-product-editor/includes/init.php on line 29
- > PHP Fatal error
Uncaught Error: Call to undefined function WPV_FPE\\add_action() in wp-content/plugins/frontend-product-editor/includes/init.php:34
- > PHP Fatal error
Uncaught Error: Class 'WPV_FPE\\Editor\\BaseEditor' not found in wp-content/plugins/frontend-product-editor/includes/editor/single.php:5
- > PHP Warning
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 86% from 29 tests
readme.txt 94% from 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
These attributes need your attention:
- Screenshots: Please describe screenshot #5 in frontend-product-editor/assets to your readme.txt
frontend-product-editor/frontend-product-editor.php 77% from 13 tests
"Frontend Product Editor for WooCommerce" version 1.1.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Domain Path: The domain path follows the same naming rules as the domain name, using only dashes and lowercase characters ("/")
- Domain Path: Prefix the domain path with a forward slash character ("//")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Good job! No executable or dangerous file extensions detected1,247 lines of code in 24 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 15 | 309 | 469 | 1,162 |
| JavaScript | 4 | 4 | 17 | 76 |
| JSON | 1 | 0 | 0 | 5 |
| CSS | 3 | 0 | 0 | 3 |
| SVG | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.47 |
| Average class complexity | 18.44 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 47.00 |
| Average method complexity | 3.49 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 31.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 4 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 9 | |
| ▷ Abstract classes | 1 | 11.11% |
| ▷ Concrete classes | 8 | 88.89% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 64 | |
| ▷ Static methods | 24 | 37.50% |
| ▷ Public methods | 59 | 92.19% |
| ▷ Protected methods | 3 | 4.69% |
| ▷ Private methods | 2 | 3.12% |
| Functions | 4 | |
| ▷ Named functions | 1 | 25.00% |
| ▷ Anonymous functions | 3 | 75.00% |
| Constants | 7 | |
| ▷ Global constants | 7 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
There were not PNG files found in your plugin