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.30MB] [CPU: ▼11.69ms] Passed 4 tests
This is a short check of server-side resources used by Flaming Browser Support
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.05 ▲0.31 | 46.70 ▲1.30 |
| Dashboard /wp-admin | 3.92 ▲0.29 | 53.53 ▼14.56 |
| Posts /wp-admin/edit.php | 3.96 ▲0.28 | 48.34 ▼5.48 |
| Add New Post /wp-admin/post-new.php | 6.55 ▲0.40 | 78.53 ▼26.97 |
| Media Library /wp-admin/upload.php | 3.80 ▲0.31 | 39.38 ▲0.24 |
Server storage [IO: ▲5.92MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 340 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
| can_compress_scripts |
| FlamingBrowserSupportSettings |
Browser metrics Passed 4 tests
A check of browser resources used by Flaming Browser Support
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,805 ▲44 | 14.75 ▲0.37 | 2.10 ▲0.14 | 40.90 ▼3.94 |
| Dashboard /wp-admin | 2,211 ▲31 | 5.66 ▼0.05 | 82.84 ▼9.41 | 38.63 ▼2.61 |
| Posts /wp-admin/edit.php | 2,116 ▲16 | 2.03 ▲0.02 | 36.34 ▼6.29 | 33.04 ▼4.90 |
| Add New Post /wp-admin/post-new.php | 1,539 ▲8 | 17.39 ▼5.88 | 692.63 ▼8.76 | 54.92 ▼11.16 |
| Media Library /wp-admin/upload.php | 1,416 ▲22 | 4.17 ▼0.06 | 104.15 ▼4.32 | 44.77 ▼1.24 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 0% 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 take a closer look at the following
- 5× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/flaming-browser-support/views/messages.php
- > /wp-content/plugins/flaming-browser-support/views/unsupported.php
- > /wp-content/plugins/flaming-browser-support/views/defaults/unsupported_mobile.php
- > /wp-content/plugins/flaming-browser-support/views/defaults/unsupported_tablet.php
- > /wp-content/plugins/flaming-browser-support/views/defaults/unsupported_browser.php
- 22× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Warning
Use of undefined constant FLAMING_BROWSER_SUPPORT_VERSION - assumed 'FLAMING_BROWSER_SUPPORT_VERSION' (this will throw an Error in a future version of PHP) in wp-content/plugins/flaming-browser-support/views/settings.php on line 9
- > PHP Notice
Trying to get property 'CSS' of non-object in wp-content/plugins/flaming-browser-support/views/unsupported.php on line 19
- > PHP Notice
Undefined variable: Settings in wp-content/plugins/flaming-browser-support/views/settings.php on line 57
- > PHP Notice
Trying to get property 'BlockTablets' of non-object in wp-content/plugins/flaming-browser-support/views/settings.php on line 39
- > PHP Notice
Trying to get property 'BlockTabletsRedirect' of non-object in wp-content/plugins/flaming-browser-support/views/settings.php on line 40
- > PHP Notice
Trying to get property 'BlockUnsupportedBrowsers' of non-object in wp-content/plugins/flaming-browser-support/views/settings.php on line 48
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/flaming-browser-support/flaming-browser-support.php:23
- > PHP Notice
Trying to get property 'BlockMobileRedirect' of non-object in wp-content/plugins/flaming-browser-support/views/settings.php on line 31
- > PHP Notice
Undefined variable: Settings in wp-content/plugins/flaming-browser-support/views/settings.php on line 49
- > PHP Notice
Trying to get property 'BlockMobile' of non-object in wp-content/plugins/flaming-browser-support/views/settings.php on line 30
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that need to be fixed:
- Plugin Name: Please specify the plugin name on the first line (
=== flaming-browser-support ===)
flaming-browser-support/flaming-browser-support.php Passed 13 tests
The entry point to "Flaming Browser Support" version 1.0.2 is a PHP file that has certain tags in its header comment area
105 characters long description:
Checks the users browser to see if it is supported, and displays a message if the browser is unsupported.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
There were no executable files found in this plugin2,046 lines of code in 336 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 11 | 160 | 430 | 1,469 |
| JavaScript | 323 | 27 | 12 | 425 |
| CSS | 2 | 28 | 0 | 152 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.42 |
| Average class complexity | 57.50 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 163.00 |
| Average method complexity | 3.79 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 32.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 81 | |
| ▷ Static methods | 6 | 7.41% |
| ▷ Public methods | 37 | 45.68% |
| ▷ Protected methods | 44 | 54.32% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 60 | |
| ▷ Global constants | 4 | 6.67% |
| ▷ Class constants | 56 | 93.33% |
| ▷ Public constants | 56 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.03MB with 0.02MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| resources/images/FlamingLogoReverse.png | 18.38KB | 5.16KB | ▼ 71.95% |
| resources/images/FlamingLogo.png | 17.23KB | 8.92KB | ▼ 48.22% |