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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼3.95ms] Passed 4 tests
Analyzing server-side resources used by Portfolio Widgets for Elementor
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 43.42 ▲1.95 |
Dashboard /wp-admin | 3.32 ▼0.02 | 50.59 ▼8.91 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 49.05 ▼1.50 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 90.30 ▼7.34 |
Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 41.60 ▲3.87 |
Server storage [IO: ▲0.25MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 16 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
can_compress_scripts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Portfolio Widgets for Elementor
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,832 ▲46 | 13.58 ▼0.79 | 1.93 ▼0.09 | 44.60 ▲2.00 |
Dashboard /wp-admin | 2,241 ▲35 | 4.82 ▼0.05 | 101.98 ▼5.50 | 36.26 ▼1.21 |
Posts /wp-admin/edit.php | 2,117 ▲14 | 2.02 ▲0.03 | 38.77 ▲1.01 | 37.32 ▲3.04 |
Add New Post /wp-admin/post-new.php | 1,561 ▲30 | 21.14 ▼1.99 | 673.34 ▲42.80 | 60.88 ▲5.21 |
Media Library /wp-admin/upload.php | 1,417 ▲17 | 4.26 ▲0.05 | 114.27 ▲6.77 | 47.96 ▲1.40 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
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
Please take a closer look at the following
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_url() in wp-content/plugins/portfolio-widgets-for-elementor/widgets/partials/style-only_image.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_url() in wp-content/plugins/portfolio-widgets-for-elementor/widgets/partials/style-with_title_bottom.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function ElementorPortfolio\\add_action() in wp-content/plugins/portfolio-widgets-for-elementor/plugin.php:182
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
5 plugin tags: page builder, grid, elementor, carousel, portfolio
portfolio-widgets-for-elementor/elementor-portfolio.php 85% from 13 tests
Analyzing the main PHP file in "Portfolio Widgets for Elementor" version 1.0.0
It is important to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("portfolio-widgets-for-elementor.php" instead of "elementor-portfolio.php")
- 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 review of files and their extensions; it is not recommended to include executable files
No dangerous file extensions were detected6,682 lines of code in 14 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JSON | 2 | 0 | 0 | 3,974 |
JavaScript | 3 | 545 | 859 | 2,219 |
PHP | 7 | 128 | 240 | 379 |
Sass | 1 | 16 | 0 | 109 |
CSS | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.22 |
Average class complexity | 5.67 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 8.00 |
Average method complexity | 1.58 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 5.00 |
Code structure | ||
---|---|---|
Namespaces | 2 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 3 | 100.00% |
▷ Final classes | 1 | 33.33% |
Methods | 24 | |
▷ Static methods | 1 | 4.17% |
▷ Public methods | 19 | 79.17% |
▷ Protected methods | 4 | 16.67% |
▷ Private methods | 1 | 4.17% |
Functions | 2 | |
▷ Named functions | 2 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 3 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 3 | 100.00% |
▷ Public constants | 3 | 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
There are no PNG files in this plugin