Does Jetpack Protect work with WordPress 6.3.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: 466.37 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.3.2 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
| Last updated | |
|---|---|
| Active installs | 100,000+ |
| WordPress.org page | https://wordpress.org/plugins/jetpack-protect/ |
| Badges |
|
| URL | /wp-admin/admin.php?page=jetpack-protect |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=jetpack-protect%2Fjetpack-protect.php&plugin_status=all&paged=1&s&_wpnonce=9f54081b7c |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 1.245 s |
| Memory usage | 3.84 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/admin.php?page=jetpack-protect |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.372 s |
| Memory usage | 3.31 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/admin.php?page=my-jetpack |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 1.165 s |
| Memory usage | 3.44 MiB |
| JS errors | None |
| Resource errors | None |
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.224 s |
| Memory usage | 3.56 MiB |
| JS errors | None |
| Resource errors | None |
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.371 s | 0.332 s | -0.039 s | 2.83 MiB | 3.27 MiB | + 451.94 KiB |
| /wp-admin/edit.php | 0.211 s | 0.225 s | +0.014 s | 2.85 MiB | 3.29 MiB | + 451.09 KiB |
| /wp-admin/post-new.php | 0.740 s | 0.932 s | +0.192 s | 5.22 MiB | 5.78 MiB | + 581.23 KiB |
| /wp-admin/upload.php | 0.627 s | 0.497 s | -0.130 s | 2.77 MiB | 3.19 MiB | + 434.93 KiB |
| /wp-admin/options-writing.php | 0.249 s | 0.216 s | -0.033 s | 2.76 MiB | 3.18 MiB | + 427.16 KiB |
| /wp-admin/media-new.php | 0.365 s | 0.259 s | -0.106 s | 2.74 MiB | 3.18 MiB | + 447.49 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.213 s | 0.196 s | -0.017 s | 2.76 MiB | 3.2 MiB | + 451.93 KiB |
| /wp-admin/post-new.php?post_type=page | 0.580 s | 0.590 s | +0.010 s | 5.21 MiB | 5.77 MiB | + 576.82 KiB |
| /wp-admin/options-discussion.php | 0.214 s | 0.284 s | +0.070 s | 2.75 MiB | 3.18 MiB | + 436.94 KiB |
| /wp-admin/edit-comments.php | 0.224 s | 0.435 s | +0.211 s | 2.78 MiB | 3.21 MiB | + 434.6 KiB |
| / | 0.278 s | 0.239 s | -0.039 s | 3.13 MiB | 3.56 MiB | + 435.94 KiB |
| Average | 0.370 s | 0.382 s | +0.012 s | 3.25 MiB | 3.71 MiB | + 466.37 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 | |
|---|---|---|---|---|---|
| PHP | 79.6% | 31,070 | 23,483 | 192 | |
| Markdown | 15.5% | 6,051 | 0 | 24 | |
| JSON | 3.0% | 1,187 | 0 | 23 | |
| Sass | 1.1% | 427 | 15 | 3 | |
| JavaScript | 0.3% | 116 | 39 | 6 | |
| SVG | 0.2% | 87 | 3 | 7 | |
| JSX | 0.1% | 49 | 4 | 1 | |
| CSS | 0.1% | 33 | 2 | 9 | |
| Total | 39,020 | 23,546 | 265 | ||
| Lines of code | 31,025 |
|---|---|
| Total complexity | 6,483 |
| Median class complexity | 24.0 |
| Median method complexity | 2.0 |
| Most complex class | Automattic\Jetpack\Device_Detection\User_Agent_Info |
| Most complex function | Automattic\Jetpack\Protect\Scan_Status::normalize_api_data() |
| Classes | 177 |
|---|---|
| Methods | 2,120 |
| Functions | 4 |
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 4wp_usermeta 4The log file is empty.