Does WP to Twitter work with WordPress 6.0 and PHP 7.4.8? 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: 125.48 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.0 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 10,000+ |
WordPress.org page | https://wordpress.org/plugins/wp-to-twitter/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=wp-to-twitter%2Fwp-to-twitter.php&plugin_status=all&paged=1&s&_wpnonce=5727ba72ef |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.446 s |
Memory usage | 3.81 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wp-tweets-pro |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.741 s |
Memory usage | 4.07 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wp-tweets-pro&tab=basic |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.410 s |
Memory usage | 3.77 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wp-tweets-pro&tab=shortener |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.347 s |
Memory usage | 3.76 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wp-tweets-pro&tab=advanced |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.410 s |
Memory usage | 3.76 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wp-tweets-pro&tab=support |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.386 s |
Memory usage | 3.77 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wp-tweets-pro&tab=pro |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 |
Load time | 0.351 s |
Memory usage | 3.76 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.231 s |
Memory usage | 3.66 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 |
Load time | 1.101 s |
Memory usage | 5.64 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 1.846 s |
Memory usage | 5.62 MiB |
JS errors |
External errors:
The following JavaScript errors were probably triggered by
WordPress itself, or by compatibility issues in the test runner.
They are not related to the plugin.
|
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.401 s | 0.307 s | -0.094 s | 3.72 MiB | 3.83 MiB | + 109.87 KiB |
/wp-admin/edit.php | 0.186 s | 0.203 s | +0.017 s | 3.75 MiB | 3.92 MiB | + 174.55 KiB |
/wp-admin/post-new.php | 0.987 s | 1.305 s | +0.318 s | 5.53 MiB | 5.64 MiB | + 110.79 KiB |
/wp-admin/upload.php | 0.467 s | 0.552 s | +0.085 s | 3.68 MiB | 3.79 MiB | + 109.1 KiB |
/wp-admin/options-writing.php | 0.327 s | 0.169 s | -0.158 s | 3.61 MiB | 3.76 MiB | + 153.41 KiB |
/wp-admin/media-new.php | 0.321 s | 0.236 s | -0.085 s | 3.66 MiB | 3.77 MiB | + 109.27 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.194 s | 0.202 s | +0.008 s | 3.68 MiB | 3.79 MiB | + 111.23 KiB |
/wp-admin/post-new.php?post_type=page | 1.014 s | 0.970 s | -0.044 s | 5.53 MiB | 5.63 MiB | + 103.42 KiB |
/wp-admin/options-discussion.php | 0.244 s | 0.269 s | +0.025 s | 3.59 MiB | 3.76 MiB | + 173.59 KiB |
/wp-admin/edit-comments.php | 0.229 s | 0.224 s | -0.005 s | 3.69 MiB | 3.8 MiB | + 109.13 KiB |
/ | 0.270 s | 0.226 s | -0.044 s | 3.55 MiB | 3.66 MiB | + 115.92 KiB |
Average | 0.422 s | 0.424 s | +0.002 s | 4 MiB | 4.12 MiB | + 125.48 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 | 89.1% | 6,493 | 2,457 | 17 | |
CSS | 8.7% | 632 | 0 | 3 | |
JavaScript | 2.2% | 159 | 18 | 4 | |
Total | 7,284 | 2,475 | 24 |
Lines of code | 6,462 |
---|---|
Total complexity | 1,506 |
Median class complexity | 5.0 |
Median method complexity | 2.0 |
Most complex class | TmhOAuth |
Most complex function | wpt_tweet() |
Classes | 18 |
---|---|
Methods | 122 |
Functions | 131 |
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
24ID | Name |
---|---|
wpt-latest-tweets | WP to Twitter - Latest Tweets |
wpt-search-tweets | WP to Twitter - Searched Tweets |
{
"post": {
"wp2t": {
"title": "WP to Twitter",
"context": "side"
}
}
}
The log file is empty.