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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.20ms] Passed 4 tests
Server-side resources used by Header scroll event for Elementor
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 40.30 ▼4.38 |
Dashboard /wp-admin | 3.31 ▲0.01 | 46.68 ▼4.32 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.32 ▼3.28 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 82.12 ▼8.83 |
Media Library /wp-admin/upload.php | 3.24 ▲0.00 | 36.24 ▲0.59 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
widget_recent-comments |
db_upgraded |
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Header scroll event for Elementor
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.27 ▼1.31 | 1.84 ▼0.07 | 43.76 ▲1.16 |
Dashboard /wp-admin | 2,206 ▲21 | 5.90 ▲1.04 | 117.01 ▲3.64 | 43.83 ▲0.55 |
Posts /wp-admin/edit.php | 2,086 ▼0 | 2.05 ▲0.05 | 33.60 ▼3.27 | 30.99 ▼2.35 |
Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 23.08 ▲0.00 | 577.70 ▼103.12 | 51.25 ▼8.14 |
Media Library /wp-admin/upload.php | 1,391 ▲3 | 4.17 ▼0.05 | 95.66 ▼6.18 | 44.35 ▼1.72 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 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
Almost there! Just fix the following items
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/header-scroll-event-for-elementor/miga_scroll_header.php:25
- > PHP Fatal error
Uncaught Error: Class 'Elementor\\Widget_Base' not found in wp-content/plugins/header-scroll-event-for-elementor/widgets/HeaderScrollEvent.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
9 plugin tags: swiper, elementor, elements, category, slider...
header-scroll-event-for-elementor/miga_scroll_header.php 77% from 13 tests
This is the main PHP file of "Header scroll event for Elementor" version 1.0.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
You should first fix the following items:
- Requires at least: Required version must match the one declared in readme.txt ("5.0" instead of "5.2")
- Main file name: It is recommended to name the main PHP file as the plugin slug ("header-scroll-event-for-elementor.php" instead of "miga_scroll_header.php")
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected110 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 15 | 20 | 97 |
JavaScript | 1 | 3 | 0 | 13 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.10 |
Average class complexity | 2.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 2.00 |
Average method complexity | 1.12 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 2.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 8 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 6 | 75.00% |
▷ Protected methods | 2 | 25.00% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 1 | 100.00% |
Constants | 0 | |
▷ Global constants | 0 | 0.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
There were not PNG files found in your plugin