Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.13MB] [CPU: ▼4.48ms] Passed 4 tests
Analyzing server-side resources used by YaMaps for WordPress Plugin
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.58 ▲0.12 | 38.56 ▼1.83 |
| Dashboard /wp-admin | 3.44 ▲0.14 | 44.00 ▼5.04 |
| Posts /wp-admin/edit.php | 3.49 ▲0.13 | 46.86 ▼3.26 |
| Add New Post /wp-admin/post-new.php | 6.03 ▲0.14 | 95.11 ▼7.78 |
| Media Library /wp-admin/upload.php | 3.36 ▲0.13 | 35.43 ▲1.71 |
Server storage [IO: ▲0.65MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 18 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for YaMaps for WordPress Plugin
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,809 ▲74 | 13.28 ▼0.91 | 1.54 ▼0.25 | 40.76 ▼4.33 |
| Dashboard /wp-admin | 2,215 ▲24 | 4.88 ▼1.02 | 112.21 ▲10.15 | 43.10 ▼1.61 |
| Posts /wp-admin/edit.php | 2,101 ▲9 | 2.05 ▲0.02 | 39.87 ▼1.66 | 36.63 ▲0.27 |
| Add New Post /wp-admin/post-new.php | 1,529 ▲7 | 17.71 ▼5.63 | 602.66 ▼59.84 | 51.46 ▼6.34 |
| Media Library /wp-admin/upload.php | 1,397 ▲12 | 4.15 ▼0.05 | 99.26 ▼0.65 | 43.37 ▲1.41 |
| YaMaps /wp-admin/yamaps-options.php | 26 | 0.44 | 0.12 | 14.19 |
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
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/yamaps/yamap.php:53
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/yamaps/options.php:6
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
These are user-side errors you should fix
- > GET request to /wp-admin/yamaps-options.php
- > Network (severe)
wp-admin/yamaps-options.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 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
Attributes that need to be fixed:
- Screenshots: Add images for these screenshots: #1 (Visual shortcode dialog window.), #2 (Shortcode in TinyMCE editor.), #3 (Map on the blog page.), #4 (Shortcode button.), #5 (Visual selecting the marker color.)
yamaps/yamap.php 92% from 13 tests
"YaMaps for WordPress Plugin" version 0.6.26's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("yamaps.php" instead of "yamap.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 detected1,667 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 2 | 218 | 60 | 730 |
| PHP | 2 | 141 | 92 | 611 |
| PO File | 1 | 61 | 63 | 227 |
| SVG | 2 | 0 | 2 | 60 |
| CSS | 1 | 6 | 0 | 33 |
| HTML | 1 | 0 | 0 | 6 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
There are no cyclomatic complexity problems detected for this plugin
| 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 | 15 | |
| ▷ Named functions | 15 | 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
PNG files should be compressed to save space and minimize bandwidth usage
No PNG files were detected