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
This plugin's installer ran successfully
Server metrics [RAM: ▲4.26MB] [CPU: ▲32.34ms] Passed 4 tests
Analyzing server-side resources used by MapifyLite (by MapifyPro)
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 7.65 ▲4.19 | 71.39 ▲27.13 |
| Dashboard /wp-admin | 7.52 ▲4.21 | 75.43 ▲25.98 |
| Posts /wp-admin/edit.php | 7.81 ▲4.45 | 85.85 ▲39.61 |
| Add New Post /wp-admin/post-new.php | 10.21 ▲4.32 | 132.21 ▲36.62 |
| Media Library /wp-admin/upload.php | 7.55 ▲4.32 | 73.57 ▲40.00 |
| Map Settings /wp-admin/edit.php?post_type=map | 7.27 | 62.09 |
| Map Locations /wp-admin/edit.php?post_type=map-location | 7.66 | 61.91 |
Server storage [IO: ▲11.75MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 470 new files
Database: no new tables, 9 new options
| New WordPress options |
|---|
| acf_version |
| widget_recent-posts |
| db_upgraded |
| mpfy_flush_required |
| theysaidso_admin_options |
| can_compress_scripts |
| mpfy_plugin_version |
| widget_recent-comments |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for MapifyLite (by MapifyPro)
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,999 ▲253 | 13.57 ▼1.02 | 4.88 ▲3.13 | 39.21 ▼5.30 |
| Dashboard /wp-admin | 2,288 ▲97 | 4.88 ▼0.03 | 111.61 ▼11.72 | 52.75 ▲8.38 |
| Posts /wp-admin/edit.php | 2,174 ▲85 | 2.17 ▲0.12 | 43.08 ▲7.17 | 46.46 ▲13.78 |
| Add New Post /wp-admin/post-new.php | 6,717 ▲5,187 | 28.90 ▲10.76 | 1,082.59 ▲462.75 | 40.31 ▼21.59 |
| Media Library /wp-admin/upload.php | 2,014 ▲626 | 8.34 ▲4.15 | 239.83 ▲141.91 | 61.54 ▲19.21 |
| Map Settings /wp-admin/edit.php?post_type=map | 2,885 | 9.05 | 213.02 | 131.25 |
| MapifyPro Installer /wp-admin/mapify.php?page=mapifypro-installer | 26 | 0.44 | 0.13 | 14.38 |
| Map Locations /wp-admin/edit.php?post_type=map-location | 1,144 | 2.13 | 35.17 | 39.51 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- The uninstall procedure has failed, leaving 9 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
- mpfy_plugin_version
- mpfy_flush_required
- db_upgraded
- acf_version
- widget_recent-comments
- widget_recent-posts
Smoke tests 25% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
SRP 0% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 3× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/mapifylite/templates/popup.php
- > /wp-content/plugins/mapifylite/templates/map.js.php
- > /wp-content/plugins/mapifylite/lib/acf-mapifylite/public/partials/acf-mapifylite-public-display.php
- 144× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/mapifylite/modules/map-location-popup.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/mapifylite/modules/updater.php:14
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/mapifylite/lib/advanced-custom-fields/includes/fields/class-acf-field-group.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function acf_esc_attr_e() in wp-content/plugins/mapifylite/lib/acf-mapifylite/admin/partials/mapify-map-selector-field-display.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/mapifylite/lib/advanced-custom-fields/includes/api/api-template.php:928
- > PHP Fatal error
Uncaught Error: Call to undefined function acf_idify() in wp-content/plugins/mapifylite/lib/advanced-custom-fields/includes/admin/views/field-group-field.php:5
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/mapifylite/lib/advanced-custom-fields/includes/fields/class-acf-field-link.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/mapifylite/modules/service-map-settings.php:17
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/mapifylite/lib/advanced-custom-fields/includes/fields/class-acf-field-output.php:5
- > PHP Fatal error
Uncaught Error: Class 'WP_Image_Editor_GD' not found in wp-content/plugins/mapifylite/lib/wpthumb/wpthumb.image-editor.php:3
- > 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)
There are user-side issues you should fix
- > GET request to /wp-admin/mapify.php?page=mapifypro-installer
- > Network (severe)
wp-admin/mapify.php?page=mapifypro-installer - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need to be fixed:
- Screenshots: No descriptions were found for these screenshots #1, #2, #3, #4, #5, #6 in mapifylite/assets to your readme.txt
mapifylite/mapify_lite.php 85% from 13 tests
The main PHP file in "MapifyLite (by MapifyPro)" ver. 4.3.4 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Main file name: It is recommended to name the main PHP file as the plugin slug ("mapifylite.php" instead of "mapify_lite.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
There were no executable files found in this plugin123,336 lines of code in 328 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PO File | 32 | 23,726 | 40,123 | 49,150 |
| JavaScript | 44 | 9,574 | 7,726 | 36,518 |
| PHP | 210 | 12,174 | 21,866 | 21,417 |
| SVG | 11 | 1 | 0 | 11,620 |
| CSS | 25 | 766 | 232 | 4,174 |
| Sass | 2 | 27 | 5 | 262 |
| LESS | 1 | 11 | 5 | 152 |
| JSON | 1 | 0 | 0 | 21 |
| Markdown | 1 | 11 | 0 | 14 |
| Ruby | 1 | 2 | 0 | 8 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.34 |
| Average class complexity | 12.42 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 78.00 |
| Average method complexity | 2.60 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 24.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 134 | |
| ▷ Abstract classes | 3 | 2.24% |
| ▷ Concrete classes | 131 | 97.76% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 962 | |
| ▷ Static methods | 13 | 1.35% |
| ▷ Public methods | 931 | 96.78% |
| ▷ Protected methods | 1 | 0.10% |
| ▷ Private methods | 30 | 3.12% |
| Functions | 539 | |
| ▷ Named functions | 538 | 99.81% |
| ▷ Anonymous functions | 1 | 0.19% |
| Constants | 28 | |
| ▷ Global constants | 27 | 96.43% |
| ▷ Class constants | 1 | 3.57% |
| ▷ Public constants | 1 | 100.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
52 PNG files occupy 0.24MB with 0.15MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/zoom-out.png | 0.99KB | 0.12KB | ▼ 87.71% |
| assets/images/arrow.png | 1.31KB | 0.25KB | ▼ 80.61% |
| lib/advanced-custom-fields/assets/images/acf-logo.png | 3.40KB | 3.39KB | 0.23% |
| assets/images/mpfy-p-sprite.png | 35.91KB | 13.52KB | ▼ 62.35% |
| assets/images/ico-search.png | 3.11KB | 0.49KB | ▼ 84.14% |