PJ News Ticker 1.5.2
Does PJ News Ticker work with WordPress 5.0.3 and PHP 7.0.16? A smoke test was performed on .
Summary
Errors
| 12 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Performance
Memory usage: 35.93 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.052 seconds
The average page load time increased by this amount after activating the plugin.
Environment
| WordPress version | 5.0.3 |
|---|---|
| PHP version | 7.0.16 |
| MySQL version | 5.7.17 |
| PHP memory limit | 256M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 4,000+ |
| WordPress.org page | https://wordpress.org/plugins/pj-news-ticker/ |
| Badges |
|
Pages 3
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=pj-news-ticker%2Fpj-news-ticker.php&plugin_status=all&paged=1&s&_wpnonce=10bf789361 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.326 s |
| Memory usage | 3.19 MiB |
| JS errors | None |
| Resource errors | None |
Settings → PJ News Ticker
| URL | /wp-admin/options-general.php?page=pj-news-ticker |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.223 s |
| Memory usage | 3.16 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.268 s |
| Memory usage | 2.92 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.215 s | 0.205 s | -0.010 s | 3.22 MiB | 3.25 MiB | + 27.53 KiB |
| /wp-admin/edit.php | 0.183 s | 0.165 s | -0.018 s | 3.25 MiB | 3.28 MiB | + 25.31 KiB |
| /wp-admin/post-new.php | 0.905 s | 1.081 s | +0.176 s | 4.92 MiB | 4.95 MiB | + 31.08 KiB |
| /wp-admin/upload.php | 0.369 s | 0.511 s | +0.142 s | 3.15 MiB | 3.17 MiB | + 25.23 KiB |
| /wp-admin/options-writing.php | 0.162 s | 0.190 s | +0.028 s | 3.14 MiB | 3.16 MiB | + 26.12 KiB |
| /wp-admin/media-new.php | 0.160 s | 0.227 s | +0.067 s | 3.07 MiB | 3.15 MiB | + 90.16 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.168 s | 0.162 s | -0.006 s | 3.17 MiB | 3.2 MiB | + 26.48 KiB |
| /wp-admin/post-new.php?post_type=page | 0.837 s | 0.989 s | +0.152 s | 4.9 MiB | 4.93 MiB | + 23.82 KiB |
| /wp-admin/options-discussion.php | 0.199 s | 0.215 s | +0.016 s | 3.07 MiB | 3.16 MiB | + 90.12 KiB |
| /wp-admin/edit-comments.php | 0.184 s | 0.248 s | +0.064 s | 3.18 MiB | 3.2 MiB | + 24.91 KiB |
| / | 0.267 s | 0.227 s | -0.040 s | 2.92 MiB | 2.92 MiB | + 4.51 KiB |
| Average | 0.332 s | 0.384 s | +0.052 s | 3.45 MiB | 3.49 MiB | + 35.93 KiB |
Additions
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.
No new entries found.
PHP Error Log 12 lines
[12-Jan-2019 02:07:11 UTC] PHP Notice: wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[12-Jan-2019 02:07:11 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[12-Jan-2019 02:07:13 UTC] PHP Notice: wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[12-Jan-2019 02:07:13 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[12-Jan-2019 02:07:13 UTC] PHP Notice: wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[12-Jan-2019 02:07:13 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[12-Jan-2019 02:07:15 UTC] PHP Notice: wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[12-Jan-2019 02:07:15 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[12-Jan-2019 02:07:15 UTC] PHP Notice: wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[12-Jan-2019 02:07:15 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[12-Jan-2019 02:07:16 UTC] PHP Notice: wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[12-Jan-2019 02:07:16 UTC] PHP Notice: wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231