Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼8.45ms] Passed 4 tests
This is a short check of server-side resources used by Core Web Vitals Booster
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 40.74 ▼1.61 |
Dashboard /wp-admin | 3.32 ▲0.02 | 48.69 ▼16.40 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 43.81 ▼4.83 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 83.17 ▼10.95 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 32.96 ▲3.02 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] 67% from 3 tests
Analyzing filesystem and database footprints of this plugin
Please fix the following
- There were 1 file (0.00KB) illegally modified outside of "wp-content/plugins/speedien/" and "wp-content/uploads/"
- (new file) wp-content/advanced-cache.php
Filesystem: 5 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_recent-posts |
db_upgraded |
can_compress_scripts |
theysaidso_admin_options |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Core Web Vitals Booster
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,816 ▲70 | 13.73 ▼0.68 | 1.82 ▼0.38 | 45.31 ▼0.92 |
Dashboard /wp-admin | 2,225 ▲34 | 5.84 ▲0.95 | 97.39 ▼4.10 | 38.76 ▼2.35 |
Posts /wp-admin/edit.php | 2,105 ▲13 | 1.99 ▼0.09 | 38.33 ▼1.50 | 32.73 ▼4.20 |
Add New Post /wp-admin/post-new.php | 1,556 ▲37 | 18.73 ▼4.50 | 604.32 ▲4.88 | 52.74 ▼1.54 |
Media Library /wp-admin/upload.php | 1,404 ▲13 | 4.30 ▲0.11 | 92.03 ▼8.55 | 41.48 ▼1.24 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- This plugin cannot be uninstalled
- > Notice in wp-content/plugins/speedien/speedien.php+30
Undefined variable: wp_config_file
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
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
Even though no errors were found, this is by no means an exhaustive test
SRP 50% 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 items
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/speedien/speedien_cache.php:203
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/speedien/speedien_ui.php:90
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need to be fixed:
- Screenshots: Please a description for screenshot #3 in speedien/assets to your readme.txt
speedien/speedien.php 85% from 13 tests
The main file in "Core Web Vitals Booster" v. 1.1.7 serves as a complement to information provided in readme.txt and as the entry point to the plugin
It is important to fix the following:
- Domain Path: Prefix the domain path with a forward slash character ("//")
- Domain Path: The domain path follows the same naming rules as the domain name, using only dashes and lowercase characters ("/")
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 detected464 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 90 | 57 | 464 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.39 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 20 | |
▷ Named functions | 18 | 90.00% |
▷ Anonymous functions | 2 | 10.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There are no PNG files in this plugin