Benchmarks
Plugin footprint 65% 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.66MB] [CPU: ▲2.09ms] Passed 4 tests
An overview of server-side resources used by Geo Redirects Lite
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.30 ▲0.84 | 50.54 ▲11.19 |
| Dashboard /wp-admin | 3.96 ▲0.66 | 59.13 ▲4.45 |
| Posts /wp-admin/edit.php | 4.01 ▲0.66 | 51.56 ▲3.74 |
| Add New Post /wp-admin/post-new.php | 6.54 ▲0.66 | 101.49 ▼2.79 |
| Media Library /wp-admin/upload.php | 3.89 ▲0.66 | 43.02 ▲2.94 |
| Settings /wp-admin/admin.php?page=geot-settings | 3.93 | 37.43 |
| Geo Redirects /wp-admin/edit.php?post_type=geotr_cpt | 3.93 | 46.25 |
| Debug data /wp-admin/admin.php?page=geot-debug-data | 4.03 | 36.07 |
Server storage [IO: ▲3.82MB] [DB: ▲0.01MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 222 new files
Database: 1 new table, 6 new options
| New tables |
|---|
| wp_geot_countries |
| New WordPress options |
|---|
| widget_recent-comments |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by Geo Redirects Lite
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,837 ▲66 | 13.55 ▼1.20 | 1.69 ▼0.28 | 40.91 ▼0.86 |
| Dashboard /wp-admin | 2,240 ▲49 | 5.00 ▼0.90 | 107.38 ▲0.05 | 41.73 ▼4.69 |
| Posts /wp-admin/edit.php | 2,126 ▲37 | 2.01 ▼0.04 | 37.51 ▼2.69 | 32.79 ▼4.56 |
| Add New Post /wp-admin/post-new.php | 1,561 ▲42 | 23.21 ▼0.03 | 658.45 ▼32.93 | 66.48 ▼1.61 |
| Media Library /wp-admin/upload.php | 1,422 ▲31 | 4.41 ▲0.29 | 96.00 ▼12.78 | 45.39 ▼1.61 |
| Settings /wp-admin/admin.php?page=geot-settings | 3,462 | 2.02 | 24.90 | 29.68 |
| Geo Redirects /wp-admin/edit.php?post_type=geotr_cpt | 1,090 | 1.98 | 35.71 | 29.13 |
| Debug data /wp-admin/admin.php?page=geot-debug-data | 820 | 2.03 | 25.02 | 26.44 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
- Zombie tables detected upon uninstall: 1 table
- wp_geot_countries
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Smoke test failed, please fix the following
- > GET request to /wp-admin/admin.php?page=geot-debug-data
- > Notice in wp-content/plugins/geo-redirects/vendor/timersys/geot-functions/src/GeotFunctions.php+309
Undefined variable: record
SRP 0% 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
Please fix the following
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/geo-redirects/vendor/mobiledetect/mobiledetectlib/export/exportToJSON.php
- 64× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Psr7\\Request' not found in wp-content/plugins/geo-redirects/vendor/guzzlehttp/psr7/src/ServerRequest.php:25
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\RequestInterface' not found in wp-content/plugins/geo-redirects/vendor/psr/http-message/src/ServerRequestInterface.php:43
- > PHP Fatal error
Uncaught Error: Class 'GeotWP\\Record\\AbstractRecord' not found in wp-content/plugins/geo-redirects/vendor/timersys/geotargetingwp/src/Record/City.php:5
- > PHP Fatal error
Uncaught Error: Class 'GeotWP\\Exception\\GeotException' not found in wp-content/plugins/geo-redirects/vendor/timersys/geotargetingwp/src/Exception/OutofCreditsException.php:10
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\RequestException' not found in wp-content/plugins/geo-redirects/vendor/guzzlehttp/guzzle/src/Exception/BadResponseException.php:7
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/geo-redirects/vendor/guzzlehttp/psr7/src/BufferStream.php:14
- > PHP Fatal error
Uncaught Error: Interface 'Dotenv\\Exception\\ExceptionInterface' not found in wp-content/plugins/geo-redirects/vendor/vlucas/phpdotenv/src/Exception/InvalidFileException.php:10
- > PHP Fatal error
Uncaught Error: Class 'Jaybizzle\\CrawlerDetect\\Fixtures\\AbstractProvider' not found in wp-content/plugins/geo-redirects/vendor/jaybizzle/crawler-detect/src/Fixtures/Headers.php:14
- > PHP Fatal error
Uncaught Error: Class 'GeotWP\\Record\\AbstractRecord' not found in wp-content/plugins/geo-redirects/vendor/timersys/geotargetingwp/src/Record/Continent.php:5
- > PHP Fatal error
Uncaught Error: Class 'GeotWP\\Record\\AbstractRecord' not found in wp-content/plugins/geo-redirects/vendor/timersys/geotargetingwp/src/Record/Country.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 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
6 plugin tags: geotargeting, geolite, geo redirects, redirect by country, maxmind...
geo-redirects/geotr.php 85% from 13 tests
Analyzing the main PHP file in "Geo Redirects Lite" version 1.0.0
It is important to fix the following:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Main file name: The principal plugin file should be the same as the plugin slug ("geo-redirects.php" instead of "geotr.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Everything looks great! No dangerous files found in this plugin18,320 lines of code in 195 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 156 | 2,742 | 7,222 | 12,865 |
| Markdown | 15 | 1,109 | 0 | 3,538 |
| JSON | 13 | 0 | 0 | 898 |
| C | 1 | 73 | 15 | 477 |
| CSS | 2 | 31 | 16 | 231 |
| JavaScript | 2 | 83 | 60 | 170 |
| XML | 2 | 45 | 78 | 76 |
| YAML | 1 | 7 | 0 | 34 |
| m4 | 1 | 5 | 0 | 14 |
| make | 1 | 4 | 0 | 9 |
| C/C++ Header | 1 | 4 | 12 | 8 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.44 |
| Average class complexity | 12.83 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 134.00 |
| Average method complexity | 2.90 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 77.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 22 | |
| Interfaces | 15 | |
| Traits | 2 | |
| Classes | 110 | |
| ▷ Abstract classes | 2 | 1.82% |
| ▷ Concrete classes | 108 | 98.18% |
| ▷ Final classes | 7 | 6.48% |
| Methods | 846 | |
| ▷ Static methods | 123 | 14.54% |
| ▷ Public methods | 678 | 80.14% |
| ▷ Protected methods | 19 | 2.25% |
| ▷ Private methods | 149 | 17.61% |
| Functions | 193 | |
| ▷ Named functions | 96 | 49.74% |
| ▷ Anonymous functions | 97 | 50.26% |
| Constants | 61 | |
| ▷ Global constants | 7 | 11.48% |
| ▷ Class constants | 54 | 88.52% |
| ▷ Public constants | 54 | 100.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
There were not PNG files found in your plugin