Report - Quentn WP 1.1.3 - PluginTests.com

Does Quentn WP work with WordPress 5.6 and PHP 7.4.8? A smoke test was performed on 2020-12-13 23:05:41 UTC.

Summary

Errors

5	PHP warnings
18	PHP notices
	No JavaScript exceptions
	All test pages loaded successfully
	No resource errors

Performance

Memory usage: 169.65 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 version	5.6
PHP version	7.4.8
MySQL version	8.0.21
PHP memory limit	256M

Plugin Info

Last updated	2026-04-14T18:23:00+00:00
Active installs	500+
WordPress.org page	https://wordpress.org/plugins/quentn-wp/
Badges	Get badge code

Pages 8

Plugins ‹ Test site — WordPress

URL	/wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL	/wp-admin/plugins.php?action=activate&plugin=quentn-wp%2Fquentn-wp.php&plugin_status=all&paged=1&s&_wpnonce=a84e71ce44
Aspect	after-activation
HTTP status	200
Load time	1.736 s
Memory usage	2.88 MiB
JS errors	None
Resource errors	None

Quentn

URL	/wp-admin/admin.php?page=quentn-dashboard
Aspect	menu-item
HTTP status	200
Load time	0.442 s
Memory usage	2.89 MiB
JS errors	None
Resource errors	None

Quentn → Roles

URL	/wp-admin/admin.php?page=quentn-dashboard&tab=quentn_tags_selection
Aspect	menu-item-tab
HTTP status	200
Load time	0.214 s
Memory usage	2.81 MiB
JS errors	None
Resource errors	None

Quentn → Web Tracking

URL	/wp-admin/admin.php?page=quentn-dashboard&tab=quentn_web_tracking_tab
Aspect	menu-item-tab
HTTP status	200
Load time	0.207 s
Memory usage	2.81 MiB
JS errors	None
Resource errors	None

Quentn → Misc

URL	/wp-admin/admin.php?page=quentn-dashboard&tab=quentn_settings
Aspect	menu-item-tab
HTTP status	200
Load time	0.178 s
Memory usage	2.85 MiB
JS errors	None
Resource errors	None

Quentn → Access Restrictions

URL	/wp-admin/admin.php?page=quentn-access-pages-restrictions
Aspect	menu-item
HTTP status	200
Load time	0.190 s
Memory usage	2.87 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.297 s
Memory usage	2.9 MiB
JS errors	None
Resource errors	None

Add New Page ‹ Test site — WordPress

URL	/wp-admin/post-new.php?post_type=page
Aspect	new-meta-boxes
HTTP status	200
Load time	0.869 s
Memory usage	5.27 MiB
JS errors	None
Resource errors	None

Benchmark

URL	Load time			Memory usage
URL	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.267 s	0.403 s	+0.136 s	2.79 MiB	2.94 MiB	+ 152.82 KiB
/wp-admin/edit.php	0.186 s	0.221 s	+0.035 s	2.84 MiB	2.97 MiB	+ 134.54 KiB
/wp-admin/post-new.php	0.873 s	1.213 s	+0.340 s	4.93 MiB	5.27 MiB	+ 342.88 KiB
/wp-admin/upload.php	0.467 s	0.458 s	-0.009 s	2.67 MiB	2.84 MiB	+ 179.7 KiB
/wp-admin/options-writing.php	0.159 s	0.181 s	+0.022 s	2.68 MiB	2.76 MiB	+ 83.59 KiB
/wp-admin/media-new.php	0.222 s	0.214 s	-0.008 s	2.64 MiB	2.76 MiB	+ 114.59 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.188 s	0.204 s	+0.016 s	2.68 MiB	2.87 MiB	+ 196.75 KiB
/wp-admin/post-new.php?post_type=page	1.104 s	0.834 s	-0.270 s	4.92 MiB	5.26 MiB	+ 346 KiB
/wp-admin/options-discussion.php	0.304 s	0.272 s	-0.032 s	2.65 MiB	2.78 MiB	+ 132.09 KiB
/wp-admin/edit-comments.php	0.232 s	0.220 s	-0.012 s	2.75 MiB	2.88 MiB	+ 131.44 KiB
/	0.258 s	0.228 s	-0.030 s	2.67 MiB	2.72 MiB	+ 51.78 KiB
Average	0.387 s	0.404 s	+0.017 s	3.11 MiB	3.28 MiB	+ 169.65 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.

Database Tables 2

wp_qntn_restrictions
wp_qntn_user_data

Options `wp_options` 2

quentn_db_version
quentn_unique_id

Meta Boxes

{
    "page": {
        "quentn-access-restriction-meta-box": {
            "title": "Quentn Page Restriction",
            "context": "advanced"
        }
    }
}

PHP Error Log 23 lines

[13-Dec-2020 23:05:58 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[13-Dec-2020 23:05:58 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[13-Dec-2020 23:05:58 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[13-Dec-2020 23:05:58 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[13-Dec-2020 23:05:58 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[13-Dec-2020 23:06:02 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:02 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:02 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:02 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:02 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:02 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:05 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:05 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:05 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:05 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:05 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:05 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:08 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:08 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:08 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:08 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:08 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311
[13-Dec-2020 23:06:08 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5311

Quentn WP 1.1.3