73% podlove-web-player

Code Review | Podlove Web Player

WordPress plugin Podlove Web Player scored73%from 54 tests.

About plugin

  • Plugin page: podlove-web-player
  • Plugin version: 5.7.1
  • PHP compatiblity: 7.2+
  • PHP version: 7.4.16
  • WordPress compatibility: 4.9.6-5.8
  • WordPress version: 6.3.1
  • First release: Jul 3, 2012
  • Latest release: Oct 16, 2022
  • Number of updates: 140
  • Update frequency: every 26.9 days
  • Top authors: gerritvanaaken (40.71%)aheimbuch (37.14%)simonwaldherr (20.71%)eteubert (3.57%)

Code review

54 tests

User reviews

13 reviews

Install metrics

6,000+ active /146,689 total downloads

Benchmarks

Plugin footprint 83% from 16 tests

Installer Passed 1 test

🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully

Server metrics [RAM: ▼0.40MB] [CPU: ▼14.78ms] Passed 4 tests

A check of server-side resources used by Podlove Web Player
Server-side resource usage in normal parameters
PageMemory (MB)CPU Time (ms)
Home /3.74 ▲0.2840.59 ▼5.26
Dashboard /wp-admin3.57 ▲0.2745.75 ▼5.27
Posts /wp-admin/edit.php3.62 ▲0.2749.90 ▲1.96
Add New Post /wp-admin/post-new.php3.47 ▼2.4144.68 ▼46.99
Media Library /wp-admin/upload.php3.49 ▲0.2632.65 ▼1.58
Podlove Web Player /wp-admin/options-general.php?page=podlove-web-player-settings3.4930.70

Server storage [IO: ▲14.36MB] [DB: ▲0.00MB] Passed 3 tests

Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 126 new files
Database: no new tables, 7 new options
New WordPress options
widget_recent-posts
podlove-web-player
db_upgraded
can_compress_scripts
widget_theysaidso_widget
theysaidso_admin_options
widget_recent-comments

Browser metrics Passed 4 tests

An overview of browser requirements for Podlove Web Player
Normal browser usage
PageNodesMemory (MB)Script (ms)Layout (ms)
Home /2,819 ▲7313.76 ▼0.8112.35 ▲10.1841.83 ▼3.32
Dashboard /wp-admin2,210 ▲224.86 ▼0.02100.98 ▼13.8739.03 ▼5.11
Posts /wp-admin/edit.php2,093 ▲42.01 ▲0.0138.77 ▲0.8834.08 ▼1.24
Add New Post /wp-admin/post-new.php6,204 ▲4,66019.40 ▲1.01893.97 ▲243.5656.05 ▲1.71
Media Library /wp-admin/upload.php1,395 ▲74.22 ▲0.0398.33 ▼0.2042.19 ▼0.33
Podlove Web Player /wp-admin/options-general.php?page=podlove-web-player-settings1,63013.78459.5099.39

Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests

🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
  • The uninstall procedure has failed, leaving 6 options in the database
    • theysaidso_admin_options
    • can_compress_scripts
    • widget_recent-posts
    • db_upgraded
    • widget_recent-comments
    • widget_theysaidso_widget

Smoke tests 25% from 4 tests

Server-side errors 0% from 1 test

🔹 Test weight: 20 | This is a shallow check for server-side errors
These errors were triggered by the plugin
    • > GET request to /wp-admin/options-general.php?page=podlove-web-player-settings
    • > Notice in wp-content/plugins/podlove-web-player/includes/class-podlove-web-player-admin-api.php+426
    Undefined property: WP_Error::$data

SRP 0% from 2 tests

🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
  • 1× PHP files output text when accessed directly:
    • > /wp-content/plugins/podlove-web-player/admin/partials/podlove-web-player-admin-display.php
  • 2× PHP files trigger errors when accessed directly with GET requests:
    • > PHP Fatal error
      Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/podlove-web-player/includes/class-podlove-web-player-activator.php:2
    • > PHP Fatal error
      Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/podlove-web-player/includes/class-podlove-web-player-uninstall.php:2

User-side errors Passed 1 test

🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test

Optimizations

Plugin configuration 97% from 29 tests

readme.txt 94% from 16 tests

The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that need to be fixed:
  • Plugin Name: You should set the name of your plugin on the first line ( === podlove-web-player === )
You can look at the official readme.txt

podlove-web-player/podlove-web-player.php Passed 13 tests

Analyzing the main PHP file in "Podlove Web Player" version 5.7.1
30 characters long description:
Audio First Podcast Web Player

Code Analysis Passed 3 tests

File types Passed 1 test

🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Success! There were no dangerous files found in this plugin2,558 lines of code in 86 files:
LanguageFilesBlank linesComment linesLines of code
PHP203601,0221,543
HTML6181327
JSON610220
PO File28082216
SVG2600191
JavaScript2306831
Markdown116028
CSS2022

PHP code Passed 2 tests

This plugin's cyclomatic complexity and code structure detailed below
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity
Average complexity per logical line of code0.29
Average class complexity9.47
▷ Minimum class complexity1.00
▷ Maximum class complexity47.00
Average method complexity2.28
▷ Minimum method complexity1.00
▷ Maximum method complexity21.00
Code structure
Namespaces0
Interfaces0
Traits0
Classes15
▷ Abstract classes00.00%
▷ Concrete classes15100.00%
▷ Final classes00.00%
Methods100
▷ Static methods44.00%
▷ Public methods7676.00%
▷ Protected methods00.00%
▷ Private methods2424.00%
Functions10
▷ Named functions220.00%
▷ Anonymous functions880.00%
Constants2
▷ Global constants2100.00%
▷ Class constants00.00%
▷ Public constants00.00%

Plugin size Passed 2 tests

Image compression Passed 2 tests

Often times overlooked, PNG files can occupy unnecessary space in your plugin
No PNG files were detected