Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.03MB] [CPU: ▼199.77ms] Passed 4 tests
Analyzing server-side resources used by Advanced Custom Fields - Location Field add-on
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.88 ▲0.04 | 32.88 ▲6.57 |
| Dashboard /wp-admin | 3.10 ▲0.04 | 37.33 ▼4.88 |
| Posts /wp-admin/edit.php | 3.16 ▲0.04 | 34.35 ▼4.84 |
| Add New Post /wp-admin/post-new.php | 5.47 ▲0.02 | 76.03 ▼792.96 |
| Media Library /wp-admin/upload.php | 3.05 ▲0.04 | 29.17 ▲3.60 |
Server storage [IO: ▲0.34MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 13 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Advanced Custom Fields - Location Field add-on: an overview of browser usage
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,666 ▲65 | 16.01 ▲0.03 | 8.87 ▲1.56 | 75.68 ▼2.50 |
| Dashboard /wp-admin | 2,930 ▲34 | 6.13 ▼0.11 | 122.36 ▼9.16 | 178.13 ▲6.21 |
| Posts /wp-admin/edit.php | 2,740 ▼3 | 3.24 ▲0.00 | 63.94 ▼1.93 | 137.65 ▲0.20 |
| Add New Post /wp-admin/post-new.php | 3,815 ▼0 | 19.29 ▼0.04 | 445.06 ▼4.66 | 162.19 ▼2.17 |
| Media Library /wp-admin/upload.php | 1,752 ▼0 | 5.54 ▲0.02 | 142.73 ▲8.96 | 183.34 ▼4.04 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
This plugin's uninstaller ran successfully
Smoke tests 75% 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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following items
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/advanced-custom-fields-location-field-add-on/location-field.php:476
- > PHP Fatal error
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 87% from 29 tests
readme.txt 88% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need to be fixed:
- Screenshots: Please add images for these screenshots: #1 (Location field and its options), #2 (Location field on an edit-post page), #3 (Type in a partial address or some coordinates), #4 (Choose to get the complete address)
- Tags: Too many tags (11 tag instead of maximum 10); only the first 5 tags are used in your directory listing
advanced-custom-fields-location-field-add-on/location-field.php 85% from 13 tests
The entry point to "Advanced Custom Fields - Location Field add-on" version 1.0 is a PHP file that has certain tags in its header comment area
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("advanced-custom-fields-location-field-add-on.php" instead of "location-field.php")
- 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
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
No dangerous file extensions were detected488 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 72 | 229 | 206 |
| JavaScript | 1 | 13 | 69 | 142 |
| Markdown | 1 | 27 | 0 | 62 |
| CSS | 1 | 0 | 0 | 48 |
| PO File | 1 | 14 | 26 | 30 |
PHP code Passed 2 tests
An short overview of 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.14 |
| Average class complexity | 6.00 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 9.00 |
| Average method complexity | 1.62 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 4.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 16 | |
| ▷ Static methods | 1 | 6.25% |
| ▷ Public methods | 13 | 81.25% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 3 | 18.75% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 1 | 100.00% |
| ▷ Public constants | 1 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
5 compressed PNG files occupy 0.30MB
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/sprite.png | 1.02KB | 1.00KB | ▼ 1.34% |
| screenshot-1.png | 27.35KB | 27.79KB | 0.00% |
| screenshot-3.png | 92.73KB | 95.50KB | 0.00% |
| screenshot-2.png | 94.86KB | 98.19KB | 0.00% |
| screenshot-4.png | 94.68KB | 97.67KB | 0.00% |