Does MainWP Child work with WordPress 6.9.1 and PHP 8.1.12? A smoke test was performed on .
| 1 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Memory usage: 273.69 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.9.1 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
| Last updated | |
|---|---|
| Active installs | 700,000+ |
| WordPress.org page | https://wordpress.org/plugins/mainwp-child/ |
| Badges |
|
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=mainwp-child%2Fmainwp-child.php&plugin_status=all&paged=1&s&_wpnonce=add4088b15 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.564 s |
| Memory usage | 5.51 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/options-general.php?page=mainwp_child_tab |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 1.180 s |
| Memory usage | 4.19 MiB |
| JS errors | None |
| Resource errors | None |
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.300 s |
| Memory usage | 4.29 MiB |
| JS errors | None |
| Resource errors | None |
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.545 s | 0.385 s | -0.160 s | 3.78 MiB | 4.11 MiB | + 343.13 KiB |
| /wp-admin/edit.php | 0.862 s | 0.343 s | -0.519 s | 3.78 MiB | 4.1 MiB | + 323.84 KiB |
| /wp-admin/post-new.php | 1.299 s | 1.268 s | -0.031 s | 6.31 MiB | 6.63 MiB | + 333.14 KiB |
| /wp-admin/upload.php | 0.479 s | 0.999 s | +0.520 s | 3.74 MiB | 3.98 MiB | + 246.76 KiB |
| /wp-admin/options-writing.php | 0.332 s | 0.419 s | +0.087 s | 3.71 MiB | 3.95 MiB | + 248.29 KiB |
| /wp-admin/media-new.php | 0.523 s | 0.366 s | -0.157 s | 3.7 MiB | 3.95 MiB | + 256.48 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.339 s | 0.320 s | -0.019 s | 3.72 MiB | 3.97 MiB | + 261.75 KiB |
| /wp-admin/post-new.php?post_type=page | 0.975 s | 0.952 s | -0.023 s | 6.3 MiB | 6.61 MiB | + 323.52 KiB |
| /wp-admin/options-discussion.php | 0.395 s | 0.446 s | +0.051 s | 3.71 MiB | 3.95 MiB | + 244.16 KiB |
| /wp-admin/edit-comments.php | 0.793 s | 0.388 s | -0.405 s | 3.73 MiB | 3.97 MiB | + 244.38 KiB |
| / | 0.391 s | 0.258 s | -0.133 s | 4.11 MiB | 4.29 MiB | + 185.09 KiB |
| Average | 0.630 s | 0.559 s | -0.072 s | 4.23 MiB | 4.5 MiB | + 273.69 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 | 82.8% | 43,543 | 19,843 | 97 | |
| PO File | 17.2% | 9,023 | 4,470 | 4 | |
| JSON | 0.0% | 6 | 0 | 1 | |
| Total | 52,572 | 24,313 | 102 | ||
| Lines of code | 42,940 |
|---|---|
| Total complexity | 11,593 |
| Median class complexity | 71.0 |
| Median method complexity | 3.0 |
| Most complex class | MainWP_Child_Updraft_Plus_Backups |
| Most complex function | MainWP_Child_Wordfence::get_diagnostics() |
| Classes | 97 |
|---|---|
| Methods | 1,843 |
| Functions | 17 |
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 13wp_usermeta 1[03-Mar-2026 16:44:46 UTC] PHP Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>mainwp-child</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6131