Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼2.82ms] Passed 4 tests
An overview of server-side resources used by Browsee
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 43.97 ▼6.20 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 53.90 ▼0.14 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 52.74 ▲1.26 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 103.28 ▲10.40 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.15 ▼6.18 |
| Browsee /wp-admin/options-general.php?page=browsee_settings | 3.25 | 34.34 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 7 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| browsee_version |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
| db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for Browsee
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,806 ▲17 | 13.38 ▼0.93 | 1.72 ▼0.40 | 44.08 ▼0.45 |
| Dashboard /wp-admin | 2,212 ▲6 | 5.85 ▲1.01 | 114.44 ▲2.45 | 45.88 ▲3.10 |
| Posts /wp-admin/edit.php | 2,095 ▲3 | 2.04 ▼0.02 | 40.72 ▲1.03 | 34.87 ▲0.44 |
| Add New Post /wp-admin/post-new.php | 1,535 ▼1 | 23.13 ▲0.16 | 662.76 ▼7.15 | 66.27 ▲12.43 |
| Media Library /wp-admin/upload.php | 1,397 ▲9 | 4.18 ▲0.01 | 96.91 ▼20.90 | 41.42 ▼5.25 |
| Browsee /wp-admin/options-general.php?page=browsee_settings | 823 | 2.02 | 24.66 | 21.23 |
Uninstaller [IO: ✅] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- Zombie WordPress options were found after uninstall: 7 options
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- browsee_version
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
SRP Passed 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
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 97% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that need to be fixed:
- Tags: There are too many tags (11 tag instead of maximum 10)
browsee/browsee.php Passed 13 tests
The main file in "Browsee" v. 1.0.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
115 characters long description:
Browsee helps you understand your users better using session recordings, heatmaps, simulations and session tagging.
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 plugin173 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 51 | 47 | 159 |
| CSS | 1 | 2 | 0 | 14 |
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.20 |
| Average class complexity | 3.50 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 4.00 |
| Average method complexity | 1.29 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 3.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 17 | |
| ▷ Static methods | 4 | 23.53% |
| ▷ Public methods | 12 | 70.59% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 29.41% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 1 | 100.00% |
| ▷ Public constants | 1 | 100.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.02MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| admin/static/browsee_logo_2x.png | 18.09KB | 9.27KB | ▼ 48.73% |