Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.92MB] [CPU: ▼32.32ms] Passed 4 tests
This is a short check of server-side resources used by WP Leaflet Mapper
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.04 | 40.26 ▲1.66 |
| Dashboard /wp-admin | 3.02 ▼0.28 | 22.71 ▼24.06 |
| Posts /wp-admin/edit.php | 3.02 ▼0.33 | 23.62 ▼22.70 |
| Add New Post /wp-admin/post-new.php | 3.02 ▼2.86 | 23.56 ▼74.49 |
| Media Library /wp-admin/upload.php | 3.02 ▼0.20 | 24.74 ▼8.04 |
| Leaflet-Mapper /wp-admin/options-general.php?page=wp-leaflet-mapper/wp-leaflet-mapper.php | 3.03 | 23.36 |
Server storage [IO: ▲0.02MB] [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_theysaidso_widget |
| can_compress_scripts |
| Leaflet_Mapper_Option |
| theysaidso_admin_options |
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by WP Leaflet Mapper
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,814 ▲79 | 14.67 ▲0.30 | 4.83 ▲2.91 | 42.39 ▼3.07 |
| Dashboard /wp-admin | 2,209 ▲20 | 5.95 ▲0.03 | 99.39 ▼5.60 | 41.91 ▼1.70 |
| Posts /wp-admin/edit.php | 2,101 ▲12 | 2.77 ▲0.71 | 37.31 ▲2.49 | 31.54 ▼1.28 |
| Add New Post /wp-admin/post-new.php | 6,463 ▲4,934 | 23.87 ▲5.48 | 836.73 ▲242.43 | 38.98 ▼27.65 |
| Media Library /wp-admin/upload.php | 1,394 ▲6 | 5.14 ▲0.93 | 100.23 ▲1.50 | 43.03 ▼0.61 |
| Leaflet-Mapper /wp-admin/options-general.php?page=wp-leaflet-mapper/wp-leaflet-mapper.php | 960 | 2.68 | 44.16 | 43.34 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- This plugin did not uninstall without warnings or errors
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
- The uninstall procedure has failed, leaving 7 options in the database
- widget_recent-comments
- Leaflet_Mapper_Option
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
These server-side errors were triggered
- 2 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=wp-leaflet-mapper/wp-leaflet-mapper.php
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
- > GET request to /wp-admin/options-general.php?page=wp-leaflet-mapper/wp-leaflet-mapper.php
- > Notice in wp-content/plugins/wp-leaflet-mapper/wp-leaflet-mapper.php+124
Undefined index: action
- > GET request to /wp-admin/options-general.php?page=wp-leaflet-mapper/wp-leaflet-mapper.php
- > Notice in wp-content/plugins/wp-leaflet-mapper/wp-leaflet-mapper.php+134
Trying to access array offset on value of type bool
- > GET request to /wp-admin/options-general.php?page=wp-leaflet-mapper/wp-leaflet-mapper.php
- > Notice in wp-content/plugins/wp-leaflet-mapper/wp-leaflet-mapper.php+137
Undefined index: ilm_admin_map_height
- > GET request to /wp-admin/options-general.php?page=wp-leaflet-mapper/wp-leaflet-mapper.php
- > Notice in wp-content/plugins/wp-leaflet-mapper/wp-leaflet-mapper.php+140
Undefined index: ilm_min_zoom
- > GET request to /wp-admin/options-general.php?page=wp-leaflet-mapper/wp-leaflet-mapper.php
- > Notice in wp-content/plugins/wp-leaflet-mapper/wp-leaflet-mapper.php+143
Undefined index: ilm_max_zoom
- > GET request to /wp-admin/options-general.php?page=wp-leaflet-mapper/wp-leaflet-mapper.php
- > Notice in wp-content/plugins/wp-leaflet-mapper/wp-leaflet-mapper.php+146
Undefined index: ilm_post_type
- > GET request to /wp-admin/options-general.php?page=wp-leaflet-mapper/wp-leaflet-mapper.php
- > Notice in wp-content/plugins/wp-leaflet-mapper/wp-leaflet-mapper.php+149
Undefined index: ilm_select_maptile
- > GET request to /wp-admin/options-general.php?page=wp-leaflet-mapper/wp-leaflet-mapper.php
- > Notice in wp-content/plugins/wp-leaflet-mapper/wp-leaflet-mapper.php+43
Undefined index: post
SRP 50% 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
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function load_plugin_textdomain() in wp-content/plugins/wp-leaflet-mapper/wp-leaflet-mapper.php:28
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
3 plugin tags: map, gmap, leaflet
wp-leaflet-mapper/wp-leaflet-mapper.php Passed 13 tests
"WP Leaflet Mapper" version 1.0.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
109 characters long description:
Supports switching from GMap to Leaflet. Display map on post screen and save LatLng as a custom field at GUI.
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
Good job! No executable or dangerous file extensions detected252 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 17 | 22 | 205 |
| PO File | 1 | 17 | 19 | 47 |
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.27 |
| 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 | 8 | |
| ▷ Named functions | 8 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/center_icon.png | 3.79KB | 1.48KB | ▼ 61.03% |
| img/location_icon.png | 1.41KB | 1.46KB | 0.00% |