Does Wordfence Security work with WordPress 4.9.5 and PHP 7.0.16? 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: 1.71 MiB
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 | 4.9.5 |
---|---|
PHP version | 7.0.16 |
MySQL version | 5.7.17 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 5,000,000+ |
WordPress.org page | https://wordpress.org/plugins/wordfence/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?activate=true&plugin_status=all&paged=1&s= |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=wordfence%2Fwordfence.php&plugin_status=all&paged=1&s&_wpnonce=63c65272c3 |
Aspect | after-activation |
HTTP status | 200 OK |
Load time | 7.997 s |
Memory usage | 4.99 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=Wordfence |
---|---|
Aspect | menu-item |
HTTP status | 200 OK |
Load time | 0.941 s |
Memory usage | 4.68 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=WordfenceWAF |
---|---|
Aspect | menu-item |
HTTP status | 200 OK |
Load time | 0.198 s |
Memory usage | 5.39 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=WordfenceScan |
---|---|
Aspect | menu-item |
HTTP status | 200 OK |
Load time | 0.230 s |
Memory usage | 4.65 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=WordfenceTools |
---|---|
Aspect | menu-item |
HTTP status | 200 OK |
Load time | 0.233 s |
Memory usage | 6.24 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=WordfenceOptions |
---|---|
Aspect | menu-item |
HTTP status | 200 OK |
Load time | 0.296 s |
Memory usage | 5.35 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=WordfenceSupport |
---|---|
Aspect | menu-item |
HTTP status | 200 OK |
Load time | 0.142 s |
Memory usage | 4.58 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 OK |
Load time | 0.079 s |
Memory usage | 4.33 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/index.php |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 OK |
Load time | 0.155 s |
Memory usage | 4.74 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.124 s | 0.133 s | +0.009 s | 2.97 MiB | 4.74 MiB | + 1.77 MiB |
/wp-admin/edit.php | 0.103 s | 0.110 s | +0.007 s | 3 MiB | 4.75 MiB | + 1.75 MiB |
/wp-admin/post-new.php | 0.195 s | 0.096 s | -0.099 s | 3.07 MiB | 4.83 MiB | + 1.76 MiB |
/wp-admin/upload.php | 0.082 s | 0.098 s | +0.016 s | 2.9 MiB | 4.59 MiB | + 1.69 MiB |
/wp-admin/options-writing.php | 0.075 s | 0.115 s | +0.040 s | 2.89 MiB | 4.58 MiB | + 1.69 MiB |
/wp-admin/media-new.php | 0.056 s | 0.107 s | +0.051 s | 2.88 MiB | 4.57 MiB | + 1.69 MiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.077 s | 0.098 s | +0.021 s | 2.92 MiB | 4.61 MiB | + 1.69 MiB |
/wp-admin/post-new.php?post_type=page | 0.177 s | 0.190 s | +0.013 s | 3.07 MiB | 4.83 MiB | + 1.75 MiB |
/wp-admin/options-discussion.php | 0.077 s | 0.100 s | +0.023 s | 2.89 MiB | 4.58 MiB | + 1.69 MiB |
/wp-admin/edit-comments.php | 0.132 s | 0.098 s | -0.034 s | 2.93 MiB | 4.68 MiB | + 1.75 MiB |
/ | 0.101 s | 0.079 s | -0.022 s | 2.71 MiB | 4.33 MiB | + 1.62 MiB |
Average | 0.109 s | 0.111 s | +0.002 s | 2.93 MiB | 4.64 MiB | + 1.71 MiB |
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
3{
"dashboard": {
"wordfence_activity_report_widget": {
"title": "Wordfence activity in the past week",
"context": "normal"
}
}
}
The log file is empty.