Does Custom Twitter Feeds work with WordPress 5.7 and PHP 7.4.8? A smoke test was performed on .
1 | PHP warnings |
3 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 179.28 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.034 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.7 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 100,000+ |
WordPress.org page | https://wordpress.org/plugins/custom-twitter-feeds/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=custom-twitter-feeds%2Fcustom-twitter-feed.php&plugin_status=all&paged=1&s&_wpnonce=58cd4fe2a6 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.765 s |
Memory usage | 2.99 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=custom-twitter-feeds |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.308 s |
Memory usage | 2.93 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=custom-twitter-feeds&tab=customize |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.251 s |
Memory usage | 2.92 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=custom-twitter-feeds&tab=style |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.213 s |
Memory usage | 2.91 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=custom-twitter-feeds&tab=display |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.211 s |
Memory usage | 2.97 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=custom-twitter-feeds&tab=support |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.611 s |
Memory usage | 2.94 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=custom-twitter-feeds-customize |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.243 s |
Memory usage | 2.86 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=custom-twitter-feeds&tab=configure |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.191 s |
Memory usage | 2.86 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=custom-twitter-feeds-style |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.382 s |
Memory usage | 2.86 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.224 s |
Memory usage | 2.71 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 1.042 s |
Memory usage | 3.03 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.453 s | +0.185 s | 2.82 MiB | 3.01 MiB | + 194.8 KiB |
/wp-admin/edit.php | 0.180 s | 0.316 s | +0.136 s | 2.86 MiB | 3.06 MiB | + 200.25 KiB |
/wp-admin/post-new.php | 0.952 s | 1.268 s | +0.316 s | 5.02 MiB | 5.24 MiB | + 216.66 KiB |
/wp-admin/upload.php | 0.502 s | 0.540 s | +0.038 s | 2.7 MiB | 2.88 MiB | + 192.72 KiB |
/wp-admin/options-writing.php | 0.260 s | 0.203 s | -0.057 s | 2.71 MiB | 2.87 MiB | + 164.13 KiB |
/wp-admin/media-new.php | 0.222 s | 0.220 s | -0.002 s | 2.67 MiB | 2.86 MiB | + 195.76 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.180 s | 0.217 s | +0.037 s | 2.77 MiB | 2.96 MiB | + 196.35 KiB |
/wp-admin/post-new.php?post_type=page | 1.270 s | 0.934 s | -0.336 s | 5.01 MiB | 5.21 MiB | + 211.62 KiB |
/wp-admin/options-discussion.php | 0.320 s | 0.340 s | +0.020 s | 2.67 MiB | 2.87 MiB | + 197.26 KiB |
/wp-admin/edit-comments.php | 0.231 s | 0.277 s | +0.046 s | 2.78 MiB | 2.96 MiB | + 193.73 KiB |
/ | 0.260 s | 0.250 s | -0.010 s | 2.71 MiB | 2.72 MiB | + 8.76 KiB |
Average | 0.422 s | 0.456 s | +0.034 s | 3.16 MiB | 3.33 MiB | + 179.28 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 | 69.9% | 5,762 | 953 | 20 | |
CSS | 19.6% | 1,615 | 36 | 4 | |
JavaScript | 10.5% | 867 | 132 | 4 | |
Total | 8,244 | 1,121 | 28 |
Lines of code | 5,253 |
---|---|
Total complexity | 1,213 |
Median class complexity | 39.0 |
Median method complexity | 4.0 |
Most complex class | CtfFeed |
Most complex function | CtfFeed::filterTrimmedTweets() |
Classes | 10 |
---|---|
Methods | 142 |
Functions | 56 |
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
9ID | Name |
---|---|
custom-twitter-feeds-widget | Custom Twitter Feeds |
[10-Mar-2021 00:14:06 UTC] PHP Warning: Invalid argument supplied for foreach() in /wp-content/plugins/custom-twitter-feeds/views/admin/support.php on line 39
[10-Mar-2021 00:14:06 UTC] PHP Notice: Trying to access array offset on value of type bool in /wp-content/plugins/custom-twitter-feeds/views/admin/support.php on line 51
[10-Mar-2021 00:14:06 UTC] PHP Notice: Trying to access array offset on value of type bool in /wp-content/plugins/custom-twitter-feeds/views/admin/support.php on line 52
[10-Mar-2021 00:14:06 UTC] PHP Notice: Trying to access array offset on value of type bool in /wp-content/plugins/custom-twitter-feeds/views/admin/support.php on line 55