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
Installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼7.19ms] Passed 4 tests
An overview of server-side resources used by ACF: Yandex Maps Field
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.02 | 33.68 ▼1.27 |
| Dashboard /wp-admin | 3.34 ▼0.01 | 46.01 ▼23.09 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 47.61 ▲2.35 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.02 | 89.59 ▼6.75 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 39.38 ▲4.91 |
| ACF Yandex Map Settings /wp-admin/options-general.php?page=acf-yandex-map | 3.22 | 28.49 |
Server storage [IO: ▲0.06MB] [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: 9 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-posts |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by ACF: Yandex Maps Field
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲58 | 13.17 ▼1.48 | 1.68 ▼0.06 | 37.89 ▼3.28 |
| Dashboard /wp-admin | 2,207 ▲19 | 5.86 ▲1.00 | 95.86 ▼13.37 | 41.16 ▼2.23 |
| Posts /wp-admin/edit.php | 2,093 ▲7 | 2.06 ▼0.07 | 37.67 ▲2.99 | 35.89 ▼0.61 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲17 | 23.18 ▲0.07 | 687.60 ▼8.47 | 64.12 ▲8.00 |
| Media Library /wp-admin/upload.php | 1,392 ▲1 | 4.22 ▲0.03 | 113.43 ▲4.22 | 49.90 ▲3.27 |
| ACF Yandex Map Settings /wp-admin/options-general.php?page=acf-yandex-map | 779 | 2.03 | 24.22 | 24.99 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
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 fix the following
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/acf-yandex-maps-field/acf-yandex-map-fields.php:18
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 83% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
6 plugin tags: yandex, fields, map, advanced custom fields, acf...
acf-yandex-maps-field/acf-yandex-map-fields.php 62% from 13 tests
The main file in "ACF: Yandex Maps Field" v. 1.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please make the necessary changes and fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("acf-yandex-maps-field.php" instead of "acf-yandex-map-fields.php")
- Domain Path: The domain path points to a folder that does not exist ("/languages")
- Requires PHP: Required version number should only contain digits separated by dots (ex. "7.0" instead of "7.4 or higher")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Requires at least: Required version does not match the one declared in readme.txt ("5.0" instead of "6.1.1")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Good job! No executable or dangerous file extensions detected891 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 129 | 52 | 539 |
| JavaScript | 2 | 100 | 43 | 279 |
| PO File | 1 | 28 | 28 | 73 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 15.33 |
| ▷ Minimum class complexity | 4.00 |
| ▷ Maximum class complexity | 21.00 |
| Average method complexity | 3.26 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 12.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 19 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 17 | 89.47% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 2 | 10.53% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
No PNG files were detected