Does Device Detector work with WordPress 6.7.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: 154.14 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.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=a9ff313e7c |
Aspect | after-activation |
HTTP status | 200 |
Load time | 1.110 s |
Memory usage | 5.93 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=perfopsone-dashboard |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.271 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.188 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.166 s |
Memory usage | 3.62 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.202 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.292 s | 0.301 s | +0.009 s | 3.48 MiB | 3.64 MiB | + 164.11 KiB |
/wp-admin/edit.php | 0.203 s | 0.211 s | +0.008 s | 3.54 MiB | 3.73 MiB | + 190.08 KiB |
/wp-admin/post-new.php | 0.790 s | 0.656 s | -0.134 s | 5.92 MiB | 6.11 MiB | + 194.42 KiB |
/wp-admin/upload.php | 0.549 s | 0.330 s | -0.219 s | 3.49 MiB | 3.64 MiB | + 143.95 KiB |
/wp-admin/options-writing.php | 0.204 s | 0.189 s | -0.015 s | 3.47 MiB | 3.62 MiB | + 148.35 KiB |
/wp-admin/media-new.php | 0.341 s | 0.495 s | +0.154 s | 3.46 MiB | 3.62 MiB | + 156.55 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.202 s | 0.192 s | -0.010 s | 3.48 MiB | 3.64 MiB | + 167.3 KiB |
/wp-admin/post-new.php?post_type=page | 0.575 s | 0.621 s | +0.046 s | 5.92 MiB | 6.1 MiB | + 189.98 KiB |
/wp-admin/options-discussion.php | 0.282 s | 0.268 s | -0.014 s | 3.47 MiB | 3.62 MiB | + 144.85 KiB |
/wp-admin/edit-comments.php | 0.198 s | 0.216 s | +0.018 s | 3.49 MiB | 3.64 MiB | + 144.51 KiB |
/ | 0.317 s | 0.200 s | -0.117 s | 3.48 MiB | 3.53 MiB | + 51.46 KiB |
Average | 0.359 s | 0.334 s | -0.025 s | 3.93 MiB | 4.08 MiB | + 154.14 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 | 53.4% | 50,465 | 3,532 | 20 | |
JavaScript | 21.6% | 20,453 | 2,305 | 6 | |
PHP | 17.9% | 16,934 | 10,249 | 167 | |
SVG | 4.5% | 4,251 | 1 | 285 | |
CSS | 2.0% | 1,931 | 2 | 7 | |
Markdown | 0.5% | 471 | 0 | 7 | |
JSON | 0.1% | 60 | 0 | 3 | |
Total | 94,565 | 16,089 | 495 |
Lines of code | 16,417 |
---|---|
Total complexity | 3,211 |
Median class complexity | 7.5 |
Median method complexity | 2.0 |
Most complex class | PODeviceDetector\Plugin\Feature\Analytics |
Most complex function | PODeviceDetector\Plugin\Feature\Analytics::query_kpi() |
Classes | 116 |
---|---|
Methods | 769 |
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.