Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▲0.22MB] [CPU: ▼145.33ms] Passed 4 tests
Analyzing server-side resources used by Map pins
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.04 ▲0.32 | 39.84 ▲12.24 |
| Dashboard /wp-admin | 3.27 ▲0.22 | 40.64 ▼7.67 |
| Posts /wp-admin/edit.php | 3.38 ▲0.27 | 48.47 ▼1.26 |
| Add New Post /wp-admin/post-new.php | 5.63 ▲0.19 | 92.65 ▼574.19 |
| Media Library /wp-admin/upload.php | 3.21 ▲0.21 | 37.82 ▲1.80 |
| Locations /wp-admin/admin.php?page=mappins-menu-markers | 3.18 | 33.69 |
| Settings /wp-admin/admin.php?page=mappins-menu-settings | 3.18 | 27.94 |
| Help /wp-admin/admin.php?page=mappins-menu-help | 3.18 | 32.55 |
Server storage [IO: ▲0.67MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 338 new files
Database: 1 new table, no new options
| New tables |
|---|
| wp_mappins_markers |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Map pins
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,732 ▲136 | 16.32 ▲1.07 | 7.33 ▼3.65 | 49.90 ▼3.12 |
| Dashboard /wp-admin | 3,017 ▲83 | 6.17 ▲0.24 | 143.66 ▼0.51 | 132.70 ▲4.58 |
| Posts /wp-admin/edit.php | 2,811 ▲72 | 2.71 ▲0.02 | 68.23 ▼1.67 | 117.81 ▲22.35 |
| Add New Post /wp-admin/post-new.php | 1,644 ▼39 | 19.03 ▲0.31 | 405.02 ▼6.45 | 131.27 ▲16.75 |
| Media Library /wp-admin/upload.php | 1,802 ▼5 | 5.04 ▲0.02 | 134.19 ▼29.31 | 156.53 ▲29.14 |
| Locations /wp-admin/admin.php?page=mappins-menu-markers | 1,111 | 2.09 | 53.52 | 68.95 |
| Settings /wp-admin/admin.php?page=mappins-menu-settings | 3,494 | 2.21 | 65.84 | 176.16 |
| Help /wp-admin/admin.php?page=mappins-menu-help | 1,159 | 2.21 | 57.99 | 68.73 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- Zombie tables were found after uninstall: 1 table
- wp_mappins_markers
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
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
Almost there! Just fix the following items
- 5× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/map-pins/map-pins.php
- > /wp-content/plugins/map-pins/include/marker.php
- > /wp-content/plugins/map-pins/include/xcos.php
- > /wp-content/plugins/map-pins/include/xcos_country.php
- > /wp-content/plugins/map-pins/include/mappins.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need your attention:
- Tags: There are too many tags (23 tag instead of maximum 10)
map-pins/map-pins.php Passed 13 tests
The main PHP file in "Map pins" ver. 1.29 adds more information about the plugin and also serves as the entry point for this plugin
46 characters long description:
Show pins on a map from an admin defined table
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
No dangerous file extensions were detected3,329 lines of code in 13 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PO File | 2 | 604 | 619 | 1,240 |
| PHP | 5 | 77 | 87 | 903 |
| JavaScript | 5 | 28 | 114 | 677 |
| CSS | 1 | 12 | 8 | 509 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 18.50 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 40.00 |
| Average method complexity | 2.75 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 12.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 40 | |
| ▷ Static methods | 23 | 57.50% |
| ▷ Public methods | 40 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 5 | |
| ▷ Global constants | 5 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
320 PNG files occupy 0.35MB with 0.09MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| pics/markers/black_airport.png | 1.17KB | 0.87KB | ▼ 25.40% |
| pics/markers/brown_bench.png | 1.56KB | 1.32KB | ▼ 15.31% |
| pics/markers/blue_mine.png | 1.36KB | 0.96KB | ▼ 28.89% |
| pics/markers/brown_entrance.png | 0.85KB | 0.61KB | ▼ 28.80% |
| pics/markers/red_stadium.png | 1.44KB | 1.06KB | ▼ 26.32% |