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.02MB] [CPU: ▼7.40ms] Passed 4 tests
An overview of server-side resources used by Magic Google Maps
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.03 | 36.87 ▲0.03 |
| Dashboard /wp-admin | 3.33 ▼0.02 | 44.76 ▼12.63 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 43.58 ▼4.09 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 78.47 ▼11.96 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 35.28 ▼0.93 |
Server storage [IO: ▲0.02MB] [DB: ▲0.31MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 7 new files
Database: no new tables, 15 new options
| New WordPress options |
|---|
| widget_recent-posts |
| googlemapsCode |
| widget_theysaidso_widget |
| googlemapspinLng |
| enabledescription |
| height |
| placedescription |
| zoom |
| theysaidso_admin_options |
| can_compress_scripts |
| ... |
Browser metrics Passed 4 tests
Checking browser requirements for Magic Google Maps
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,826 ▲40 | 14.39 ▼0.01 | 7.00 ▲4.76 | 42.07 ▲0.95 |
| Dashboard /wp-admin | 2,203 ▲25 | 5.49 ▼0.22 | 93.06 ▼21.24 | 83.88 ▲46.03 |
| Posts /wp-admin/edit.php | 2,120 ▲20 | 2.52 ▲0.53 | 40.93 ▲4.10 | 34.88 ▼0.03 |
| Add New Post /wp-admin/post-new.php | 1,548 ▲12 | 23.35 ▲0.23 | 691.14 ▲10.89 | 35.77 ▼24.71 |
| Media Library /wp-admin/upload.php | 1,423 ▲23 | 5.03 ▲0.84 | 103.11 ▲0.40 | 70.63 ▲25.89 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.31MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- The uninstall procedure has failed, leaving 7 options in the database
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- placedescription
- theysaidso_admin_options
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
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× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/magic-google-maps/magic-Maps.php:27
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 93% 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: Too many tags (18 tag instead of maximum 10); only the first 5 tags are used in your directory listing
magic-google-maps/magic-Maps.php 92% from 13 tests
The primary PHP file in "Magic Google Maps" version 1.0.4 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("magic-google-maps.php" instead of "magic-Maps.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected343 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 41 | 29 | 276 |
| JavaScript | 2 | 17 | 9 | 64 |
| CSS | 1 | 0 | 0 | 3 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.02 |
| 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 | 20 | |
| ▷ Named functions | 20 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/Magic-maps.png | 1.69KB | 0.90KB | ▼ 47.02% |