Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼0.00MB] [CPU: ▼12.59ms] Passed 4 tests
A check of server-side resources used by Video Expander
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 40.02 ▼7.41 |
Dashboard /wp-admin | 3.31 ▼0.03 | 44.47 ▼20.73 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 47.71 ▼2.01 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 77.73 ▼20.19 |
Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 35.59 ▲1.44 |
Server storage [IO: ▲0.83MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 10 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
theysaidso_admin_options |
widget_recent-comments |
widget_theysaidso_widget |
widget_recent-posts |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Video Expander
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.26 ▼1.13 | 1.84 ▼0.07 | 43.43 ▼0.64 |
Dashboard /wp-admin | 2,203 ▲15 | 5.80 ▲0.90 | 95.16 ▼21.07 | 39.29 ▼3.58 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.04 ▲0.04 | 37.88 ▼0.25 | 36.48 ▲5.59 |
Add New Post /wp-admin/post-new.php | 1,536 ▲3 | 23.22 ▲0.28 | 654.92 ▲15.80 | 52.36 ▲5.14 |
Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.20 ▼0.10 | 120.49 ▲22.21 | 53.40 ▲9.26 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please fix the following
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/video-expander/video-expander.php:42
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need your attention:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Example of a group of video-expander shortcodes ready to be displayed!), #2 (Two column video-expander gallery), #3 (Two column video-expander gallery with expanded video)
video-expander/video-expander.php Passed 13 tests
The entry point to "Video Expander" version 1.0 is a PHP file that has certain tags in its header comment area
103 characters long description:
Creates shortcode to display video iframes in columns, where each video expands to play on mouse click.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Everything looks great! No dangerous files found in this plugin207 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 1 | 7 | 0 | 74 |
PHP | 1 | 29 | 21 | 72 |
JavaScript | 1 | 18 | 13 | 58 |
Markdown | 1 | 1 | 0 | 3 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.17 |
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 | 6 | |
▷ Named functions | 6 | 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 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
3 PNG files occupy 0.72MB with 0.30MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-1.png | 170.55KB | 54.83KB | ▼ 67.85% |
assets/screenshot-3.png | 560.85KB | 225.58KB | ▼ 59.78% |
assets/play-button.png | 2.12KB | 2.19KB | 0.00% |