Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼0.63ms] Passed 4 tests
Analyzing server-side resources used by Leverage Browser Caching
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 35.15 ▼7.79 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 48.09 ▲2.51 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 44.29 ▼3.57 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 93.42 ▲8.18 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 37.37 ▲6.33 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] 67% from 3 tests
A short overview of filesystem and database impact
Please try to fix the following items
- Illegal file modification detected: 1 file (1.24KB) outside of "wp-content/plugins/leverage-browser-caching/" and "wp-content/uploads/"
- (modified) .htaccess
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
Browser metrics Passed 4 tests
Leverage Browser Caching: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲11 | 14.48 ▲1.09 | 1.71 ▲0.03 | 40.27 ▼5.95 |
| Dashboard /wp-admin | 2,203 ▼3 | 5.81 ▲0.93 | 95.55 ▼13.43 | 39.12 ▲1.08 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.18 ▲0.17 | 40.23 ▲0.36 | 35.64 ▼0.77 |
| Add New Post /wp-admin/post-new.php | 1,546 ▲32 | 18.49 ▲0.96 | 659.32 ▼4.95 | 56.92 ▲2.35 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.20 ▲0.00 | 108.34 ▲7.30 | 45.70 ▼0.31 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP Passed 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
Looking good! No server-side errors or output on direct access of PHP files
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
3 plugin tags: caching, leverage, browser
leverage-browser-caching/leverage-browser-caching.php 85% from 13 tests
The main PHP script in "Leverage Browser Caching" version 2.3 is automatically included on every request by WordPress
You should first fix the following items:
- Domain Path: The domain path folder does not exist ("/languages")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Everything looks great! No dangerous files found in this plugin118 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 41 | 97 | 118 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.26 |
| Average class complexity | 11.00 |
| ▷ Minimum class complexity | 11.00 |
| ▷ Maximum class complexity | 11.00 |
| Average method complexity | 2.67 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 6.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 | 6 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 6 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.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 were not PNG files found in your plugin