Radio Player 1.1.1

Does Radio Player work with WordPress 6.0 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
1PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 579.56 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: 0.137 seconds
The average page load time increased by this amount after activating the plugin.

Environment
WordPress version6.0
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 7,000+
WordPress.org page https://wordpress.org/plugins/radio-player/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 9

‹ Test site — WordPress

Page screenshot: ‹ Test site — WordPress
URL /wp-admin/admin.php?page=radio-player
Requested URL /wp-admin/plugins.php?action=activate&plugin=radio-player%2Fplugin.php&plugin_status=all&paged=1&s&_wpnonce=667a242762
Aspect after-activation
HTTP status 200
Load time 1.075 s
Memory usage 4.62 MiB
JS errors None
Resource errors None

Radio Player

Page screenshot: Radio Player
URL /wp-admin/edit.php?post_type=radio
Aspect menu-item
HTTP status 200
Load time 0.424 s
Memory usage 4.31 MiB
JS errors None
Resource errors None

Radio Player → Add New Player

Page screenshot: Radio Player → Add New Player
URL /wp-admin/post-new.php?post_type=radio
Aspect menu-item
HTTP status 200
Load time 0.694 s
Memory usage 4.45 MiB
JS errors None
Resource errors None

Radio Player → Getting Started

Page screenshot: Radio Player → Getting Started
URL /wp-admin/edit.php?post_type=radio&page=radio-player-get-started
Aspect menu-item
HTTP status 200
Load time 1.028 s
Memory usage 4.22 MiB
JS errors None
Resource errors None

Radio Player → Settings

Page screenshot: Radio Player → Settings
URL /wp-admin/edit.php?post_type=radio&page=radio-player-settings
Aspect menu-item
HTTP status 200
Load time 0.711 s
Memory usage 4.27 MiB
JS errors None
Resource errors None

Radio Player → Contact Us

Page screenshot: Radio Player → Contact Us
URL /wp-admin/edit.php?post_type=radio&page=radio-player-contact
Aspect menu-item
HTTP status 200
Load time 0.350 s
Memory usage 4.28 MiB
JS errors None
Resource errors None

Radio Player → Upgrade  ➤

Page screenshot: Radio Player → Upgrade  ➤
URL /wp-admin/edit.php?post_type=radio&page=radio-player-pricing
Aspect menu-item
HTTP status 200
Load time 0.302 s
Memory usage 4.57 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.388 s
Memory usage 4.08 MiB
JS errors None
Resource errors None

Widgets ‹ Test site — WordPress

Page screenshot: Widgets ‹ Test site — WordPress
URL /wp-admin/widgets.php
Aspect new-sidebar-widgets
HTTP status 200
Load time 1.355 s
Memory usage 5.97 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.
[
    {
        "message": "TypeError: Cannot read properties of null (reading 'offsetHeight')\n    at t (/wp-includes/js/dist/widgets.min.js?ver=80e98954519d1dad7a91a2248dbc2cc9:7:10419)\n    at IntersectionObserver.n.threshold (/wp-includes/js/dist/widgets.min.js?ver=80e98954519d1dad7a91a2248dbc2cc9:7:10591)",
        "trace": null,
        "code": null
    },
    {
        "message": "TypeError: Cannot read properties of null (reading 'offsetHeight')\n    at t (/wp-includes/js/dist/widgets.min.js?ver=80e98954519d1dad7a91a2248dbc2cc9:7:10419)\n    at IntersectionObserver.n.threshold (/wp-includes/js/dist/widgets.min.js?ver=80e98954519d1dad7a91a2248dbc2cc9:7:10591)",
        "trace": null,
        "code": null
    }
]
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.282 s0.567 s+0.285 s3.72 MiB4.31 MiB+ 607.63 KiB
/wp-admin/edit.php0.156 s0.327 s+0.171 s3.75 MiB4.33 MiB+ 595.09 KiB
/wp-admin/post-new.php0.650 s0.965 s+0.315 s5.53 MiB6.01 MiB+ 489.15 KiB
/wp-admin/upload.php0.319 s0.431 s+0.112 s3.68 MiB4.26 MiB+ 589.63 KiB
/wp-admin/options-writing.php0.340 s0.286 s-0.054 s3.61 MiB4.24 MiB+ 643.27 KiB
/wp-admin/media-new.php0.291 s0.292 s+0.001 s3.66 MiB4.23 MiB+ 581.47 KiB
/wp-admin/edit-tags.php?taxonomy=category0.159 s0.315 s+0.156 s3.68 MiB4.25 MiB+ 581.44 KiB
/wp-admin/post-new.php?post_type=page0.538 s0.615 s+0.077 s5.53 MiB6 MiB+ 484.16 KiB
/wp-admin/options-discussion.php0.179 s0.424 s+0.245 s3.59 MiB4.24 MiB+ 662.82 KiB
/wp-admin/edit-comments.php0.205 s0.344 s+0.139 s3.69 MiB4.27 MiB+ 594.61 KiB
/0.253 s0.310 s+0.057 s3.55 MiB4.08 MiB+ 545.87 KiB
Average 0.307 s0.443 s+0.137 s4 MiB4.57 MiB+ 579.56 KiB

Code Statistics

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.

PHP
Language % Lines of code Comment lines Files
PHP99.2%32,45416,471141
JavaScript0.6%202716
SVG0.1%3104
CSS0.0%152012
JSON0.0%901
Total 32,711 16,562 164

PHP Code Analysis | More results »

Lines of code 22,564
Total complexity 5,667
Median class complexity 12.0
Median method complexity 2.0
Most complex class Freemius
Most complex function FS_Plugin_Info_Dialog::install_plugin_information()
Classes 61
Methods 1,220
Functions 106

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.

Options wp_options 7

Custom Post Types 1

ID Name
radioPlayers

Sidebar Widgets 1

ID Name
radio_playerRadio Player

Meta Boxes

{
    "radio": {
        "radio_player_metabox": {
            "title": "Player Configuration",
            "context": "normal"
        },
        "radio_player_side_metabox": {
            "title": "Get more",
            "context": "side"
        }
    }
}

PHP Error Log 1 lines

[26-Jun-2022 22:41:33 UTC] PHP Notice:  Function wp_enqueue_script() was called <strong>incorrectly</strong>. "wp-editor" script should not be enqueued together with the new widgets editor (wp-edit-widgets or wp-customize-widgets). Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.8.0.) in /wp-includes/functions.php on line 5831
See also: All tests for this plugin, How to Hide Radio Player Admin Menus