Landingi Landing pages 2.1.1

Does Landingi Landing pages work with WordPress 5.3.2 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: 343.03 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 version5.3.2
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=05fbd4a2e2
Aspect after-activation
HTTP status 200
Load time 0.618 s
Memory usage 3.91 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 2.067 s
Memory usage 4.84 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.222 s
Memory usage 3.93 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.158 s
Memory usage 4.16 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.265 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.308 s0.247 s-0.061 s3.61 MiB3.97 MiB+ 367.34 KiB
/wp-admin/edit.php0.259 s0.230 s-0.029 s3.64 MiB3.99 MiB+ 353.64 KiB
/wp-admin/post-new.php1.227 s1.602 s+0.375 s5.36 MiB5.71 MiB+ 354.88 KiB
/wp-admin/upload.php0.501 s0.514 s+0.013 s3.48 MiB3.83 MiB+ 359.98 KiB
/wp-admin/options-writing.php0.335 s0.189 s-0.146 s3.56 MiB3.82 MiB+ 266.54 KiB
/wp-admin/media-new.php0.235 s0.230 s-0.005 s3.46 MiB3.81 MiB+ 360.15 KiB
/wp-admin/edit-tags.php?taxonomy=category0.185 s0.217 s+0.032 s3.56 MiB3.91 MiB+ 361.05 KiB
/wp-admin/post-new.php?post_type=page0.990 s1.063 s+0.073 s5.35 MiB5.7 MiB+ 355.17 KiB
/wp-admin/options-discussion.php0.293 s0.269 s-0.024 s3.46 MiB3.82 MiB+ 360.46 KiB
/wp-admin/edit-comments.php0.223 s0.251 s+0.028 s3.57 MiB3.92 MiB+ 360 KiB
/0.366 s0.246 s-0.120 s3.32 MiB3.58 MiB+ 274.12 KiB
Average 0.447 s0.460 s+0.012 s3.85 MiB4.19 MiB+ 343.03 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

[20-Jan-2020 11:52:27 UTC] PHP Warning:  Cannot modify header information - headers already sent by (output started at /wp-includes/script-loader.php:2585) in /wp-content/plugins/landingi-landing-pages/src/Framework/Http/Response.php on line 45
[20-Jan-2020 11:52:28 UTC] PHP Warning:  Cannot modify header information - headers already sent by (output started at /wp-includes/script-loader.php:2585) 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