Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▲3.42MB] [CPU: ▲12.03ms] Passed 4 tests
Server-side resources used by Protect Wordpress Videos
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 6.88 ▲3.42 | 62.36 ▲18.75 |
| Dashboard /wp-admin | 6.72 ▲3.41 | 67.07 ▲12.59 |
| Posts /wp-admin/edit.php | 6.83 ▲3.47 | 66.58 ▲14.97 |
| Add New Post /wp-admin/post-new.php | 9.32 ▲3.43 | 105.87 ▲1.82 |
| Media Library /wp-admin/upload.php | 6.64 ▲3.41 | 66.99 ▲30.34 |
Server storage [IO: ▲10.70MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 1,103 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| puv_customer_guid |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
| puv_mfl |
Browser metrics Passed 4 tests
An overview of browser requirements for Protect Wordpress Videos
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,947 ▲186 | 14.23 ▼0.26 | 9.84 ▲8.20 | 37.57 ▼7.42 |
| Dashboard /wp-admin | 2,217 ▲43 | 5.06 ▼0.52 | 96.46 ▲5.86 | 36.86 ▲0.22 |
| Posts /wp-admin/edit.php | 2,119 ▲19 | 2.50 ▲0.51 | 36.55 ▲0.35 | 34.76 ▼3.27 |
| Add New Post /wp-admin/post-new.php | 1,380 ▼148 | 17.39 ▼5.61 | 562.28 ▼122.98 | 27.15 ▼35.61 |
| Media Library /wp-admin/upload.php | 1,422 ▲25 | 4.64 ▲0.38 | 112.03 ▲10.70 | 49.75 ▲6.31 |
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 8 options in the database
- puv_mfl
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- puv_customer_guid
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
SRP 0% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 2× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/protect-wp-videos/public/partials/protect-ur-videos-public-display.php
- > /wp-content/plugins/protect-wp-videos/admin/partials/protect-ur-videos-admin-display.php
- 414× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'Aws\\CacheInterface' not found in wp-content/plugins/protect-wp-videos/vendor/aws/aws-sdk-php/src/PsrCacheAdapter.php:6
- > PHP Fatal error
Uncaught Error: Class 'Aws\\Exception\\AwsException' not found in wp-content/plugins/protect-wp-videos/vendor/aws/aws-sdk-php/src/Inspector/Exception/InspectorException.php:9
- > PHP Fatal error
Uncaught Error: Class 'Aws\\Exception\\AwsException' not found in wp-content/plugins/protect-wp-videos/vendor/aws/aws-sdk-php/src/ACMPCA/Exception/ACMPCAException.php:9
- > PHP Fatal error
Uncaught Error: Class 'Aws\\Exception\\AwsException' not found in wp-content/plugins/protect-wp-videos/vendor/aws/aws-sdk-php/src/AlexaForBusiness/Exception/AlexaForBusinessException.php:9
- > PHP Fatal error
Uncaught Error: Interface 'Aws\\AwsClientInterface' not found in wp-content/plugins/protect-wp-videos/vendor/aws/aws-sdk-php/src/AwsClient.php:13
- > PHP Fatal error
Uncaught Error: Interface 'Aws\\CommandInterface' not found in wp-content/plugins/protect-wp-videos/vendor/aws/aws-sdk-php/src/Command.php:7
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromisorInterface' not found in wp-content/plugins/protect-wp-videos/vendor/aws/aws-sdk-php/src/Waiter.php:22
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\UriInterface' not found in wp-content/plugins/protect-wp-videos/vendor/guzzlehttp/psr7/src/Uri.php:13
- > PHP Fatal error
Uncaught Error: Class 'Aws\\AwsClient' not found in wp-content/plugins/protect-wp-videos/vendor/aws/aws-sdk-php/src/MigrationHub/MigrationHubClient.php:41
- > PHP Fatal error
Uncaught Error: Class 'Aws\\AwsClient' not found in wp-content/plugins/protect-wp-videos/vendor/aws/aws-sdk-php/src/S3/S3Client.php:177
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
4 plugin tags: posts, content, private, videos
protect-wp-videos/protect-ur-videos.php 85% from 13 tests
The main file in "Protect Wordpress Videos" v. 1.1.4 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("protect-wp-videos.php" instead of "protect-ur-videos.php")
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
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
No dangerous file extensions were detected38,563 lines of code in 1,087 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1,009 | 5,269 | 23,225 | 26,675 |
| JSON | 31 | 8 | 0 | 6,483 |
| Markdown | 13 | 993 | 0 | 3,315 |
| JavaScript | 24 | 375 | 270 | 1,978 |
| reStructuredText | 1 | 35 | 29 | 59 |
| make | 2 | 10 | 0 | 22 |
| XML | 1 | 3 | 0 | 14 |
| Bourne Shell | 2 | 2 | 0 | 12 |
| CSS | 4 | 1 | 14 | 5 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.36 |
| Average class complexity | 5.81 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 81.00 |
| Average method complexity | 2.39 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 27.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 315 | |
| Interfaces | 27 | |
| Traits | 13 | |
| Classes | 523 | |
| ▷ Abstract classes | 8 | 1.53% |
| ▷ Concrete classes | 515 | 98.47% |
| ▷ Final classes | 10 | 1.94% |
| Methods | 1,935 | |
| ▷ Static methods | 221 | 11.42% |
| ▷ Public methods | 1,358 | 70.18% |
| ▷ Protected methods | 89 | 4.60% |
| ▷ Private methods | 488 | 25.22% |
| Functions | 375 | |
| ▷ Named functions | 74 | 19.73% |
| ▷ Anonymous functions | 301 | 80.27% |
| Constants | 147 | |
| ▷ Global constants | 1 | 0.68% |
| ▷ Class constants | 146 | 99.32% |
| ▷ Public constants | 146 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| admin/js/pur-video-js.png | 22.10KB | 10.23KB | ▼ 53.73% |