Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.09MB] [CPU: ▼7.30ms] Passed 4 tests
A check of server-side resources used by b-Locator
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.05 | 30.75 ▼11.48 |
| Dashboard /wp-admin | 3.45 ▲0.15 | 54.14 ▲4.09 |
| Posts /wp-admin/edit.php | 3.51 ▲0.15 | 55.47 ▲4.05 |
| Add New Post /wp-admin/post-new.php | 5.97 ▲0.08 | 84.01 ▼21.25 |
| Media Library /wp-admin/upload.php | 3.29 ▲0.07 | 36.38 ▼0.52 |
| Categories /wp-admin/edit-tags.php?taxonomy=location-categories&post_type=b-locator | 3.32 | 38.64 |
| Add New /wp-admin/post-new.php?post_type=b-locator | 3.44 | 48.75 |
| All Location /wp-admin/edit.php?post_type=b-locator | 3.36 | 42.98 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 21 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
| b_locator |
| can_compress_scripts |
Browser metrics Passed 4 tests
b-Locator: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,455 ▲705 | 17.86 ▲3.49 | 40.21 ▲38.37 | 42.19 ▼3.38 |
| Dashboard /wp-admin | 2,396 ▲198 | 6.41 ▲0.40 | 121.86 ▲14.60 | 39.68 ▼2.27 |
| Posts /wp-admin/edit.php | 2,292 ▲189 | 3.31 ▲1.28 | 46.19 ▲5.40 | 32.39 ▼12.69 |
| Add New Post /wp-admin/post-new.php | 1,558 ▲10 | 23.23 ▼0.08 | 633.39 ▲20.43 | 44.43 ▼16.67 |
| Media Library /wp-admin/upload.php | 1,435 ▲35 | 4.15 ▼0.07 | 89.19 ▼22.52 | 49.35 ▼2.43 |
| Categories /wp-admin/edit-tags.php?taxonomy=location-categories&post_type=b-locator | 1,469 | 3.12 | 40.25 | 31.65 |
| Add New /wp-admin/post-new.php?post_type=b-locator | 2,329 | 7.73 | 175.00 | 66.44 |
| All Location /wp-admin/edit.php?post_type=b-locator | 1,273 | 3.29 | 44.15 | 28.59 |
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
These items require your attention
- The uninstall procedure has failed, leaving 7 options in the database
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
- b_locator
- widget_recent-posts
Smoke tests 50% 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)
Even though everything seems fine, this is not 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 fix the following
- 4× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/b-locator/backend/partials/noticeForAPIKey.php
- > /wp-content/plugins/b-locator/backend/partials/instruction.php
- > /wp-content/plugins/b-locator/backend/partials/updateNotice.php
- > /wp-content/plugins/b-locator/frontend/partials/map.php
- 9× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function do_settings_sections() in wp-content/plugins/b-locator/backend/partials/form.php:4
- > PHP Notice
Undefined variable: search in wp-content/plugins/b-locator/frontend/partials/locationList.php on line 12
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_reset_postdata() in wp-content/plugins/b-locator/frontend/partials/locationList.php:23
- > PHP Notice
Undefined variable: categories in wp-content/plugins/b-locator/frontend/partials/locationList.php on line 3
- > PHP Notice
Undefined variable: locations in wp-content/plugins/b-locator/frontend/partials/locationList.php on line 1
- > PHP Notice
Undefined variable: search in wp-content/plugins/b-locator/frontend/partials/locationList.php on line 1
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/b-locator/backend/partials/metaboxContent.php:4
- > PHP Notice
Undefined variable: categories in wp-content/plugins/b-locator/frontend/partials/locationList.php on line 1
- > PHP Notice
Undefined variable: map_height in wp-content/plugins/b-locator/frontend/partials/map.php on line 3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Please fix the following attributes:
- Requires at least: The plugin version is formatted incorrectly
b-locator/BLocator.php 92% from 13 tests
The main file in "b-Locator" v. 1.0.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("b-locator.php" instead of "BLocator.php")
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
Good job! No executable or dangerous file extensions detected965 lines of code in 18 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 14 | 102 | 240 | 719 |
| JavaScript | 2 | 32 | 19 | 162 |
| CSS | 2 | 1 | 0 | 84 |
PHP code Passed 2 tests
An short overview of 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.50 |
| Average class complexity | 8.86 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 26.00 |
| Average method complexity | 2.20 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 15.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 7 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 7 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 46 | |
| ▷ Static methods | 1 | 2.17% |
| ▷ Public methods | 43 | 93.48% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 3 | 6.52% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 PNG file occupies 0.05MB with 0.05MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| backend/imgs/buy-me-a-coffee.png | 51.76KB | 5.03KB | ▼ 90.29% |