Report - Quentn WP 1.1.5 - PluginTests.com

Does Quentn WP work with WordPress 5.7.2 and PHP 7.4.8? A smoke test was performed on 2021-05-17 06:36:00 UTC.

Summary

Errors

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

Performance

Memory usage: 188.39 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: 0.078 seconds
The average page load time increased by this amount after activating the plugin.

Environment

WordPress version	5.7.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=999020b148
Aspect	after-activation
HTTP status	200
Load time	0.483 s
Memory usage	2.91 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.408 s
Memory usage	2.92 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.206 s
Memory usage	2.84 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.194 s
Memory usage	2.84 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.169 s
Memory usage	2.88 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.202 s
Memory usage	2.96 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.222 s
Memory usage	2.94 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.961 s
Memory usage	5.39 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.258 s	0.373 s	+0.115 s	2.82 MiB	2.97 MiB	+ 155.67 KiB
/wp-admin/edit.php	0.173 s	0.197 s	+0.024 s	2.86 MiB	2.99 MiB	+ 134.54 KiB
/wp-admin/post-new.php	0.882 s	1.137 s	+0.255 s	5.02 MiB	5.39 MiB	+ 370.88 KiB
/wp-admin/upload.php	0.577 s	0.601 s	+0.024 s	2.7 MiB	2.94 MiB	+ 247.34 KiB
/wp-admin/options-writing.php	0.239 s	0.203 s	-0.036 s	2.71 MiB	2.86 MiB	+ 151.59 KiB
/wp-admin/media-new.php	0.207 s	0.195 s	-0.012 s	2.67 MiB	2.79 MiB	+ 118.59 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.175 s	0.192 s	+0.017 s	2.77 MiB	2.9 MiB	+ 136.75 KiB
/wp-admin/post-new.php?post_type=page	1.057 s	1.484 s	+0.427 s	5.01 MiB	5.38 MiB	+ 382 KiB
/wp-admin/options-discussion.php	0.271 s	0.322 s	+0.051 s	2.67 MiB	2.81 MiB	+ 136.09 KiB
/wp-admin/edit-comments.php	0.227 s	0.238 s	+0.011 s	2.78 MiB	2.91 MiB	+ 135.44 KiB
/	0.232 s	0.211 s	-0.021 s	2.65 MiB	2.75 MiB	+ 103.46 KiB
Average	0.391 s	0.468 s	+0.078 s	3.15 MiB	3.34 MiB	+ 188.39 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,695	2,176	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,279	2,420	52

PHP Code Analysis | More results »

Lines of code	3,466
Total complexity	781
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

[17-May-2021 06:36:16 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[17-May-2021 06:36:16 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[17-May-2021 06:36:16 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[17-May-2021 06:36:16 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[17-May-2021 06:36:16 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/quentn-wp/admin/class-quentn-wp-admin.php on line 875
[17-May-2021 06:36:19 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 5313
[17-May-2021 06:36:19 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 5313
[17-May-2021 06:36:19 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 5313
[17-May-2021 06:36:19 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 5313
[17-May-2021 06:36:19 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 5313
[17-May-2021 06:36:19 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 5313
[17-May-2021 06:36:23 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 5313
[17-May-2021 06:36:23 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 5313
[17-May-2021 06:36:23 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 5313
[17-May-2021 06:36:23 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 5313
[17-May-2021 06:36:23 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 5313
[17-May-2021 06:36:23 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 5313
[17-May-2021 06:36:26 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 5313
[17-May-2021 06:36:26 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 5313
[17-May-2021 06:36:26 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 5313
[17-May-2021 06:36:26 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 5313
[17-May-2021 06:36:26 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 5313
[17-May-2021 06:36:26 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 5313

Quentn WP 1.1.5