Does Device Detector work with WordPress 6.7.2 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: 154.61 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.7.2 |
---|---|
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=c39fc30cd1 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.960 s |
Memory usage | 6 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=perfopsone-dashboard |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.207 s |
Memory usage | 3.65 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=perfopsone-tools |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.142 s |
Memory usage | 3.62 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=perfopsone-analytics |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.141 s |
Memory usage | 3.62 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.166 s |
Memory usage | 3.53 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.312 s | 0.283 s | -0.029 s | 3.48 MiB | 3.64 MiB | + 164.17 KiB |
/wp-admin/edit.php | 0.179 s | 0.191 s | +0.012 s | 3.54 MiB | 3.73 MiB | + 190.13 KiB |
/wp-admin/post-new.php | 0.718 s | 0.672 s | -0.046 s | 5.93 MiB | 6.12 MiB | + 194.48 KiB |
/wp-admin/upload.php | 0.572 s | 0.482 s | -0.090 s | 3.5 MiB | 3.64 MiB | + 144.01 KiB |
/wp-admin/options-writing.php | 0.206 s | 0.190 s | -0.016 s | 3.47 MiB | 3.62 MiB | + 148.41 KiB |
/wp-admin/media-new.php | 0.252 s | 0.218 s | -0.034 s | 3.46 MiB | 3.62 MiB | + 156.6 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.186 s | 0.172 s | -0.014 s | 3.48 MiB | 3.64 MiB | + 167.37 KiB |
/wp-admin/post-new.php?post_type=page | 0.574 s | 0.562 s | -0.012 s | 5.92 MiB | 6.1 MiB | + 190.04 KiB |
/wp-admin/options-discussion.php | 0.415 s | 0.232 s | -0.183 s | 3.47 MiB | 3.62 MiB | + 144.91 KiB |
/wp-admin/edit-comments.php | 0.230 s | 0.365 s | +0.135 s | 3.49 MiB | 3.64 MiB | + 144.56 KiB |
/ | 0.273 s | 0.222 s | -0.051 s | 3.47 MiB | 3.53 MiB | + 56.02 KiB |
Average | 0.356 s | 0.326 s | -0.030 s | 3.93 MiB | 4.08 MiB | + 154.61 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.