Report - Travelpayouts 1.0.12

Does Travelpayouts work with WordPress 5.7 and PHP 7.4.8? A smoke test was performed on 2021-03-10 16:49:24 UTC.

Summary

Errors

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

Performance

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

Page speed impact: 1.199 seconds
The average page load time increased by this amount after activating the plugin.

Environment

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

Plugin Info

Last updated	2025-05-27T11:21:00+00:00
Active installs	8,000+
WordPress.org page	https://wordpress.org/plugins/travelpayouts/
Badges	Get badge code

Pages 10

Plugins ‹ Test site — WordPress

URL	/wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL	/wp-admin/plugins.php?action=activate&plugin=travelpayouts%2Ftravelpayouts.php&plugin_status=all&paged=1&s&_wpnonce=fb6b298ca0
Aspect	after-activation
HTTP status	200
Load time	2.661 s
Memory usage	5.96 MiB
JS errors	None
Resource errors	None

Settings → Travelpayouts

URL	/wp-admin/options-general.php?page=travelpayouts_landing_page
Aspect	menu-item
HTTP status	200
Load time	0.949 s
Memory usage	5.78 MiB
JS errors	None
Resource errors	None

Travelpayouts

URL	/wp-admin/admin.php?page=travelpayouts_options&tab=1
Aspect	menu-item
HTTP status	200
Load time	2.422 s
Memory usage	9.78 MiB
JS errors	None
Resource errors	None

Travelpayouts → Widgets

URL	/wp-admin/admin.php?page=travelpayouts_options&tab=5
Aspect	menu-item
HTTP status	200
Load time	1.543 s
Memory usage	9.71 MiB
JS errors	None
Resource errors	None

Travelpayouts → Search forms

URL	/wp-admin/admin.php?page=travelpayouts_options&tab=8
Aspect	menu-item
HTTP status	200
Load time	1.463 s
Memory usage	9.71 MiB
JS errors	None
Resource errors	None

Travelpayouts → Account

URL	/wp-admin/admin.php?page=travelpayouts_options&tab=9
Aspect	menu-item
HTTP status	200
Load time	2.080 s
Memory usage	9.71 MiB
JS errors	None
Resource errors	None

Travelpayouts → Settings

URL	/wp-admin/admin.php?page=travelpayouts_options&tab=10
Aspect	menu-item
HTTP status	200
Load time	1.184 s
Memory usage	9.71 MiB
JS errors	None
Resource errors	None

Travelpayouts → Help

URL	/wp-admin/admin.php?page=travelpayouts_options&tab=11
Aspect	menu-item
HTTP status	200
Load time	1.054 s
Memory usage	9.71 MiB
JS errors	None
Resource errors	None

Travelpayouts → Import / Export

URL	/wp-admin/admin.php?page=travelpayouts_options&tab=12
Aspect	menu-item
HTTP status	200
Load time	1.330 s
Memory usage	9.71 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.570 s
Memory usage	8.01 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.305 s	1.870 s	+1.565 s	2.82 MiB	5.51 MiB	+ 2.69 MiB
/wp-admin/edit.php	0.193 s	0.882 s	+0.689 s	2.86 MiB	5.6 MiB	+ 2.74 MiB
/wp-admin/post-new.php	0.970 s	4.744 s	+3.774 s	5.02 MiB	8.07 MiB	+ 3.05 MiB
/wp-admin/upload.php	0.495 s	1.406 s	+0.911 s	2.7 MiB	5.45 MiB	+ 2.76 MiB
/wp-admin/options-writing.php	0.164 s	0.881 s	+0.717 s	2.71 MiB	5.43 MiB	+ 2.72 MiB
/wp-admin/media-new.php	0.241 s	0.475 s	+0.234 s	2.67 MiB	5.43 MiB	+ 2.76 MiB
/wp-admin/edit-tags.php?taxonomy=category	0.209 s	0.421 s	+0.212 s	2.77 MiB	5.47 MiB	+ 2.7 MiB
/wp-admin/post-new.php?post_type=page	1.170 s	4.427 s	+3.257 s	5.01 MiB	8.06 MiB	+ 3.05 MiB
/wp-admin/options-discussion.php	0.357 s	1.268 s	+0.911 s	2.67 MiB	5.43 MiB	+ 2.76 MiB
/wp-admin/edit-comments.php	0.256 s	0.753 s	+0.497 s	2.78 MiB	5.47 MiB	+ 2.7 MiB
/	0.285 s	0.705 s	+0.420 s	2.71 MiB	8.01 MiB	+ 5.3 MiB
Average	0.422 s	1.621 s	+1.199 s	3.16 MiB	6.18 MiB	+ 3.02 MiB

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.

PHP

CSS

YAML

Language		%	Lines of code	Comment lines	Files
	PHP	66.2%	35,349	13,393	437
	CSS	15.5%	8,262	154	29
	YAML	8.9%	4,768	0	30
	JavaScript	5.3%	2,822	95	57
	PO File	2.1%	1,144	672	1
	SVG	1.8%	954	0	15
	Markdown	0.1%	43	0	2
	Sass	0.1%	35	0	3
	JSON	0.0%	2	0	2
Total			53,379	14,314	576

PHP Code Analysis | More results »

Lines of code	34,682
Total complexity	6,769
Median class complexity	5.0
Median method complexity	1.0
Most complex class	Redux_Travelpayouts
Most complex function	Redux_Travelpayouts_Options_Constructor::register()

Classes	393
Methods	2,349
Functions	7

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.

Options `wp_options` 4

travelpayouts_admin_settings
travelpayouts_admin_settings-transients
travelpayouts_notices
travelpayouts_version

PHP Error Log 24 lines

[10-Mar-2021 16:49:42 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 16:49:43 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 16:49:45 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 16:49:46 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 16:49:49 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 16:49:51 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 16:49: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 16:49: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 16:49: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 16:49: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 16:50:01 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 16:50:01 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 16:50: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 16:50:05 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 16:50:10 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 16:50:11 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 16:50:11 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 16:50:12 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 16:50:13 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 16:50:18 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 16:50:18 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 16:50:19 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 16:50:20 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 16:50:21 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

Travelpayouts 1.0.12