Does WP DSGVO Tools (GDPR) work with WordPress 5.5.1 and PHP 7.4.8? A smoke test was performed on .
6 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 1.72 MiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
1.065 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.5.1 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 20,000+ |
WordPress.org page | https://wordpress.org/plugins/shapepress-dsgvo/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=shapepress-dsgvo%2Fsp-dsgvo.php&plugin_status=all&paged=1&s&_wpnonce=1c1d7fab51 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 3.035 s |
Memory usage | 6.73 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=sp-dsgvo |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 4.980 s |
Memory usage | 4.44 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=sp-dsgvo&tab=cookie-notice |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 3.331 s |
Memory usage | 4.44 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=sp-dsgvo&tab=operator |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 4.730 s |
Memory usage | 4.44 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=sp-dsgvo&tab=page-basics |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 3.305 s |
Memory usage | 4.44 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=sp-dsgvo&tab=tagmanager-integrations |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 2.840 s |
Memory usage | 4.44 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=sp-dsgvo&tab=statistic-integrations |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 2.866 s |
Memory usage | 4.44 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=sp-dsgvo&tab=targeting-integrations |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 3.378 s |
Memory usage | 4.44 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=sp-dsgvo&tab=embeddings-integrations |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 3.105 s |
Memory usage | 4.96 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=sp-dsgvo&tab=subject-access-request |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 3.192 s |
Memory usage | 4.44 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=sp-dsgvo&tab=super-unsubscribe |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 3.404 s |
Memory usage | 4.44 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=sp-dsgvo&tab=webinars |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 4.573 s |
Memory usage | 4.44 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=sp-dsgvo&tab=info |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 2.740 s |
Memory usage | 4.44 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 1.389 s |
Memory usage | 4.78 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.613 s | 1.234 s | +0.621 s | 2.75 MiB | 4.44 MiB | + 1.69 MiB |
/wp-admin/edit.php | 0.319 s | 1.828 s | +1.509 s | 2.8 MiB | 4.44 MiB | + 1.65 MiB |
/wp-admin/post-new.php | 2.213 s | 4.305 s | +2.092 s | 4.54 MiB | 5.79 MiB | + 1.24 MiB |
/wp-admin/upload.php | 0.640 s | 2.104 s | +1.464 s | 2.63 MiB | 4.44 MiB | + 1.81 MiB |
/wp-admin/options-writing.php | 0.216 s | 1.476 s | +1.260 s | 2.64 MiB | 4.44 MiB | + 1.8 MiB |
/wp-admin/media-new.php | 0.247 s | 0.787 s | +0.540 s | 2.6 MiB | 4.44 MiB | + 1.84 MiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.237 s | 0.781 s | +0.544 s | 2.64 MiB | 4.44 MiB | + 1.8 MiB |
/wp-admin/post-new.php?post_type=page | 1.736 s | 2.977 s | +1.241 s | 4.53 MiB | 5.77 MiB | + 1.24 MiB |
/wp-admin/options-discussion.php | 0.496 s | 1.850 s | +1.354 s | 2.61 MiB | 4.44 MiB | + 1.83 MiB |
/wp-admin/edit-comments.php | 0.243 s | 0.805 s | +0.562 s | 2.65 MiB | 4.44 MiB | + 1.79 MiB |
/ | 0.910 s | 1.436 s | +0.526 s | 2.56 MiB | 4.78 MiB | + 2.22 MiB |
Average | 0.715 s | 1.780 s | +1.065 s | 3 MiB | 4.72 MiB | + 1.72 MiB |
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
7ID | Name |
---|---|
subjectaccessrequest | Posts |
[15-Sep-2020 08:21:53 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>legalweb/v1/lwTextEndpoint</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5225
[15-Sep-2020 08:21:54 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>legalweb/v1/lwTextEndpoint</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5225
[15-Sep-2020 08:21:55 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>legalweb/v1/lwTextEndpoint</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5225
[15-Sep-2020 08:22:02 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>legalweb/v1/lwTextEndpoint</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5225
[15-Sep-2020 08:22:03 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>legalweb/v1/lwTextEndpoint</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5225
[15-Sep-2020 08:22:04 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>legalweb/v1/lwTextEndpoint</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5225