Does Device Detector work with WordPress 6.8.1 and PHP 8.1.12? A smoke test was performed on .
No PHP errors, warnings or notices | |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors | |
Looks good! No problems were detected. |
Memory usage: 170.04 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.
WordPress version | 6.8.1 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 700+ |
WordPress.org page | https://wordpress.org/plugins/device-detector/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=device-detector%2Fdevice-detector.php&plugin_status=all&paged=1&s&_wpnonce=91b2202b59 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 1.137 s |
Memory usage | 6.02 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=perfopsone-dashboard |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.284 s |
Memory usage | 3.67 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=perfopsone-tools |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.170 s |
Memory usage | 3.64 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=perfopsone-analytics |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.161 s |
Memory usage | 3.64 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.179 s |
Memory usage | 3.55 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.396 s | 0.306 s | -0.090 s | 3.51 MiB | 3.67 MiB | + 163.92 KiB |
/wp-admin/edit.php | 0.209 s | 0.196 s | -0.013 s | 3.57 MiB | 3.75 MiB | + 187.44 KiB |
/wp-admin/post-new.php | 0.773 s | 0.665 s | -0.108 s | 6.06 MiB | 6.3 MiB | + 248.3 KiB |
/wp-admin/upload.php | 0.615 s | 0.763 s | +0.148 s | 3.52 MiB | 3.66 MiB | + 143.73 KiB |
/wp-admin/options-writing.php | 0.223 s | 0.233 s | +0.010 s | 3.5 MiB | 3.65 MiB | + 148.13 KiB |
/wp-admin/media-new.php | 0.294 s | 0.219 s | -0.075 s | 3.49 MiB | 3.64 MiB | + 156.33 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.200 s | 0.214 s | +0.014 s | 3.5 MiB | 3.67 MiB | + 167.09 KiB |
/wp-admin/post-new.php?post_type=page | 0.611 s | 0.567 s | -0.044 s | 6.05 MiB | 6.29 MiB | + 243.85 KiB |
/wp-admin/options-discussion.php | 0.435 s | 0.412 s | -0.023 s | 3.5 MiB | 3.64 MiB | + 144.63 KiB |
/wp-admin/edit-comments.php | 0.266 s | 0.220 s | -0.046 s | 3.52 MiB | 3.66 MiB | + 144.29 KiB |
/ | 0.318 s | 0.402 s | +0.084 s | 3.43 MiB | 3.55 MiB | + 122.77 KiB |
Average | 0.395 s | 0.382 s | -0.013 s | 3.97 MiB | 4.14 MiB | + 170.04 KiB |
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.
Language | % | Lines of code | Comment lines | Files | |
---|---|---|---|---|---|
YAML | 54.1% | 52,230 | 3,674 | 20 | |
JavaScript | 21.2% | 20,453 | 2,305 | 6 | |
PHP | 17.7% | 17,099 | 10,266 | 167 | |
SVG | 4.4% | 4,251 | 1 | 285 | |
CSS | 2.0% | 1,931 | 2 | 7 | |
Markdown | 0.5% | 481 | 0 | 7 | |
JSON | 0.1% | 60 | 0 | 3 | |
Total | 96,505 | 16,248 | 495 |
Lines of code | 16,582 |
---|---|
Total complexity | 3,239 |
Median class complexity | 8.0 |
Median method complexity | 2.0 |
Most complex class | PODeviceDetector\Plugin\Feature\Analytics |
Most complex function | UDD\DeviceDetector::parseDevice() |
Classes | 116 |
---|---|
Methods | 770 |
Functions | 9 |
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
3The log file is empty.