Does Gutenberg work with WordPress 5.2.2 and PHP 7.2.16? A smoke test was performed on .
6 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 136.65 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.092 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.2.2 |
---|---|
PHP version | 7.2.16 |
MySQL version | 8.0.15 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 300,000+ |
WordPress.org page | https://wordpress.org/plugins/gutenberg/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=gutenberg%2Fgutenberg.php&plugin_status=all&paged=1&s&_wpnonce=5e40d6d74a |
Aspect | after-activation |
HTTP status | 200 |
Load time | 1.064 s |
Memory usage | 3.65 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php?gutenberg-demo |
---|---|
Requested URL | /wp-admin/admin.php?page=gutenberg |
Aspect | menu-item |
HTTP status | 200 |
Load time | 4.135 s |
Memory usage | 5.63 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=gutenberg-widgets |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.527 s |
Memory usage | 3.63 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.233 s |
Memory usage | 3.32 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.342 s | 0.296 s | -0.046 s | 3.6 MiB | 3.7 MiB | + 102.72 KiB |
/wp-admin/edit.php | 0.274 s | 0.444 s | +0.170 s | 3.63 MiB | 3.73 MiB | + 102.28 KiB |
/wp-admin/post-new.php | 1.316 s | 2.035 s | +0.719 s | 5.27 MiB | 5.62 MiB | + 354.57 KiB |
/wp-admin/upload.php | 0.813 s | 0.442 s | -0.371 s | 3.46 MiB | 3.56 MiB | + 99.09 KiB |
/wp-admin/options-writing.php | 0.234 s | 0.186 s | -0.048 s | 3.55 MiB | 3.55 MiB | + 6 KiB |
/wp-admin/media-new.php | 0.229 s | 0.358 s | +0.129 s | 3.45 MiB | 3.54 MiB | + 99.57 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.237 s | 0.237 s | +0.000 s | 3.48 MiB | 3.65 MiB | + 165.41 KiB |
/wp-admin/post-new.php?post_type=page | 1.222 s | 1.976 s | +0.754 s | 5.25 MiB | 5.6 MiB | + 355.78 KiB |
/wp-admin/options-discussion.php | 0.543 s | 0.239 s | -0.304 s | 3.45 MiB | 3.55 MiB | + 99.88 KiB |
/wp-admin/edit-comments.php | 0.248 s | 0.217 s | -0.031 s | 3.55 MiB | 3.65 MiB | + 99.11 KiB |
/ | 0.352 s | 0.394 s | +0.042 s | 3.3 MiB | 3.32 MiB | + 18.73 KiB |
Average | 0.528 s | 0.620 s | +0.092 s | 3.82 MiB | 3.95 MiB | + 136.65 KiB |
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.
ID | Name |
---|---|
wp_area | Block Area (Experimental) |
[26-Jun-2019 13:09:59 UTC] PHP Notice: the_widget was called <strong>incorrectly</strong>. Widgets need to be registered using <code>register_widget()</code>, before they can be displayed. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 4.9.0.) in /wp-includes/functions.php on line 4773
[26-Jun-2019 13:09:59 UTC] PHP Notice: the_widget was called <strong>incorrectly</strong>. Widgets need to be registered using <code>register_widget()</code>, before they can be displayed. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 4.9.0.) in /wp-includes/functions.php on line 4773
[26-Jun-2019 13:09:59 UTC] PHP Notice: the_widget was called <strong>incorrectly</strong>. Widgets need to be registered using <code>register_widget()</code>, before they can be displayed. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 4.9.0.) in /wp-includes/functions.php on line 4773
[26-Jun-2019 13:09:59 UTC] PHP Notice: the_widget was called <strong>incorrectly</strong>. Widgets need to be registered using <code>register_widget()</code>, before they can be displayed. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 4.9.0.) in /wp-includes/functions.php on line 4773
[26-Jun-2019 13:09:59 UTC] PHP Notice: the_widget was called <strong>incorrectly</strong>. Widgets need to be registered using <code>register_widget()</code>, before they can be displayed. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 4.9.0.) in /wp-includes/functions.php on line 4773
[26-Jun-2019 13:09:59 UTC] PHP Notice: the_widget was called <strong>incorrectly</strong>. Widgets need to be registered using <code>register_widget()</code>, before they can be displayed. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 4.9.0.) in /wp-includes/functions.php on line 4773