Landingi Landing pages 1.2.9

Does Landingi Landing pages work with WordPress 5.3 and PHP 7.2.16? A smoke test was performed on .

Summary

Errors
2PHP warnings
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

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

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

Environment
WordPress version5.3
PHP version7.2.16
MySQL version8.0.15
PHP memory limit256M
Plugin Info
Last updated
Active installs 3,000+
WordPress.org page https://wordpress.org/plugins/landingi-landing-pages/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 5

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL /wp-admin/plugins.php?action=activate&plugin=landingi-landing-pages%2Flandingi-plugin.php&plugin_status=all&paged=1&s&_wpnonce=2fdb87a83e
Aspect after-activation
HTTP status 200
Load time 0.432 s
Memory usage 3.85 MiB
JS errors None
Resource errors None

Landingi

Page screenshot: Landingi
URL /wp-admin/admin.php?page=landingi
Aspect menu-item
HTTP status 200
Load time 1.043 s
Memory usage 4.92 MiB
JS errors None
Resource errors None

Landingi → Imported Landings

Page screenshot: Landingi → Imported Landings
URL /wp-admin/edit.php?post_type=landing
Aspect menu-item
HTTP status 200
Load time 0.424 s
Memory usage 3.92 MiB
JS errors None
Resource errors None

Landingi → Settings

Page screenshot: Landingi → Settings
URL /wp-admin/admin.php?page=landingi_settings
Aspect menu-item
HTTP status 200
Load time 0.191 s
Memory usage 4.09 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.263 s
Memory usage 3.58 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.336 s0.357 s+0.021 s3.62 MiB3.97 MiB+ 363.23 KiB
/wp-admin/edit.php0.243 s0.420 s+0.177 s3.65 MiB3.99 MiB+ 349.53 KiB
/wp-admin/post-new.php1.179 s1.221 s+0.042 s5.36 MiB5.71 MiB+ 358.77 KiB
/wp-admin/upload.php0.431 s0.534 s+0.103 s3.48 MiB3.83 MiB+ 355.24 KiB
/wp-admin/options-writing.php0.154 s0.229 s+0.075 s3.56 MiB3.82 MiB+ 262.43 KiB
/wp-admin/media-new.php0.278 s0.355 s+0.077 s3.46 MiB3.81 MiB+ 356.04 KiB
/wp-admin/edit-tags.php?taxonomy=category0.250 s0.227 s-0.023 s3.56 MiB3.85 MiB+ 292.95 KiB
/wp-admin/post-new.php?post_type=page1.042 s1.123 s+0.081 s5.34 MiB5.63 MiB+ 295.06 KiB
/wp-admin/options-discussion.php0.231 s0.252 s+0.021 s3.46 MiB3.81 MiB+ 356.35 KiB
/wp-admin/edit-comments.php0.315 s0.333 s+0.018 s3.57 MiB3.92 MiB+ 355.89 KiB
/0.331 s0.284 s-0.047 s3.32 MiB3.58 MiB+ 270.01 KiB
Average 0.435 s0.485 s+0.050 s3.85 MiB4.17 MiB+ 328.68 KiB

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 1

Custom Post Types 1

ID Name
landingImported Landings

PHP Error Log 2 lines

[15-Nov-2019 17:40:45 UTC] PHP Warning:  Cannot modify header information - headers already sent by (output started at /wp-includes/script-loader.php:2582) in /wp-content/plugins/landingi-landing-pages/src/Framework/Http/Response.php on line 45
[15-Nov-2019 17:40:46 UTC] PHP Warning:  Cannot modify header information - headers already sent by (output started at /wp-includes/script-loader.php:2582) in /wp-content/plugins/landingi-landing-pages/src/Framework/Http/Response.php on line 45
See also: All tests for this plugin, How to Hide Landingi Landing pages Admin Menus