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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼7.14ms] Passed 4 tests
Server-side resources used by Advanced Custom Fields: Leaflet Field
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 36.75 ▼5.12 |
Dashboard /wp-admin | 3.32 ▼0.02 | 50.33 ▼14.96 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 44.08 ▲1.84 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 79.15 ▼10.32 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.67 ▲4.03 |
Server storage [IO: ▲1.13MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 100 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
Advanced Custom Fields: Leaflet Field: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲79 | 13.27 ▼1.03 | 1.90 ▲0.08 | 43.94 ▼0.55 |
Dashboard /wp-admin | 2,206 ▲18 | 4.84 ▼0.97 | 99.19 ▼19.40 | 37.09 ▼9.51 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.03 ▼0.03 | 35.88 ▲1.66 | 33.76 ▼5.24 |
Add New Post /wp-admin/post-new.php | 1,533 ▲12 | 23.30 ▲0.00 | 670.13 ▼8.96 | 61.40 ▲1.12 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.11 ▼0.08 | 94.56 ▼7.97 | 45.90 ▼0.65 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
Smoke tests 50% 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 0% 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
Almost there! Just fix the following items
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/advanced-custom-fields-leaflet-field/js/input.js.php
- 6× PHP files trigger server errors when accessed directly:
- > PHP Notice
Trying to access array offset on value of type null in wp-content/plugins/advanced-custom-fields-leaflet-field/js/input.js.php on line 4
- > PHP Fatal error
Uncaught Error: Class 'acf_Field' not found in wp-content/plugins/advanced-custom-fields-leaflet-field/leaflet_field-v3.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function trailingslashit() in wp-content/plugins/advanced-custom-fields-leaflet-field/acf-leaflet_field.php:28
- > PHP Notice
Undefined variable: field in wp-content/plugins/advanced-custom-fields-leaflet-field/js/input.js.php on line 4
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/advanced-custom-fields-leaflet-field/leaflet_field-v4.php:3
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/advanced-custom-fields-leaflet-field/leaflet_field-v5.php:3
- > PHP Notice
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
9 plugin tags: admin, acf4, map markers, map, acf...
advanced-custom-fields-leaflet-field/acf-leaflet_field.php 85% from 13 tests
The primary PHP file in "Advanced Custom Fields: Leaflet Field" version 1.2.1 is used by WordPress to initiate all plugin functionality
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("advanced-custom-fields-leaflet-field.php" instead of "acf-leaflet_field.php")
- Git Repository: An alternative Git repository was detected
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Success! There were no dangerous files found in this plugin25,751 lines of code in 78 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 51 | 6,661 | 1,990 | 21,896 |
CSS | 5 | 156 | 58 | 1,235 |
PHP | 5 | 390 | 773 | 916 |
HTML | 6 | 90 | 3 | 762 |
Markdown | 5 | 183 | 0 | 529 |
SVG | 3 | 2 | 1 | 250 |
JSON | 2 | 0 | 0 | 96 |
Stylus | 1 | 0 | 0 | 67 |
PHP code Passed 2 tests
Analyzing 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.05 |
Average class complexity | 3.25 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 4.00 |
Average method complexity | 1.26 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 3.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 4 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 4 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 35 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 35 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 1 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
13 PNG files occupy 0.03MB with 0.00MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
js/Leaflet.draw/examples/libs/images/marker-icon.png | 1.71KB | 1.56KB | ▼ 8.59% |
js/Leaflet.draw/dist/images/spritesheet-2x.png | 2.03KB | 1.27KB | ▼ 37.63% |
js/Leaflet.draw/examples/libs/images/marker-icon-2x.png | 3.94KB | 2.53KB | ▼ 35.71% |
js/leaflet/images/marker-shadow.png | 0.78KB | 1.16KB | 0.00% |
js/Leaflet.draw/examples/libs/images/marker-shadow.png | 0.78KB | 1.16KB | 0.00% |