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.03MB] [CPU: ▼3.38ms] Passed 4 tests
This is a short check of server-side resources used by BugFu Console Debugger
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 49.13 ▲1.82 |
| Dashboard /wp-admin | 3.33 ▲0.03 | 53.41 ▼5.94 |
| Posts /wp-admin/edit.php | 3.44 ▲0.09 | 45.85 ▼4.41 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 107.09 ▼4.52 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 40.24 ▲1.37 |
| BugFu /wp-admin/tools.php?page=bugfu-console-debugger | 3.26 | 36.11 |
Server storage [IO: ▲0.43MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 9 new files
Database: no new tables, 9 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| bugfu_plugin_version |
| bugfu_debug_log |
| bugfu_debug_status |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for BugFu Console Debugger
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,911 ▲150 | 13.53 ▼0.76 | 13.82 ▲12.05 | 49.86 ▲6.11 |
| Dashboard /wp-admin | 2,219 ▲39 | 5.70 ▲0.05 | 97.90 ▼19.13 | 39.66 ▼7.79 |
| Posts /wp-admin/edit.php | 2,121 ▲24 | 2.04 ▲0.05 | 44.06 ▲4.59 | 37.59 ▼0.04 |
| Add New Post /wp-admin/post-new.php | 1,539 ▲8 | 23.63 ▲0.52 | 673.83 ▼76.67 | 52.01 ▼17.02 |
| Media Library /wp-admin/upload.php | 1,421 ▲21 | 4.26 ▲0.04 | 112.23 ▼20.35 | 53.39 ▼13.67 |
| BugFu /wp-admin/tools.php?page=bugfu-console-debugger | 946 | 2.05 | 34.35 | 56.08 |
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
Please fix the following items
- Zombie WordPress options detected upon uninstall: 9 options
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- bugfu_plugin_version
- widget_recent-posts
- bugfu_debug_log
- bugfu_debug_status
- can_compress_scripts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Good news, no errors were detected
SRP 50% from 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
Please take a closer look at the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Cannot access self:: when no class scope is active in wp-content/plugins/bugfu-console-debugger/views/settings-page.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 97% 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 add images for these screenshots: #1 (The admin page when BugFu is ON), #2 (The Browser JavaScript Console when BugFu is ON), #3 (The admin page when BugFu is OFF)
bugfu-console-debugger/bugfu-console-debugger.php Passed 13 tests
The main file in "BugFu Console Debugger" v. 1.3.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
91 characters long description:
Log/Debug the PHP code in your Theme/Plugin with your Browser Console *no extension needed*
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Success! There were no dangerous files found in this plugin332 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 96 | 23 | 227 |
| CSS | 1 | 11 | 0 | 67 |
| JavaScript | 1 | 17 | 0 | 38 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.23 |
| Average class complexity | 17.00 |
| ▷ Minimum class complexity | 17.00 |
| ▷ Maximum class complexity | 17.00 |
| Average method complexity | 1.89 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 8.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 | 18 | |
| ▷ Static methods | 4 | 22.22% |
| ▷ Public methods | 11 | 61.11% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 7 | 38.89% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 10 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 10 | 100.00% |
| ▷ Public constants | 10 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
No PNG images were found in this plugin