Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.22MB] [CPU: ▼301.51ms] Passed 4 tests
A check of server-side resources used by Address Geocoder
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.01 | 71.66 ▲14.16 |
| Dashboard /wp-admin | 3.43 ▲0.02 | 37.55 ▼1.23 |
| Posts /wp-admin/edit.php | 3.65 ▲0.01 | 42.79 ▲0.31 |
| Add New Post /wp-admin/post-new.php | 6.05 ▼0.92 | 83.88 ▼1,204.04 |
| Media Library /wp-admin/upload.php | 3.31 ▲0.01 | 24.91 ▼1.09 |
| Address Geocoder /wp-admin/options-general.php?page=address-geocoder-options | 3.27 | 26.32 |
Server storage [IO: ▲0.16MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 6 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for Address Geocoder
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,799 ▲45 | 15.98 ▼0.10 | 7.42 ▲0.08 | 2.83 ▼0.01 |
| Dashboard /wp-admin | 2,897 ▲39 | 6.17 ▲0.01 | 117.26 ▼17.67 | 161.21 ▲6.52 |
| Posts /wp-admin/edit.php | 2,696 ▲2 | 3.24 ▼0.01 | 63.85 ▼2.51 | 140.23 ▼6.84 |
| Add New Post /wp-admin/post-new.php | 1,793 ▲122 | 17.94 ▼3.60 | 402.40 ▼48.99 | 164.60 ▲3.48 |
| Media Library /wp-admin/upload.php | 1,706 ▲11 | 5.52 ▲0.02 | 148.17 ▲4.33 | 196.91 ▲5.73 |
| Address Geocoder /wp-admin/options-general.php?page=address-geocoder-options | 1,197 | 2.41 | 54.93 | 114.03 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Uninstall script ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/address-geocoder/address-geocoder.php:20
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 97% 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: Please add images for these screenshots: #1 (The meta box before clicking "Geocode"), #2 (The meta box after clicking "Geocode"), #3 (The settings page)
address-geocoder/address-geocoder.php Passed 13 tests
The main file in "Address Geocoder" v. 1.0.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
36 characters long description:
Attach location information to posts
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
There were no executable files found in this plugin230 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 57 | 46 | 172 |
| JavaScript | 1 | 12 | 3 | 58 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.45 |
| Average class complexity | 33.00 |
| ▷ Minimum class complexity | 33.00 |
| ▷ Maximum class complexity | 33.00 |
| Average method complexity | 4.20 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 10 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 10 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 4 | |
| ▷ Named functions | 4 | 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 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
3 PNG files occupy 0.14MB with 0.11MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| (invalid) screenshot-3.png | 45.06KB | 0.00KB | ▼ 100.00% |
| screenshot-1.png | 33.43KB | 13.32KB | ▼ 60.14% |
| screenshot-2.png | 67.07KB | 24.93KB | ▼ 62.83% |