Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲5.04MB] [CPU: ▲20.27ms] 75% from 4 tests
A check of server-side resources used by WP Tools Divi Product Carousel
It is recommended to improve the following
- Extra RAM: The extra memory usage should kept under 5MB (currently 5.04MB on /wp-admin/admin.php?page=wp-tools-divi-product-carousel)
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 8.93 ▲5.47 | 71.56 ▲30.21 |
| Dashboard /wp-admin | 8.95 ▲5.64 | 77.90 ▲16.48 |
| Posts /wp-admin/edit.php | 8.95 ▲5.59 | 64.56 ▲19.65 |
| Add New Post /wp-admin/post-new.php | 9.34 ▲3.46 | 119.79 ▲14.72 |
| Media Library /wp-admin/upload.php | 8.95 ▲5.72 | 66.02 ▲33.30 |
| Freemius Debug [v.2.5.10] /wp-admin/admin.php?page=freemius | 8.95 | 58.24 |
| Divi Product Carousel /wp-admin/admin.php?page=wp-tools-divi-product-carousel | 8.95 | 61.20 |
Server storage [IO: ▲3.34MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 250 new files
Database: no new tables, 9 new options
| New WordPress options |
|---|
| fs_accounts |
| widget_recent-posts |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
| fs_active_plugins |
| db_upgraded |
| fs_debug_mode |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for WP Tools Divi Product Carousel
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,818 ▲83 | 14.48 ▲0.10 | 1.79 ▲0.07 | 32.11 ▼9.43 |
| Dashboard /wp-admin | 2,224 ▲39 | 5.82 ▲0.01 | 97.73 ▼4.04 | 40.64 ▼5.81 |
| Posts /wp-admin/edit.php | 2,107 ▲18 | 2.04 ▲0.05 | 35.19 ▼2.88 | 35.48 ▲1.83 |
| Add New Post /wp-admin/post-new.php | 1,519 ▼14 | 23.06 ▲0.19 | 613.70 ▲33.66 | 62.37 ▲3.75 |
| Media Library /wp-admin/upload.php | 1,409 ▲18 | 4.22 ▲0.08 | 108.94 ▲9.60 | 50.41 ▲7.97 |
| Freemius Debug [v.2.5.10] /wp-admin/admin.php?page=freemius | 1,081 | 1.68 | 23.75 | 25.96 |
| Divi Product Carousel /wp-admin/admin.php?page=wp-tools-divi-product-carousel | 954 | 1.71 | 31.27 | 57.90 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- Uninstall procedure had uncaught errors
- > Notice in wp-content/plugins/wp-tools-divi-product-carousel/freemius/includes/class-freemius.php+8486
Undefined property: stdClass::$plugins
- This plugin does not fully uninstall, leaving 9 options in the database
- db_upgraded
- can_compress_scripts
- fs_debug_mode
- widget_theysaidso_widget
- fs_active_plugins
- theysaidso_admin_options
- fs_accounts
- widget_recent-comments
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 0% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/wp-tools-divi-product-carousel/resources/views/wptools-divi-carousel-blog-item.php
- 21× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Pimple\\Container' not found in wp-content/plugins/wp-tools-divi-product-carousel/src/Loader.php:9
- > PHP Fatal error
Uncaught Error: Class 'DiviExtension' not found in wp-content/plugins/wp-tools-divi-product-carousel/includes/modules/DiviProductCarouselExtension.php:6
- > PHP Notice
Undefined variable: featured_image in wp-content/plugins/wp-tools-divi-product-carousel/resources/views/wptools-divi-carousel-blog-item.php on line 8
- > PHP Notice
Undefined variable: blog in wp-content/plugins/wp-tools-divi-product-carousel/resources/views/wptools-divi-carousel-blog-item.php on line 13
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Container\otFoundExceptionInterface' not found in wp-content/plugins/wp-tools-divi-product-carousel/vendor/pimple/pimple/src/Pimple/Exception/InvalidServiceIdentifierException.php:36
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Container\\ContainerExceptionInterface' not found in wp-content/plugins/wp-tools-divi-product-carousel/vendor/pimple/pimple/src/Pimple/Exception/ExpectedInvokableException.php:36
- > PHP Fatal error
Uncaught Error: Class 'ET_Builder_Module' not found in wp-content/plugins/wp-tools-divi-product-carousel/includes/modules/DiviCarouselProductItemModule/DiviCarouselProductItemModule.php:10
- > PHP Notice
Undefined variable: props in wp-content/plugins/wp-tools-divi-product-carousel/resources/views/wptools-divi-carousel-blog-item.php on line 2
- > PHP Notice
Undefined variable: props in wp-content/plugins/wp-tools-divi-product-carousel/resources/views/wptools-divi-carousel-blog-item.php on line 16
- > PHP Notice
Trying to get property 'post_title' of non-object in wp-content/plugins/wp-tools-divi-product-carousel/resources/views/wptools-divi-carousel-blog-item.php on line 13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
6 plugin tags: product carousel, woocommerce carousel divi, woocommerce divi carousel, divi, divi product module...
wp-tools-divi-product-carousel/wp-tools-divi-product-carousel.php 92% from 13 tests
"WP Tools Divi Product Carousel" version 1.5.1's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
The following require your attention:
- Domain Path: The domain path is invalid: folder "/languages" does not exist
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
There were no executable files found in this plugin37,879 lines of code in 190 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 152 | 8,293 | 18,193 | 34,437 |
| JavaScript | 10 | 891 | 123 | 2,367 |
| CSS | 16 | 47 | 5 | 306 |
| Sass | 2 | 27 | 5 | 262 |
| JSON | 3 | 0 | 0 | 174 |
| LESS | 1 | 11 | 5 | 152 |
| reStructuredText | 1 | 96 | 139 | 97 |
| YAML | 1 | 7 | 1 | 39 |
| XML | 1 | 2 | 0 | 16 |
| SVG | 1 | 1 | 0 | 13 |
| Markdown | 1 | 5 | 0 | 8 |
| Ruby | 1 | 2 | 0 | 8 |
PHP code 50% from 2 tests
This plugin's cyclomatic complexity and code structure detailed below
It is recommended to fix the following
- Cyclomatic complexity of classes has to be reduced to less than 1000 (currently 3,073)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.62 |
| Average class complexity | 64.38 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 3,073.00 |
| Average method complexity | 4.41 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 94.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 12 | |
| Interfaces | 4 | |
| Traits | 0 | |
| Classes | 68 | |
| ▷ Abstract classes | 2 | 2.94% |
| ▷ Concrete classes | 66 | 97.06% |
| ▷ Final classes | 2 | 3.03% |
| Methods | 1,370 | |
| ▷ Static methods | 216 | 15.77% |
| ▷ Public methods | 978 | 71.39% |
| ▷ Protected methods | 18 | 1.31% |
| ▷ Private methods | 374 | 27.30% |
| Functions | 109 | |
| ▷ Named functions | 100 | 91.74% |
| ▷ Anonymous functions | 9 | 8.26% |
| Constants | 145 | |
| ▷ Global constants | 98 | 67.59% |
| ▷ Class constants | 47 | 32.41% |
| ▷ Public constants | 47 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
3 PNG files occupy 0.03MB with 0.01MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| freemius/assets/img/plugin-icon.png | 9.16KB | 5.26KB | ▼ 42.58% |
| freemius/assets/img/theme-icon.png | 10.97KB | 5.78KB | ▼ 47.37% |
| freemius/assets/img/wp-tools-divi-product-carousel.png | 10.93KB | 4.63KB | ▼ 57.58% |