Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.42MB] [CPU: ▲2.81ms] Passed 4 tests
Analyzing server-side resources used by Before After Slider for WooCommerce - eBEAF
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.87 ▲0.40 | 38.11 ▼2.74 |
| Dashboard /wp-admin | 3.78 ▲0.48 | 57.81 ▲14.75 |
| Posts /wp-admin/edit.php | 3.83 ▲0.48 | 58.55 ▲8.11 |
| Add New Post /wp-admin/post-new.php | 6.30 ▲0.41 | 89.96 ▼0.18 |
| Media Library /wp-admin/upload.php | 3.62 ▲0.39 | 39.13 ▲6.03 |
| eBEAF /wp-admin/admin.php?page=beafwc-add-new-slider | 3.59 | 35.44 |
| Add New Slider /wp-admin/admin.php?page=add-new-slider | 3.59 | 35.44 |
Server storage [IO: ▲2.50MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 36 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| widget_recent-posts |
| tf_display_admin_notice_time |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| beafwc_installation_date |
| can_compress_scripts |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Before After Slider for WooCommerce - eBEAF
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,139 ▲352 | 15.61 ▲0.87 | 5.21 ▲3.26 | 28.58 ▼17.18 |
| Dashboard /wp-admin | 2,415 ▲235 | 6.50 ▲0.85 | 124.93 ▲27.10 | 46.14 ▲3.97 |
| Posts /wp-admin/edit.php | 2,354 ▲251 | 3.66 ▲1.72 | 62.18 ▲15.86 | 39.56 ▲2.47 |
| Add New Post /wp-admin/post-new.php | 1,592 ▲66 | 23.42 ▲0.33 | 590.43 ▼111.24 | 35.87 ▼40.34 |
| Media Library /wp-admin/upload.php | 1,491 ▲88 | 4.43 ▲0.14 | 88.39 ▼24.17 | 44.66 ▼2.75 |
| eBEAF /wp-admin/admin.php?page=beafwc-add-new-slider | 723 | 1.50 | 10.51 | 20.91 |
| Add New Slider /wp-admin/admin.php?page=add-new-slider | 723 | 1.69 | 10.45 | 20.20 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- This plugin did not uninstall successfully, leaving 8 options in the database
- tf_display_admin_notice_time
- beafwc_installation_date
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Please fix the following server-side errors
- 4 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=add-new-slider
- > Warning in wp-includes/pluggable.php+1438
Cannot modify header information - headers already sent by (output started at wp-includes/script-loader.php:2838)
SRP Passed 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Everything seems fine, however this is by no means an exhaustive test
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need your attention:
- Donate link: Invalid URI ("")
- Tags: Please delete some tags, you are using 13 tag instead of maximum 10
before-after-for-woocommerce/before-after-for-woocommerce.php 77% from 13 tests
The main PHP file in "Before After Slider for WooCommerce - eBEAF" ver. 1.2.1 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Description: Keep the plugin description shorter than 140 characters (currently 164 characters long)
- Domain Path: The domain path is invalid: folder "/languages" does not exist
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
There were no executable files found in this plugin4,873 lines of code in 20 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 10 | 577 | 770 | 2,605 |
| CSS | 3 | 244 | 22 | 1,218 |
| JavaScript | 5 | 249 | 130 | 809 |
| Markdown | 1 | 70 | 0 | 196 |
| JSON | 1 | 0 | 0 | 45 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.35 |
| Average class complexity | 43.60 |
| ▷ Minimum class complexity | 9.00 |
| ▷ Maximum class complexity | 86.00 |
| Average method complexity | 3.24 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 20.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 5 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 5 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 95 | |
| ▷ Static methods | 1 | 1.05% |
| ▷ Public methods | 61 | 64.21% |
| ▷ Protected methods | 6 | 6.32% |
| ▷ Private methods | 28 | 29.47% |
| Functions | 25 | |
| ▷ Named functions | 23 | 92.00% |
| ▷ Anonymous functions | 2 | 8.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
13 PNG files occupy 1.18MB with 0.44MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/image/BLACK_FRIDAY_BACKGROUND_GRUNGE_notice-2022.png | 249.07KB | 267.93KB | 0.00% |
| assets/image/style3.png | 1.29KB | 0.65KB | ▼ 49.81% |
| assets/image/style2.png | 0.86KB | 0.45KB | ▼ 47.90% |
| assets/image/style6.png | 0.97KB | 0.52KB | ▼ 46.83% |
| assets/image/style5.png | 1.34KB | 0.76KB | ▼ 43.04% |