Report - Quentn WP 1.1.4 - PluginTests.com

Does Quentn WP work with WordPress 5.6.2 and PHP 7.4.8? A smoke test was performed on 2021-02-26 12:47:35 UTC.

Summary

Errors

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

Performance

Memory usage: 174.71 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.2
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=c9a792a9e8
Aspect	after-activation
HTTP status	200
Load time	2.135 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.449 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.209 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.180 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.199 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.179 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.242 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.919 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.257 s	0.275 s	+0.018 s	2.79 MiB	2.94 MiB	+ 152.82 KiB
/wp-admin/edit.php	0.178 s	0.203 s	+0.025 s	2.84 MiB	2.97 MiB	+ 134.54 KiB
/wp-admin/post-new.php	0.841 s	1.398 s	+0.557 s	4.93 MiB	5.27 MiB	+ 342.88 KiB
/wp-admin/upload.php	0.490 s	0.439 s	-0.051 s	2.67 MiB	2.84 MiB	+ 179.7 KiB
/wp-admin/options-writing.php	0.162 s	0.192 s	+0.030 s	2.68 MiB	2.76 MiB	+ 83.59 KiB
/wp-admin/media-new.php	0.312 s	0.198 s	-0.114 s	2.64 MiB	2.76 MiB	+ 114.59 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.219 s	0.194 s	-0.025 s	2.68 MiB	2.87 MiB	+ 196.75 KiB
/wp-admin/post-new.php?post_type=page	1.090 s	0.824 s	-0.266 s	4.92 MiB	5.26 MiB	+ 346 KiB
/wp-admin/options-discussion.php	0.250 s	0.236 s	-0.014 s	2.65 MiB	2.78 MiB	+ 132.09 KiB
/wp-admin/edit-comments.php	0.231 s	0.253 s	+0.022 s	2.75 MiB	2.88 MiB	+ 131.44 KiB
/	0.252 s	0.258 s	+0.006 s	2.61 MiB	2.72 MiB	+ 107.46 KiB
Average	0.389 s	0.406 s	+0.017 s	3.11 MiB	3.28 MiB	+ 174.71 KiB

Code Statistics

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.

PHP

JavaScript

CSS

Language		%	Lines of code	Comment lines	Files
	PHP	58.8%	3,688	2,175	31
	JavaScript	20.1%	1,263	69	9
	CSS	11.0%	692	23	7
	PO File	4.8%	299	152	1
	SVG	4.6%	288	0	1
	Markdown	0.3%	21	0	1
	JSON	0.2%	12	0	1
	XML	0.1%	9	0	1
Total			6,272	2,419	52

PHP Code Analysis | More results »

Lines of code	3,459
Total complexity	778
Median class complexity	24.0
Median method complexity	2.0
Most complex class	Quentn_Wp_Restrict_Access
Most complex function	Quentn_Wp_Page_Restriction_Meta_Box::quentn_page_restriction_callback()

Classes	23
Methods	221
Functions	5

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

[26-Feb-2021 12:47:53 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[26-Feb-2021 12:47:53 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[26-Feb-2021 12:47:53 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[26-Feb-2021 12:47:53 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[26-Feb-2021 12:47:53 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[26-Feb-2021 12:47:55 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
[26-Feb-2021 12:47:55 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
[26-Feb-2021 12:47:55 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
[26-Feb-2021 12:47:55 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
[26-Feb-2021 12:47:55 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
[26-Feb-2021 12:47:55 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
[26-Feb-2021 12:47:59 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
[26-Feb-2021 12:47:59 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
[26-Feb-2021 12:47:59 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
[26-Feb-2021 12:47:59 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
[26-Feb-2021 12:47:59 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
[26-Feb-2021 12:47:59 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
[26-Feb-2021 12:48: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
[26-Feb-2021 12:48: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
[26-Feb-2021 12:48: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
[26-Feb-2021 12:48: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
[26-Feb-2021 12:48: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
[26-Feb-2021 12:48: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

Quentn WP 1.1.4