Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼0.06MB] [CPU: ▼184.48ms] Passed 4 tests
A check of server-side resources used by Geo Locater
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.95 ▲0.11 | 42.97 ▲5.34 |
| Dashboard /wp-admin | 3.07 ▲0.01 | 38.08 ▼14.92 |
| Posts /wp-admin/edit.php | 3.12 ▲0.01 | 35.82 ▼18.35 |
| Add New Post /wp-admin/post-new.php | 5.08 ▼0.35 | 80.57 ▼700.89 |
| Media Library /wp-admin/upload.php | 3.07 ▲0.07 | 32.32 ▼3.74 |
| Add New Location /wp-admin/post-new.php?post_type=location | 3.13 | 45.21 |
| Locater Shortcode /wp-admin/edit.php?post_type=location&page=locater_shortcode | 3.05 | 29.42 |
| Geo Locater /wp-admin/edit.php?post_type=location | 3.10 | 31.54 |
| Settings /wp-admin/edit.php?post_type=location&page=locater_settings | 3.05 | 27.02 |
Server storage [IO: ▲0.04MB] [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: 1 new table, 1 new option
| New tables |
|---|
| wp_locater_entries |
| New WordPress options |
|---|
| locater_version |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Geo Locater
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,738 ▲142 | 15.97 ▼0.01 | 10.33 ▼1.05 | 44.64 ▼8.67 |
| Dashboard /wp-admin | 3,012 ▲78 | 5.95 ▼0.15 | 151.17 ▼1.00 | 129.37 ▲19.95 |
| Posts /wp-admin/edit.php | 2,790 ▲51 | 2.61 ▼0.10 | 70.32 ▼9.17 | 93.23 ▼0.72 |
| Add New Post /wp-admin/post-new.php | 1,716 ▲33 | 18.76 ▼0.09 | 406.08 ▼11.76 | 108.71 ▼5.29 |
| Media Library /wp-admin/upload.php | 1,872 ▲65 | 5.04 ▲0.01 | 152.63 ▼29.74 | 149.68 ▲34.06 |
| Add New Location /wp-admin/post-new.php?post_type=location | 2,374 | 4.55 | 108.51 | 109.31 |
| Locater Shortcode /wp-admin/edit.php?post_type=location&page=locater_shortcode | 1,085 | 2.09 | 56.76 | 75.13 |
| Geo Locater /wp-admin/edit.php?post_type=location | 1,461 | 2.65 | 68.03 | 78.67 |
| Settings /wp-admin/edit.php?post_type=location&page=locater_settings | 1,208 | 2.15 | 58.00 | 78.61 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% 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
- This plugin does not fully uninstall, leaving 1 table in the database
- wp_locater_entries
- Zombie WordPress options detected upon uninstall: 1 option
- locater_version
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
These errors were triggered by the plugin
- 4 occurences, only the last one shown
- > GET request to /wp-admin/edit.php?post_type=location&page=locater_settings
- > Deprecated in wp-includes/class-wp-hook.php+303
Non-static method Locater::locater_scripts() should not be called statically
- 6 occurences, only the last one shown
- > GET request to /wp-admin/post-new.php?post_type=location
- > Warning in wp-content/plugins/geo-locater/classes/class.locater.api.php+112
count(): Parameter must be an array or an object that implements Countable
- 5 occurences, only the last one shown
- > GET request to /wp-admin/post-new.php?post_type=location
- > Notice in wp-content/plugins/geo-locater/classes/class.locater.php+160
Trying to access array offset on value of type bool
SRP 0% 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
- 4× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/geo-locater/classes/class.locater.php
- > /wp-content/plugins/geo-locater/classes/class.locater.api.php
- > /wp-content/plugins/geo-locater/classes/class.locater.front.php
- > /wp-content/plugins/geo-locater/locater.php
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function current_user_can() in wp-content/plugins/geo-locater/tpl/shortcode-template.php:9
- > PHP Fatal error
Uncaught Error: Call to undefined function current_user_can() in wp-content/plugins/geo-locater/tpl/settings-template.php:7
- > 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 96% 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
6 plugin tags: store finder, google map, geo coding, geo location, nearby location...
geo-locater/locater.php 92% from 13 tests
The primary PHP file in "Geo Locater" version 1.2 is used by WordPress to initiate all plugin functionality
Please make the necessary changes and fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("geo-locater.php" instead of "locater.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
There were no executable files found in this plugin721 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 136 | 213 | 480 |
| JavaScript | 2 | 48 | 7 | 198 |
| CSS | 1 | 6 | 0 | 43 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.24 |
| Average class complexity | 10.67 |
| ▷ Minimum class complexity | 6.00 |
| ▷ Maximum class complexity | 19.00 |
| Average method complexity | 2.32 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 14.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 | 22 | |
| ▷ Static methods | 21 | 95.45% |
| ▷ Public methods | 22 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 9 | |
| ▷ Global constants | 9 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/red-dot.png | 1.31KB | 1.07KB | ▼ 18.25% |
| img/loc.png | 0.48KB | 0.38KB | ▼ 21.47% |