Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.15MB] [CPU: ▼2.23ms] Passed 4 tests
A check of server-side resources used by WP Map Builder/Styler
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.61 ▲0.15 | 38.23 ▼5.18 |
Dashboard /wp-admin | 3.45 ▲0.14 | 46.00 ▼3.44 |
Posts /wp-admin/edit.php | 3.56 ▲0.20 | 47.30 ▼4.34 |
Add New Post /wp-admin/post-new.php | 6.05 ▲0.16 | 94.23 ▲6.35 |
Media Library /wp-admin/upload.php | 3.37 ▲0.14 | 36.93 ▲4.05 |
WP Map Builder /wp-admin/admin.php?page=wbm_map_init_page | 3.34 | 29.97 |
Map List /wp-admin/admin.php?page=wbm_map_list_page | 3.34 | 34.09 |
Create New Map /wp-admin/admin.php?page=wbm_create_new_map | 3.34 | 31.37 |
Server storage [IO: ▲2.25MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 85 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_wmb_map_builder |
New WordPress options |
---|
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
widget_theysaidso_widget |
db_upgraded |
Browser metrics Passed 4 tests
WP Map Builder/Styler: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,955 ▲220 | 14.66 ▲0.08 | 24.76 ▲22.78 | 40.24 ▼7.36 |
Dashboard /wp-admin | 2,236 ▲48 | 5.47 ▲0.60 | 101.44 ▼15.53 | 80.66 ▲38.48 |
Posts /wp-admin/edit.php | 2,128 ▲36 | 2.52 ▲0.51 | 39.14 ▼5.84 | 34.27 ▼3.94 |
Add New Post /wp-admin/post-new.php | 1,551 ▲37 | 23.19 ▲5.49 | 751.62 ▲50.12 | 35.53 ▼32.92 |
Media Library /wp-admin/upload.php | 1,424 ▲39 | 4.53 ▲0.31 | 100.35 ▼0.22 | 73.91 ▲31.43 |
WP Map Builder /wp-admin/admin.php?page=wbm_map_init_page | 908 | 1.89 | 29.80 | 32.09 |
Map List /wp-admin/admin.php?page=wbm_map_list_page | 971 | 2.45 | 40.12 | 29.68 |
Create New Map /wp-admin/admin.php?page=wbm_create_new_map | 1,337 | 2.88 | 38.87 | 71.13 |
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
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 25% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 2× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/wp-map-builderstyler/admin/partials/wp-map-builder-admin-display.php
- > /wp-content/plugins/wp-map-builderstyler/public/partials/wp-map-builder-public-display.php
- 4× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'Wp_Map_Builder_Admin' not found in wp-content/plugins/wp-map-builderstyler/admin/class-wp-map-listing.php:16
- > PHP Fatal error
Uncaught Error: Class 'Wp_Map_Builder_Admin' not found in wp-content/plugins/wp-map-builderstyler/admin/class-wp-map-builder-init-page.php:16
- > PHP Fatal error
Uncaught Error: Class 'Wp_Map_Builder_Admin' not found in wp-content/plugins/wp-map-builderstyler/admin/class-wp-map-builder-create-map.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/wp-map-builderstyler/public/class-wp-map-builder-shortcode.php:45
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Please fix the following user-side errors
- > GET request to /wp-admin/admin.php?page=wbm_map_list_page
- > Network (severe)
wp-content/plugins/wp-map-builderstyler/admin/images/sort_both.png - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/admin.php?page=wbm_map_list_page
- > Network (severe)
wp-content/plugins/wp-map-builderstyler/admin/images/sort_asc.png - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/admin.php?page=wbm_create_new_map
- > Javascript (severe) in unknown
https://maps.googleapis.com/maps/api/js?key=&libraries=places&callback=myMap 152:473 Uncaught fca: Map: Expected mapDiv of type HTMLElement but was passed null.
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that require attention:
- Screenshots: These screenshots lack descriptions #1, #2, #3, #4 in wp-map-builderstyler/assets to your readme.txt
- Contributors: Plugin contributors not specified
wp-map-builderstyler/wp-map-builder.php 77% from 13 tests
The main file in "WP Map Builder/Styler" v. 1.2.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 146 characters long)
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("wp-map-builderstyler.php" instead of "wp-map-builder.php")
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
There were no executable files found in this plugin5,303 lines of code in 48 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 29 | 18 | 18 | 4,434 |
PHP | 16 | 152 | 573 | 807 |
CSS | 3 | 3 | 8 | 62 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.17 |
Average class complexity | 6.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 42.00 |
Average method complexity | 2.72 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 42.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 11 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 11 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 32 | |
▷ Static methods | 2 | 6.25% |
▷ Public methods | 27 | 84.38% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 15.62% |
Functions | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
31 PNG files occupy 2.00MB with 0.50MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
admin/images/public/17.png | 83.94KB | 82.30KB | ▼ 1.95% |
admin/images/public/11.png | 35.78KB | 20.42KB | ▼ 42.93% |
admin/images/public/8.png | 20.56KB | 11.63KB | ▼ 43.43% |
admin/images/public/19.png | 27.75KB | 25.49KB | ▼ 8.14% |
admin/images/public/20.png | 75.87KB | 53.96KB | ▼ 28.88% |