Does Jetpack Protect work with WordPress 6.1.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: 424.56 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.1.1 |
|---|---|
| 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=29e259bb3e |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 1.473 s |
| Memory usage | 3.83 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/admin.php?page=jetpack-protect |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.391 s |
| Memory usage | 3.41 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/admin.php?page=my-jetpack |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.778 s |
| Memory usage | 3.46 MiB |
| JS errors | None |
| Resource errors | None |
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.213 s |
| Memory usage | 3.36 MiB |
| JS errors | None |
| Resource errors | None |
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.268 s | 0.385 s | +0.117 s | 3.05 MiB | 3.44 MiB | + 400.56 KiB |
| /wp-admin/edit.php | 0.174 s | 0.223 s | +0.049 s | 3.07 MiB | 3.52 MiB | + 460.87 KiB |
| /wp-admin/post-new.php | 0.772 s | 0.814 s | +0.042 s | 4.97 MiB | 5.48 MiB | + 520.74 KiB |
| /wp-admin/upload.php | 0.529 s | 0.304 s | -0.225 s | 2.99 MiB | 3.36 MiB | + 381.89 KiB |
| /wp-admin/options-writing.php | 0.144 s | 0.151 s | +0.007 s | 2.99 MiB | 3.35 MiB | + 367.91 KiB |
| /wp-admin/media-new.php | 0.259 s | 0.383 s | +0.124 s | 2.97 MiB | 3.35 MiB | + 394.81 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.180 s | 0.245 s | +0.065 s | 2.98 MiB | 3.39 MiB | + 419.88 KiB |
| /wp-admin/post-new.php?post_type=page | 0.625 s | 0.648 s | +0.023 s | 4.96 MiB | 5.46 MiB | + 516.33 KiB |
| /wp-admin/options-discussion.php | 0.235 s | 0.196 s | -0.039 s | 2.98 MiB | 3.35 MiB | + 381.76 KiB |
| /wp-admin/edit-comments.php | 0.199 s | 0.235 s | +0.036 s | 3 MiB | 3.39 MiB | + 403.23 KiB |
| / | 0.271 s | 0.221 s | -0.050 s | 2.94 MiB | 3.36 MiB | + 422.14 KiB |
| Average | 0.332 s | 0.346 s | +0.014 s | 3.35 MiB | 3.77 MiB | + 424.56 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.5% | 28,035 | 21,686 | 175 | |
| Markdown | 14.2% | 5,020 | 0 | 23 | |
| JSON | 3.2% | 1,123 | 0 | 22 | |
| Sass | 1.2% | 438 | 14 | 3 | |
| JavaScript | 1.2% | 423 | 61 | 9 | |
| SVG | 0.3% | 116 | 6 | 8 | |
| CSS | 0.1% | 46 | 2 | 10 | |
| JSX | 0.1% | 45 | 3 | 1 | |
| Total | 35,246 | 21,772 | 251 | ||
| Lines of code | 27,953 |
|---|---|
| Total complexity | 5,820 |
| Median class complexity | 22.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 | 160 |
|---|---|
| Methods | 1,920 |
| 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 3wp_usermeta 4The log file is empty.