Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼0.01MB] [CPU: ▼9.94ms] Passed 4 tests
A check of server-side resources used by Awesome for WC
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 53.24 ▲9.02 |
Dashboard /wp-admin | 3.31 ▼0.04 | 52.48 ▼15.21 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 49.72 ▼3.83 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 85.56 ▼15.77 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.86 ▼4.94 |
Server storage [IO: ▲6.44MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 62 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
can_compress_scripts |
widget_recent-comments |
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-posts |
Browser metrics Passed 4 tests
Awesome for WC: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,799 ▲53 | 14.17 ▼0.38 | 1.69 ▲0.04 | 46.90 ▲4.58 |
Dashboard /wp-admin | 2,202 ▲25 | 5.52 ▼0.05 | 91.44 ▲2.53 | 37.97 ▼3.97 |
Posts /wp-admin/edit.php | 2,111 ▲14 | 2.04 ▲0.05 | 38.63 ▲2.43 | 35.42 ▼3.35 |
Add New Post /wp-admin/post-new.php | 1,538 ▲12 | 22.98 ▼0.52 | 646.12 ▼62.06 | 58.58 ▲4.87 |
Media Library /wp-admin/upload.php | 1,407 ▲7 | 4.19 ▼0.13 | 100.47 ▼16.69 | 48.19 ▼1.27 |
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
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% 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
The following issues need your attention
- 4× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/awesome-wc/components/stWcCouponCode/includes/hooks.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/awesome-wc/includes/hooks.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/awesome-wc/components/stWcAwesomeBusinessHours/includes/hooks.php:2
- > PHP Fatal error
Uncaught Error: Class 'Elementor\\Widget_Base' not found in wp-content/plugins/awesome-wc/components/stWcAwesomeBusinessHours/includes/elementor/widgetAwesomeBusinessHours.php: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 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need to be fixed:
- Tags: You are using too many tags: 14 tag instead of maximum 10
awesome-wc/awesome.php 92% from 13 tests
The main PHP script in "Awesome for WC" version 1.0.1 is automatically included on every request by WordPress
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("awesome-wc.php" instead of "awesome.php")
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 detected36,509 lines of code in 53 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 13 | 4,734 | 139 | 25,054 |
JavaScript | 19 | 1,134 | 1,446 | 9,195 |
PHP | 21 | 457 | 370 | 2,260 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.42 |
Average class complexity | 21.00 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 55.00 |
Average method complexity | 2.39 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 17.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 11 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 11 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 158 | |
▷ Static methods | 21 | 13.29% |
▷ Public methods | 143 | 90.51% |
▷ Protected methods | 2 | 1.27% |
▷ Private methods | 13 | 8.23% |
Functions | 13 | |
▷ Named functions | 13 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 14 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 14 | 100.00% |
▷ Public constants | 14 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
3 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/img/product-default.png | 16.80KB | 4.69KB | ▼ 72.10% |
assets/img/wp-icon.png | 0.31KB | 0.27KB | ▼ 14.29% |
assets/img/icon.png | 0.81KB | 0.52KB | ▼ 35.46% |