Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼5.76ms] Passed 4 tests
Server-side resources used by Advanced Custom Fields - Location Field add-on
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.04 | 40.30 ▼3.78 |
Dashboard /wp-admin | 3.35 ▲0.00 | 50.81 ▼14.72 |
Posts /wp-admin/edit.php | 3.46 ▲0.10 | 44.69 ▼3.76 |
Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 89.67 ▼0.78 |
Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 37.49 ▲0.11 |
Server storage [IO: ▲0.34MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 13 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-comments |
db_upgraded |
widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for Advanced Custom Fields - Location Field add-on
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲43 | 14.57 ▲0.22 | 2.18 ▲0.57 | 45.01 ▼12.29 |
Dashboard /wp-admin | 2,192 ▲21 | 5.63 ▲0.09 | 92.30 ▲2.69 | 44.03 ▲3.56 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 1.98 ▲0.00 | 37.98 ▲1.21 | 35.52 ▲1.61 |
Add New Post /wp-admin/post-new.php | 1,526 ▼3 | 23.21 ▼0.35 | 647.95 ▲15.20 | 50.62 ▲0.94 |
Media Library /wp-admin/upload.php | 1,400 ▲6 | 4.17 ▲0.02 | 101.12 ▲0.34 | 43.14 ▼0.40 |
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
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 1× PHP files trigger server errors 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 just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that need to be fixed:
- Tags: You are using too many tags: 11 tag instead of maximum 10
- Screenshots: These screenshots require images: #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)
advanced-custom-fields-location-field-add-on/location-field.php 85% from 13 tests
Analyzing the main PHP file in "Advanced Custom Fields - Location Field add-on" version 1.0
You should first fix the following items:
- 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
- Main file name: It is recommended to name the main PHP file as the plugin slug ("advanced-custom-fields-location-field-add-on.php" instead of "location-field.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Success! There were no dangerous files found in this plugin488 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 overview of cyclomatic complexity and code structure
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
All PNG images should be compressed to minimize bandwidth usage for end users
5 compressed PNG files occupy 0.30MB
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-2.png | 94.86KB | 98.19KB | 0.00% |
screenshot-4.png | 94.68KB | 97.67KB | 0.00% |
screenshot-3.png | 92.73KB | 95.50KB | 0.00% |
screenshot-1.png | 27.35KB | 27.79KB | 0.00% |
img/sprite.png | 1.02KB | 1.00KB | ▼ 1.34% |