Benchmarks
Plugin footprint 64% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.40MB] [CPU: ▲0.33ms] 75% from 4 tests
Analyzing server-side resources used by GEO Security Suite
It is recommended to improve the following
- CPU: You should keep total CPU usage under 500.00ms (currently 981.70ms on /wp-admin/admin.php?page=plgsggeo_extensions_page)
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.85 ▲0.39 | 47.15 ▲6.85 |
Dashboard /wp-admin | 3.71 ▲0.41 | 54.22 ▼3.72 |
Posts /wp-admin/edit.php | 3.83 ▲0.47 | 58.94 ▲9.38 |
Add New Post /wp-admin/post-new.php | 6.29 ▲0.41 | 94.98 ▼11.18 |
Media Library /wp-admin/upload.php | 3.63 ▲0.41 | 52.19 ▲11.00 |
Front-end protection /wp-admin/admin.php?page=plgsggeo_protection | 3.94 | 51.45 |
Customize & Style /wp-admin/admin.php?page=plgsggeo_protection&tab=3 | 3.83 | 74.39 |
GEO Redirect /wp-admin/admin.php?page=plgsggeo_protection&tab=5 | 3.83 | 54.56 |
Get Full Version /wp-admin/admin.php?page=register_plgsggeo_upgrade_redirect | 3.82 | 39.57 |
Security Extensions /wp-admin/admin.php?page=plgsggeo_extensions_page | 4.06 | 981.70 |
Logs /wp-admin/admin.php?page=plgsggeo_protection&tab=2 | 3.83 | 62.69 |
Settings & Support /wp-admin/admin.php?page=plgsggeo_protection&tab=4 | 3.83 | 51.98 |
Backend protection /wp-admin/admin.php?page=plgsggeo_protection&tab=1 | 3.86 | 50.40 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] 67% from 3 tests
Input-output and database impact of this plugin
Please try to fix the following items
- The plugin illegally modified 69 files (11,420.28KB) outside of "wp-content/plugins/geo-security-suit/" and "wp-content/uploads/"
- (new file) siteguarding_tools.php
- (new file) wp-content/plugins/wp-geo-website-protection/css/index.html
- (modified) .htaccess
- (new file) wp-content/plugins/wp-geo-website-protection/css/themes/basic/assets/fonts/icons.eot
- (new file) wp-content/plugins/wp-geo-website-protection/css/themes/default/assets/fonts/brand-icons.svg
- (new file) wp-content/plugins/wp-geo-website-protection/css/themes/default/assets/fonts/brand-icons.eot
- (new file) wp-content/plugins/wp-geo-website-protection/css/themes/basic/assets/fonts/icons.woff
- (new file) wp-content/plugins/wp-geo-website-protection/css/themes/basic/assets/fonts/icons.ttf
- (new file) wp-content/plugins/wp-geo-website-protection/css/themes/basic/assets/fonts/icons.svg
- (modified) wp-config.php
- ...
Filesystem: 6 new files
Database: 3 new tables, 6 new options
New tables |
---|
wp_plgsggeo_stats |
wp_plgsggeo_config |
wp_plgsggeo_ip |
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
db_upgraded |
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for GEO Security Suite
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,894 ▲94 | 13.74 ▼0.91 | 1.87 ▼0.13 | 35.52 ▼8.79 |
Dashboard /wp-admin | 2,300 ▲94 | 5.24 ▲0.39 | 101.85 ▼10.59 | 83.95 ▲37.07 |
Posts /wp-admin/edit.php | 2,150 ▲61 | 2.38 ▲0.32 | 36.46 ▲0.48 | 35.46 ▲4.80 |
Add New Post /wp-admin/post-new.php | 1,589 ▲56 | 24.35 ▲1.07 | 829.23 ▲125.57 | 42.99 ▼18.74 |
Media Library /wp-admin/upload.php | 1,442 ▲51 | 4.54 ▲0.28 | 100.82 ▼3.12 | 72.36 ▲29.19 |
Front-end protection /wp-admin/admin.php?page=plgsggeo_protection | 2,505 | 2.28 | 38.74 | 178.99 |
Customize & Style /wp-admin/admin.php?page=plgsggeo_protection&tab=3 | 1,358 | 2.38 | 41.42 | 73.27 |
GEO Redirect /wp-admin/admin.php?page=plgsggeo_protection&tab=5 | 8,387 | 2.15 | 47.30 | 244.88 |
Get Full Version /wp-admin/admin.php?page=register_plgsggeo_upgrade_redirect | 2,591 | 4.62 | 82.13 | 79.54 |
Security Extensions /wp-admin/admin.php?page=plgsggeo_extensions_page | 1,646 | 1.93 | 29.73 | 69.95 |
Logs /wp-admin/admin.php?page=plgsggeo_protection&tab=2 | 1,348 | 2.94 | 65.28 | 77.94 |
Settings & Support /wp-admin/admin.php?page=plgsggeo_protection&tab=4 | 1,240 | 2.33 | 43.80 | 56.45 |
Backend protection /wp-admin/admin.php?page=plgsggeo_protection&tab=1 | 2,569 | 2.27 | 35.14 | 71.49 |
Uninstaller [IO: ▲11.15MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- This plugin does not fully uninstall, leaving 3 tables in the database
- wp_plgsggeo_stats
- wp_plgsggeo_config
- wp_plgsggeo_ip
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
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
Please fix the following server-side errors
- > GET request to /wp-admin/admin.php?page=plgsggeo_protection
- > Notice in wp-content/plugins/wp-geo-website-protection/wp-geo-website-protection.php+2692
Constant DIRSEP already defined
SRP 0% from 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
Please fix the following
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/geo-security-suit/siteguarding_tools.php
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/geo-security-suit/geo-security-suit.php:10
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 88% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Screenshots: Please describe screenshot #4 in geo-security-suit/assets to your readme.txt
- Tags: Too many tags (25 tag instead of maximum 10); only the first 5 tags are used in your directory listing
geo-security-suit/geo-security-suit.php Passed 13 tests
The principal PHP file in "GEO Security Suite" v. 1.4 is loaded by WordPress automatically on each request
138 characters long description:
Adds more security for your WordPress website. Blocks unwanted traffic, protects backend page. Blocks specific countries and IP addresses.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Everything looks great! No dangerous files found in this plugin405 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 105 | 37 | 403 |
Pascal | 1 | 0 | 0 | 2 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.45 |
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 | 15 | |
▷ Named functions | 15 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 6 | |
▷ Global constants | 6 | 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
There are no PNG files in this plugin