PJ News Ticker 1.5
Does PJ News Ticker work with WordPress 4.9.8 and PHP 7.0.16? A smoke test was performed on .
Summary
Errors
| 4 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Performance
Memory usage: 11.72 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.
Environment
| WordPress version | 4.9.8 |
|---|---|
| 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?activate=true&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=d5f1d05f66 |
| Aspect | after-activation |
| HTTP status | 200 OK |
| Load time | 0.058 s |
| Memory usage | 3.03 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 OK |
| Load time | 0.069 s |
| Memory usage | 3 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 OK |
| Load time | 0.081 s |
| Memory usage | 2.76 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.127 s | 0.089 s | -0.038 s | 3.12 MiB | 3.14 MiB | + 27.5 KiB |
| /wp-admin/edit.php | 0.097 s | 0.088 s | -0.009 s | 3.14 MiB | 3.16 MiB | + 25.28 KiB |
| /wp-admin/post-new.php | 0.182 s | 0.080 s | -0.102 s | 3.21 MiB | 3.24 MiB | + 32.45 KiB |
| /wp-admin/upload.php | 0.126 s | 0.066 s | -0.060 s | 2.98 MiB | 3.01 MiB | + 24.13 KiB |
| /wp-admin/options-writing.php | 0.090 s | 0.073 s | -0.017 s | 3.06 MiB | 3 MiB | - 63.43 KiB |
| /wp-admin/media-new.php | 0.059 s | 0.045 s | -0.014 s | 2.97 MiB | 2.99 MiB | + 25.23 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.081 s | 0.062 s | -0.019 s | 3.01 MiB | 3.03 MiB | + 26.45 KiB |
| /wp-admin/post-new.php?post_type=page | 0.173 s | 0.095 s | -0.078 s | 3.22 MiB | 3.24 MiB | + 25.2 KiB |
| /wp-admin/options-discussion.php | 0.080 s | 0.072 s | -0.008 s | 2.97 MiB | 2.99 MiB | + 25.49 KiB |
| /wp-admin/edit-comments.php | 0.082 s | 0.077 s | -0.005 s | 3.01 MiB | 3.06 MiB | + 51.95 KiB |
| / | 0.106 s | 0.133 s | +0.027 s | 2.83 MiB | 2.76 MiB | - 71.28 KiB |
| Average | 0.109 s | 0.080 s | -0.029 s | 3.05 MiB | 3.06 MiB | + 11.72 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 4 lines
[30-Sep-2018 02:40:20 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 4161
[30-Sep-2018 02:40:20 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 4161
[30-Sep-2018 02:40:23 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 4161
[30-Sep-2018 02:40:23 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 4161