Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▼0.90MB] [CPU: ▼325.77ms] Passed 4 tests
Analyzing server-side resources used by MediaGauge - Realtime Streaming Media Analytics
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.85 ▲0.13 | 35.96 ▲12.75 |
Dashboard /wp-admin | 2.75 ▼0.31 | 20.45 ▼22.67 |
Posts /wp-admin/edit.php | 2.75 ▼0.36 | 17.63 ▼24.39 |
Add New Post /wp-admin/post-new.php | 2.75 ▼2.68 | 20.21 ▼1,232.32 |
Media Library /wp-admin/upload.php | 2.75 ▼0.26 | 19.39 ▼23.69 |
MediaGauge Analytics /wp-admin/options-general.php?page=mediagauge | 2.75 | 20.59 |
Server storage [IO: ▲0.13MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 6 new files
Database: no new tables, 1 new option
New WordPress options |
---|
mediagauge_enabled |
Browser metrics Passed 4 tests
MediaGauge - Realtime Streaming Media Analytics: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,678 ▲96 | 16.32 ▲0.67 | 8.66 ▼0.64 | 47.32 ▼1.86 |
Dashboard /wp-admin | 2,938 ▲88 | 5.90 ▲0.07 | 148.72 ▲3.26 | 112.51 ▼0.79 |
Posts /wp-admin/edit.php | 2,711 ▲5 | 2.70 ▲0.02 | 65.71 ▼2.11 | 100.35 ▼9.55 |
Add New Post /wp-admin/post-new.php | 1,591 ▲110 | 21.54 ▲3.08 | 268.22 ▼99.29 | 105.74 ▼13.82 |
Media Library /wp-admin/upload.php | 1,777 ▲5 | 5.01 ▼0.00 | 163.26 ▲10.24 | 107.10 ▼20.87 |
MediaGauge Analytics /wp-admin/options-general.php?page=mediagauge | 1,057 | 2.09 | 79.10 | 80.12 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- This plugin cannot be uninstalled
- > User notice in wp-includes/functions.php+5663
add_submenu_page was called incorrectly. The seventh parameter passed to add_submenu_page() should be an integer representing menu position. Please see Debugging in WordPress for more information. (This message was added in version 5.3.0.)
- The uninstall procedure has failed, leaving 1 option in the database
- mediagauge_enabled
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
These errors were triggered by the plugin
- > GET request to /wp-admin/options-general.php?page=mediagauge
- > User notice in wp-includes/functions.php+5663
add_submenu_page was called incorrectly. The seventh parameter passed to add_submenu_page() should be an integer representing menu position. Please see Debugging in WordPress for more information. (This message was added in version 5.3.0.)
- > GET request to /wp-admin/options-general.php?page=mediagauge
- > Notice in wp-content/plugins/mediagauge-streaming-media-analytics/mediagauge-analytics-admin.php+74
Undefined variable: api_key_error
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following items
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/mediagauge-streaming-media-analytics/mediagauge-analytics-admin.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/mediagauge-streaming-media-analytics/mediagauge-analytics-admin.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Please fix the following attributes:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== mediagauge-streaming-media-analytics ===
) - Screenshots: These screenshots do not have images: #1 (The analytics dashboard.), #2 (The MediaGauge plugin settings page.)
mediagauge-streaming-media-analytics/mediagauge-analytics.php 92% from 13 tests
The main PHP script in "MediaGauge - Realtime Streaming Media Analytics" version 1.0 is automatically included on every request by WordPress
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("mediagauge-streaming-media-analytics.php" instead of "mediagauge-analytics.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected87 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 33 | 23 | 87 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.36 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 4 | |
▷ Named functions | 4 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 0 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 1 test
Image compression Passed 1 test
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
3 PNG files occupy 0.13MB with 0.07MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-2.png | 15.47KB | 6.19KB | ▼ 59.99% |
icon.png | 2.10KB | 1.43KB | ▼ 31.90% |
screenshot-1.png | 111.48KB | 41.27KB | ▼ 62.98% |