Report - GEO my WP 3.7 - PluginTests.com

Does GEO my WP work with WordPress 5.7 and PHP 7.4.8? A smoke test was performed on 2021-03-10 15:20:34 UTC.

Summary

Errors

33	PHP notices
2	JavaScript exceptions
	All test pages loaded successfully
	No resource errors

Performance

Memory usage: 266.55 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: insignificant.
The plugin didn't make the site noticeably slower.

Environment

WordPress version	5.7
PHP version	7.4.8
MySQL version	8.0.21
PHP memory limit	256M

Plugin Info

Last updated	2025-04-30T08:46:00+00:00
Active installs	4,000+
WordPress.org page	https://wordpress.org/plugins/geo-my-wp/
Badges	Get badge code

Pages 12

Plugins ‹ Test site — WordPress

URL	/wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL	/wp-admin/plugins.php?action=activate&plugin=geo-my-wp%2Fgeo-my-wp.php&plugin_status=all&paged=1&s&_wpnonce=7281d04e72
Aspect	after-activation
HTTP status	200
Load time	1.793 s
Memory usage	3.01 MiB
JS errors	None
Resource errors	None

GEO my WP

URL	/wp-admin/admin.php?page=gmw-extensions
Aspect	menu-item
HTTP status	200
Load time	0.802 s
Memory usage	3.06 MiB
JS errors	`[ { "message": "TypeError: Cannot read property 'country_code' of null\n at /wp-content/plugins/geo-my-wp/assets/js/gmw.core.min.js?ver=3.7:1:14781", "trace": null, "code": null } ]`
Resource errors	None

GEO my WP → Settings

URL	/wp-admin/admin.php?page=gmw-settings
Aspect	menu-item
HTTP status	200
Load time	0.295 s
Memory usage	3.01 MiB
JS errors	`[ { "message": "TypeError: Cannot read property 'country_code' of null\n at /wp-content/plugins/geo-my-wp/assets/js/gmw.core.min.js?ver=3.7:1:14781", "trace": null, "code": null } ]`
Resource errors	None

GEO my WP → Forms

URL	/wp-admin/admin.php?page=gmw-forms
Aspect	menu-item
HTTP status	200
Load time	0.197 s
Memory usage	2.97 MiB
JS errors	None
Resource errors	None

GEO my WP → Import / Export

URL	/wp-admin/admin.php?page=gmw-import-export
Aspect	menu-item
HTTP status	200
Load time	0.195 s
Memory usage	3 MiB
JS errors	None
Resource errors	None

GEO my WP → Import / Export → Forms

URL	/wp-admin/admin.php?page=gmw-import-export&tab=forms
Aspect	menu-item-tab
HTTP status	200
Load time	0.173 s
Memory usage	3 MiB
JS errors	None
Resource errors	None

GEO my WP → Import / Export → Location Tables

URL	/wp-admin/admin.php?page=gmw-import-export&tab=location_tables
Aspect	menu-item-tab
HTTP status	200
Load time	0.247 s
Memory usage	3 MiB
JS errors	None
Resource errors	None

GEO my WP → Tools

URL	/wp-admin/admin.php?page=gmw-tools
Aspect	menu-item
HTTP status	200
Load time	0.206 s
Memory usage	3.4 MiB
JS errors	None
Resource errors	None

GEO my WP → Tools → API Testing

URL	/wp-admin/admin.php?page=gmw-tools&tab=api_testing
Aspect	menu-item-tab
HTTP status	200
Load time	0.338 s
Memory usage	2.98 MiB
JS errors	None
Resource errors	None

GEO my WP → Tools → Uninstall GEO my WP

URL	/wp-admin/admin.php?page=gmw-tools&tab=reset_gmw
Aspect	menu-item-tab
HTTP status	200
Load time	0.181 s
Memory usage	2.98 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.418 s
Memory usage	2.8 MiB
JS errors	None
Resource errors	None

Widgets ‹ Test site — WordPress

URL	/wp-admin/widgets.php
Aspect	new-sidebar-widgets
HTTP status	200
Load time	0.913 s
Memory usage	3.05 MiB
JS errors	None
Resource errors	None

Benchmark

URL	Load time			Memory usage
URL	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.300 s	0.304 s	+0.004 s	2.82 MiB	3.11 MiB	+ 297.35 KiB
/wp-admin/edit.php	0.192 s	0.327 s	+0.135 s	2.86 MiB	3.14 MiB	+ 287.27 KiB
/wp-admin/post-new.php	1.506 s	1.315 s	-0.191 s	5.02 MiB	5.32 MiB	+ 298.95 KiB
/wp-admin/upload.php	0.583 s	0.510 s	-0.073 s	2.7 MiB	2.99 MiB	+ 299.57 KiB
/wp-admin/options-writing.php	0.201 s	0.188 s	-0.013 s	2.71 MiB	2.97 MiB	+ 267.91 KiB
/wp-admin/media-new.php	0.216 s	0.205 s	-0.011 s	2.67 MiB	2.97 MiB	+ 300.11 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.206 s	0.200 s	-0.006 s	2.77 MiB	3 MiB	+ 237.02 KiB
/wp-admin/post-new.php?post_type=page	0.738 s	0.748 s	+0.010 s	5.01 MiB	5.3 MiB	+ 296.73 KiB
/wp-admin/options-discussion.php	0.230 s	0.219 s	-0.011 s	2.67 MiB	2.97 MiB	+ 300.73 KiB
/wp-admin/edit-comments.php	0.228 s	0.230 s	+0.002 s	2.78 MiB	3.03 MiB	+ 261.4 KiB
/	0.280 s	0.330 s	+0.050 s	2.71 MiB	2.79 MiB	+ 84.99 KiB
Average	0.425 s	0.416 s	-0.009 s	3.16 MiB	3.42 MiB	+ 266.55 KiB

Code Statistics

Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.

JavaScript

PHP

CSS

PO File

Language		%	Lines of code	Comment lines	Files
	JavaScript	47.1%	42,501	16,964	29
	PHP	29.7%	26,780	13,967	139
	CSS	12.1%	10,938	960	32
	PO File	9.9%	8,958	8,849	4
	JSON	0.8%	696	0	1
	Markdown	0.2%	173	0	1
	SVG	0.1%	115	0	1
Total			90,161	40,740	207

PHP Code Analysis | More results »

Lines of code	26,146
Total complexity	4,737
Median class complexity	20.5
Median method complexity	2.0
Most complex class	ParseCsv\Csv
Most complex function	GMW_Extensions::output()

Classes	84
Methods	676
Functions	371

Additions

Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.

Database Tables 3

wp_gmw_forms
wp_gmw_locationmeta
wp_gmw_locations

Options `wp_options` 10

gmw_addons_data
gmw_addons_status
gmw_addons_version
gmw_db_version
gmw_extensions_updater
gmw_forms_table_updated
gmw_license_data
gmw_options
gmw_version
widget_gmw_search_form_widget

Sidebar Widgets 1

ID	Name
gmw_search_form_widget	GEO my WP Search Form

PHP Error Log 33 lines

[10-Mar-2021 15:20:52 UTC] PHP Notice:  Trying to access array offset on value of type bool in /wp-content/plugins/geo-my-wp/includes/gmw-enqueue-scripts.php on line 109
[10-Mar-2021 15:20:52 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:52 UTC] PHP Notice:  Trying to access array offset on value of type bool in /wp-content/plugins/geo-my-wp/includes/gmw-enqueue-scripts.php on line 109
[10-Mar-2021 15:20:52 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:53 UTC] PHP Notice:  Trying to access array offset on value of type bool in /wp-content/plugins/geo-my-wp/includes/gmw-enqueue-scripts.php on line 109
[10-Mar-2021 15:20:53 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:54 UTC] PHP Notice:  Trying to access array offset on value of type bool in /wp-content/plugins/geo-my-wp/includes/gmw-enqueue-scripts.php on line 109
[10-Mar-2021 15:20:54 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:55 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:56 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:56 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:56 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:57 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:58 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:58 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:59 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:59 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:59 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:59 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:20:59 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:00 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:00 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:03 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:03 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:04 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:04 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:04 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:06 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:06 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:06 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:07 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:07 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 15:21:08 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313

GEO my WP 3.7