Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼10.28ms] Passed 4 tests
Analyzing server-side resources used by WP Browser Compatibility Checker
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.41 ▼0.05 | 24.19 ▼16.31 |
| Dashboard /wp-admin | 3.34 ▼0.00 | 43.06 ▼15.97 |
| Posts /wp-admin/edit.php | 3.39 ▲0.04 | 47.69 ▼2.02 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.04 | 92.94 ▼3.69 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.04 | 33.90 ▼5.16 |
| Browser Warning /wp-admin/themes.php?page=browser_warning | 3.20 | 30.68 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 8 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-comments |
| db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for WP Browser Compatibility Checker
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,917 ▲171 | 13.63 ▼0.60 | 9.04 ▲7.23 | 38.51 ▼4.79 |
| Dashboard /wp-admin | 2,210 ▲22 | 5.86 ▼0.05 | 105.70 ▲2.55 | 45.66 ▲3.56 |
| Posts /wp-admin/edit.php | 2,096 ▲7 | 2.05 ▲0.03 | 41.91 ▲0.59 | 36.25 ▲1.92 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲8 | 23.25 ▲0.02 | 753.04 ▲79.10 | 58.88 ▲3.21 |
| Media Library /wp-admin/upload.php | 1,386 ▼5 | 4.21 ▲0.08 | 103.71 ▼2.93 | 46.16 ▼0.83 |
| Browser Warning /wp-admin/themes.php?page=browser_warning | 871 | 2.03 | 25.32 | 29.17 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Almost there, just fix the following server-side errors
- > GET request to /wp-admin/themes.php?page=browser_warning
- > User deprecated in wp-includes/functions.php+5463
Function screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/themes.php?page=browser_warning
- > User deprecated in wp-includes/functions.php+5463
Function get_screen_icon is deprecated since version 3.8.0 with no alternative available.
- 6 occurences, only the last one shown
- > GET request to /wp-admin/themes.php?page=browser_warning
- > Notice in wp-content/plugins/browser-compatibility-warning/include/options.php+57
Trying to access array offset on value of type bool
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
Please fix the following items
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/browser-compatibility-warning/include/options.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/browser-compatibility-warning/include/options.php:2
- > 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
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
3 plugin tags: compatibility, browser, checker
browser-compatibility-warning/index.php 85% from 13 tests
The primary PHP file in "WP Browser Compatibility Checker" version 1.05 is used by WordPress to initiate all plugin functionality
Please make the necessary changes and fix the following:
- Description: The description should be shorter than 140 characters (currently 175 characters long)
- Main file name: Name the main plugin file the same as the plugin slug ("browser-compatibility-warning.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Success! There were no dangerous files found in this plugin379 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 3 | 29 | 30 | 185 |
| PHP | 2 | 2 | 9 | 158 |
| CSS | 1 | 0 | 0 | 36 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.20 |
| 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 | 7 | |
| ▷ Named functions | 7 | 100.00% |
| ▷ Anonymous functions | 0 | 0.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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
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 |
| img/warning.png | 4.32KB | 1.79KB | ▼ 58.48% |