Landingi Landing pages 2.1.7

Does Landingi Landing pages work with WordPress 5.4 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: 364.74 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.4
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=5f473cbbf4
Aspect after-activation
HTTP status 200
Load time 0.742 s
Memory usage 3.93 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.112 s
Memory usage 4.89 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.297 s
Memory usage 3.95 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.199 s
Memory usage 4.18 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.337 s
Memory usage 3.66 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.311 s0.264 s-0.047 s3.64 MiB4 MiB+ 368.34 KiB
/wp-admin/edit.php0.228 s0.226 s-0.002 s3.67 MiB4.01 MiB+ 354.59 KiB
/wp-admin/post-new.php1.228 s1.654 s+0.426 s5.43 MiB5.78 MiB+ 355.83 KiB
/wp-admin/upload.php0.461 s0.477 s+0.016 s3.5 MiB3.92 MiB+ 424.98 KiB
/wp-admin/options-writing.php0.418 s0.190 s-0.228 s3.58 MiB3.9 MiB+ 331.54 KiB
/wp-admin/media-new.php0.215 s0.213 s-0.002 s3.48 MiB3.9 MiB+ 425.15 KiB
/wp-admin/edit-tags.php?taxonomy=category0.187 s0.231 s+0.044 s3.58 MiB3.94 MiB+ 362.05 KiB
/wp-admin/post-new.php?post_type=page1.120 s1.156 s+0.036 s5.42 MiB5.78 MiB+ 368.17 KiB
/wp-admin/options-discussion.php0.426 s0.321 s-0.105 s3.48 MiB3.9 MiB+ 425.46 KiB
/wp-admin/edit-comments.php0.217 s0.227 s+0.010 s3.59 MiB3.94 MiB+ 361 KiB
/0.376 s0.244 s-0.132 s3.43 MiB3.66 MiB+ 235 KiB
Average 0.472 s0.473 s+0.001 s3.89 MiB4.25 MiB+ 364.74 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-Apr-2020 07:20:03 UTC] PHP Warning:  Cannot modify header information - headers already sent by (output started at /wp-includes/script-loader.php:2211) in /wp-content/plugins/landingi-landing-pages/src/Framework/Http/Response.php on line 45
[15-Apr-2020 07:20:04 UTC] PHP Warning:  Cannot modify header information - headers already sent by (output started at /wp-includes/script-loader.php:2209) 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