Does Lead Form Builder work with WordPress 6.6.1 and PHP 8.1.12? A smoke test was performed on .
1 | PHP notices |
1 | JavaScript exceptions |
All test pages loaded successfully | |
No resource errors |
Memory usage: 101.31 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.
WordPress version | 6.6.1 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 10,000+ |
WordPress.org page | https://wordpress.org/plugins/lead-form-builder/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=lead-form-builder%2Flead-form-builder.php&plugin_status=all&paged=1&s&_wpnonce=c129914d98 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.365 s |
Memory usage | 3.57 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=themehunk-plugins |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.454 s |
Memory usage | 3.54 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wplf-plugin-menu |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.665 s |
Memory usage | 3.54 MiB |
JS errors |
|
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.230 s |
Memory usage | 3.47 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 2.616 s |
Memory usage | 5.69 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.338 s | 0.344 s | +0.006 s | 3.47 MiB | 3.55 MiB | + 81.23 KiB |
/wp-admin/edit.php | 0.212 s | 0.209 s | -0.003 s | 3.54 MiB | 3.62 MiB | + 82.95 KiB |
/wp-admin/post-new.php | 0.813 s | 0.675 s | -0.138 s | 5.75 MiB | 5.91 MiB | + 157.18 KiB |
/wp-admin/upload.php | 0.691 s | 0.610 s | -0.081 s | 3.49 MiB | 3.55 MiB | + 65.55 KiB |
/wp-admin/options-writing.php | 0.208 s | 0.292 s | +0.084 s | 3.41 MiB | 3.54 MiB | + 128.36 KiB |
/wp-admin/media-new.php | 0.299 s | 0.224 s | -0.075 s | 3.4 MiB | 3.53 MiB | + 141.73 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.187 s | 0.207 s | +0.020 s | 3.47 MiB | 3.56 MiB | + 88.41 KiB |
/wp-admin/post-new.php?post_type=page | 0.622 s | 0.633 s | +0.011 s | 5.75 MiB | 5.9 MiB | + 152.81 KiB |
/wp-admin/options-discussion.php | 0.254 s | 0.279 s | +0.025 s | 3.41 MiB | 3.53 MiB | + 130.05 KiB |
/wp-admin/edit-comments.php | 0.226 s | 0.246 s | +0.020 s | 3.49 MiB | 3.55 MiB | + 65.55 KiB |
/ | 0.319 s | 0.232 s | -0.087 s | 3.45 MiB | 3.47 MiB | + 20.64 KiB |
Average | 0.379 s | 0.359 s | -0.020 s | 3.88 MiB | 3.97 MiB | + 101.31 KiB |
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.
Language | % | Lines of code | Comment lines | Files | |
---|---|---|---|---|---|
PHP | 36.1% | 4,807 | 323 | 32 | |
CSS | 26.8% | 3,569 | 126 | 8 | |
SVG | 24.2% | 3,219 | 11 | 13 | |
JavaScript | 12.5% | 1,664 | 652 | 7 | |
JSON | 0.3% | 41 | 0 | 1 | |
Total | 13,300 | 1,112 | 61 |
Lines of code | 4,405 |
---|---|
Total complexity | 611 |
Median class complexity | 19.0 |
Median method complexity | 1.0 |
Most complex class | LFB_Front_end_FORMS |
Most complex function | LFB_Front_end_FORMS::lfb_show_front_end_forms() |
Classes | 14 |
---|---|
Methods | 126 |
Functions | 37 |
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.
wp_options
1ID | Name |
---|---|
lfb-form-builder | Lead Form Builder |
[25-Jul-2024 07:01:07 UTC] PHP Notice: Function wp_enqueue_script() was called <strong>incorrectly</strong>. "wp-editor" script should not be enqueued together with the new widgets editor (wp-edit-widgets or wp-customize-widgets). Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.8.0.) in /wp-includes/functions.php on line 6085