Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.34MB] [CPU: ▼299.37ms] Passed 4 tests
An overview of server-side resources used by Extended Buttons for Elementor
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.54 ▲0.03 | 55.30 ▲7.02 |
Dashboard /wp-admin | 3.28 ▼0.13 | 23.54 ▼8.68 |
Posts /wp-admin/edit.php | 3.34 ▼0.30 | 27.06 ▼11.49 |
Add New Post /wp-admin/post-new.php | 6.08 ▼0.91 | 78.78 ▼1,174.83 |
Media Library /wp-admin/upload.php | 3.29 ▼0.01 | 20.74 ▼2.48 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 12 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Checking browser requirements for Extended Buttons for Elementor
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,795 ▲40 | 15.84 ▲0.21 | 7.05 ▲0.61 | 2.99 ▲0.74 |
Dashboard /wp-admin | 2,895 ▲37 | 6.12 ▼0.09 | 117.04 ▼24.81 | 154.36 ▼21.10 |
Posts /wp-admin/edit.php | 2,691 ▼3 | 3.24 ▲0.01 | 63.53 ▼1.14 | 136.41 ▼10.36 |
Add New Post /wp-admin/post-new.php | 1,661 ▼91 | 16.19 ▼5.51 | 415.52 ▼37.39 | 157.57 ▲0.58 |
Media Library /wp-admin/upload.php | 1,701 ▲3 | 5.54 ▲0.01 | 143.26 ▲5.38 | 185.97 ▼3.12 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
This plugin's uninstaller ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Everything seems fine, however 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
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function Elementor\\add_action() in wp-content/plugins/extended-buttons-for-elementor/elementor-helper.php:4
- > 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 86% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Please fix the following attributes:
- Screenshots: Please add descriptions for these screenshots #1, #2, #3, #4, #5 in extended-buttons-for-elementor/assets to your readme.txt
extended-buttons-for-elementor/elementor-button-extended.php 77% from 13 tests
Analyzing the main PHP file in "Extended Buttons for Elementor" version 1.0.2
It is important to fix the following:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Main file name: It is recommended to name the main PHP file as the plugin slug ("extended-buttons-for-elementor.php" instead of "elementor-button-extended.php")
- Description: The description should be shorter than 140 characters (currently 265 characters long)
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
Good job! No executable or dangerous file extensions detected1,672 lines of code in 8 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 152 | 105 | 1,044 |
CSS | 3 | 36 | 17 | 615 |
JavaScript | 1 | 1 | 1 | 13 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.15 |
Average class complexity | 24.00 |
▷ Minimum class complexity | 24.00 |
▷ Maximum class complexity | 24.00 |
Average method complexity | 2.92 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 22.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 12 | |
▷ Static methods | 2 | 16.67% |
▷ Public methods | 7 | 58.33% |
▷ Protected methods | 5 | 41.67% |
▷ Private methods | 0 | 0.00% |
Functions | 8 | |
▷ Named functions | 4 | 50.00% |
▷ Anonymous functions | 4 | 50.00% |
Constants | 2 | |
▷ Global constants | 2 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/eb-button-icon.png | 1.36KB | 0.70KB | ▼ 48.35% |