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
Install script ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼1.17ms] Passed 4 tests
Analyzing server-side resources used by Blipstar Store Locator
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 40.89 ▲1.01 |
Dashboard /wp-admin | 3.32 ▲0.02 | 48.02 ▼1.49 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 46.39 ▼1.42 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 90.26 ▼2.78 |
Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 37.28 ▲1.39 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 4 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
widget_recent-posts |
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
Blipstar Store Locator: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,810 ▲53 | 14.84 ▲0.43 | 1.77 ▼0.35 | 38.15 ▼7.54 |
Dashboard /wp-admin | 2,216 ▲28 | 4.84 ▼0.07 | 120.17 ▲12.94 | 42.39 ▲2.84 |
Posts /wp-admin/edit.php | 2,098 ▲9 | 2.00 ▼0.04 | 39.10 ▼2.74 | 35.56 ▲1.43 |
Add New Post /wp-admin/post-new.php | 1,544 ▲30 | 23.49 ▲5.78 | 667.52 ▼9.25 | 50.82 ▼3.04 |
Media Library /wp-admin/upload.php | 1,398 ▲13 | 4.25 ▼0.07 | 104.26 ▲3.72 | 46.90 ▲4.29 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/blipstar-store-locator/blipstar_store_locator.php:94
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 93% 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 your attention:
- Screenshots: These screenshots do not have images: #1 (Example of the shortcode used to embed your store locator in a page or post), #2 (Example store locator embedded in page)
blipstar-store-locator/blipstar_store_locator.php 92% from 13 tests
The principal PHP file in "Blipstar Store Locator" v. 1.3 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("blipstar-store-locator.php" instead of "blipstar_store_locator.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Good job! No executable or dangerous file extensions detected98 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 24 | 11 | 98 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
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 | 4 | |
▷ Named functions | 4 | 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 compressed PNG file occupies 0.01MB
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 11.94KB | 12.20KB | 0.00% |