Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.07MB] [CPU: ▼6.22ms] Passed 4 tests
An overview of server-side resources used by WordPress Accurate Geolocation
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.53 ▲0.07 | 38.29 ▼4.87 |
| Dashboard /wp-admin | 3.38 ▲0.08 | 47.30 ▼2.91 |
| Posts /wp-admin/edit.php | 3.49 ▲0.14 | 51.04 ▲6.88 |
| Add New Post /wp-admin/post-new.php | 5.96 ▲0.07 | 84.03 ▼20.15 |
| Media Library /wp-admin/upload.php | 3.30 ▲0.07 | 34.89 ▲3.06 |
| Accurate Geolocation /wp-admin/options-general.php?page=accurate_geolocation | 3.27 | 32.08 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 4 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| theysaidso_admin_options |
| agl_settings |
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WordPress Accurate Geolocation
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,891 ▲156 | 14.03 ▼0.27 | 31.40 ▲29.06 | 39.40 ▼9.44 |
| Dashboard /wp-admin | 2,213 ▲25 | 5.88 ▲1.01 | 108.57 ▼6.57 | 42.19 ▼3.74 |
| Posts /wp-admin/edit.php | 2,096 ▲7 | 2.01 ▲0.01 | 41.01 ▼4.59 | 34.79 ▼4.38 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲22 | 22.95 ▲5.35 | 635.39 ▼3.20 | 57.30 ▲7.17 |
| Media Library /wp-admin/upload.php | 1,395 ▲10 | 4.29 ▲0.09 | 101.11 ▼3.47 | 42.87 ▼4.23 |
| Accurate Geolocation /wp-admin/options-general.php?page=accurate_geolocation | 979 | 2.05 | 23.03 | 27.25 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- The uninstall procedure has failed, leaving 7 options in the database
- agl_settings
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Looking good! No server-side errors or output on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Please fix the following attributes:
- Screenshots: Please describe screenshot #10 in wp-accurate-geolocation/assets to your readme.txt
- Tags: You are using too many tags: 24 tag instead of maximum 10
wp-accurate-geolocation/wp-accu-geolocation.php 77% from 13 tests
The main PHP file in "WordPress Accurate Geolocation" ver. 1.0.0 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Domain Path: The domain path folder does not exist ("/languages")
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wp-accurate-geolocation.php" instead of "wp-accu-geolocation.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Good job! No executable or dangerous file extensions detected632 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 93 | 14 | 349 |
| JavaScript | 2 | 32 | 33 | 283 |
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.25 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 25 | |
| ▷ Named functions | 25 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected