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
Installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼9.26ms] Passed 4 tests
An overview of server-side resources used by BMLT Meeting Map
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 34.49 ▼6.57 |
Dashboard /wp-admin | 3.32 ▼0.03 | 44.93 ▼14.62 |
Posts /wp-admin/edit.php | 3.43 ▲0.07 | 48.68 ▲1.73 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 82.60 ▼11.88 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 31.31 ▼3.98 |
Server storage [IO: ▲0.36MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 35 new files
Database: no new tables, 7 new options
New WordPress options |
---|
db_upgraded |
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
bmlt_meeting_map_options |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for BMLT Meeting Map
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,802 ▲55 | 14.33 ▲0.01 | 1.80 ▼0.39 | 43.10 ▼0.24 |
Dashboard /wp-admin | 2,207 ▲27 | 5.66 ▲0.09 | 93.81 ▲8.01 | 41.72 ▲4.09 |
Posts /wp-admin/edit.php | 2,112 ▲12 | 2.00 ▲0.00 | 39.79 ▲0.79 | 37.54 ▲3.52 |
Add New Post /wp-admin/post-new.php | 1,546 ▲20 | 25.04 ▲1.94 | 615.64 ▼56.58 | 74.43 ▲20.65 |
Media Library /wp-admin/upload.php | 1,412 ▲9 | 4.16 ▼0.01 | 97.34 ▼3.65 | 41.36 ▼2.48 |
BMLT Meeting Map /wp-admin/meeting_map.php | 26 | 0.41 | 0.09 | 19.83 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 7 options in the database
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- bmlt_meeting_map_options
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 25% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
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
Almost there! Just fix the following items
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/bmlt-meeting-map/index.php
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/bmlt-meeting-map/meeting_map.php:398
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Please fix the following browser errors
- > GET request to /wp-admin/meeting_map.php
- > Network (severe)
wp-admin/meeting_map.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
8 plugin tags: meeting list, na, maps, meeting finder, addiction...
bmlt-meeting-map/meeting_map.php 92% from 13 tests
The main PHP file in "BMLT Meeting Map" ver. 2.6.0 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("bmlt-meeting-map.php" instead of "meeting_map.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
No dangerous file extensions were detected3,539 lines of code in 18 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 6 | 65 | 56 | 1,687 |
CSS | 2 | 87 | 38 | 1,052 |
PHP | 8 | 2 | 59 | 778 |
JSON | 2 | 0 | 0 | 22 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.32 |
Average class complexity | 73.00 |
▷ Minimum class complexity | 73.00 |
▷ Maximum class complexity | 73.00 |
Average method complexity | 3.17 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.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 | 25 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 21 | 84.00% |
▷ Protected methods | 1 | 4.00% |
▷ Private methods | 3 | 12.00% |
Functions | 1 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 1 | 100.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
12 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
map_images/NAMarkerS.png | 1.58KB | 0.78KB | ▼ 50.71% |
lang/ar.png | 0.49KB | 0.69KB | 0.00% |
lang/en.png | 0.58KB | 0.65KB | 0.00% |
map_images/NAMarkerSel.png | 2.86KB | 1.52KB | ▼ 46.81% |
lang/fr.png | 0.53KB | 0.63KB | 0.00% |