Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.56MB] [CPU: ▲1.07ms] Passed 4 tests
Server-side resources used by Front-End Managed Files Block
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.03 ▲0.57 | 47.10 ▲6.57 |
Dashboard /wp-admin | 3.86 ▲0.55 | 49.03 ▼3.79 |
Posts /wp-admin/edit.php | 3.97 ▲0.61 | 53.18 ▲4.12 |
Add New Post /wp-admin/post-new.php | 6.47 ▲0.58 | 100.47 ▼2.61 |
Media Library /wp-admin/upload.php | 3.78 ▲0.55 | 43.78 ▲10.13 |
Server storage [IO: ▲0.45MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 156 new files
Database: 2 new tables, 7 new options
New tables |
---|
wp_frontend_managed_files_block_files |
wp_frontend_managed_files_block_configurations |
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
widget_theysaidso_widget |
frontend_managed_files_block_db_version |
theysaidso_admin_options |
widget_recent-comments |
can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Front-End Managed Files Block
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,910 ▲175 | 13.80 ▼0.59 | 9.76 ▲7.88 | 43.02 ▲4.09 |
Dashboard /wp-admin | 2,211 ▲23 | 4.86 ▼0.04 | 98.46 ▼10.96 | 41.02 ▲1.69 |
Posts /wp-admin/edit.php | 2,088 ▼4 | 2.06 ▲0.04 | 39.99 ▼0.04 | 36.71 ▲2.09 |
Add New Post /wp-admin/post-new.php | 6,447 ▲4,914 | 28.45 ▲5.23 | 911.76 ▲286.76 | 38.69 ▼19.25 |
Media Library /wp-admin/upload.php | 1,390 ▲5 | 4.26 ▲0.03 | 95.00 ▼11.91 | 40.31 ▼5.87 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- The uninstall procedure failed, leaving 2 tables in the database
- wp_frontend_managed_files_block_files
- wp_frontend_managed_files_block_configurations
- This plugin did not uninstall successfully, leaving 7 options in the database
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- frontend_managed_files_block_db_version
- widget_theysaidso_widget
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 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 3× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/front-end-managed-files-block/public/views/file.blade.php
- > /wp-content/plugins/front-end-managed-files-block/public/views/error.blade.php
- > /wp-content/plugins/front-end-managed-files-block/public/views/file-list.blade.php
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Trait 'eftec\\bladeone\\BladeOneHtml' not found in wp-content/plugins/front-end-managed-files-block/vendor/BladeOne-3.45.1/lib/BladeOneHtmlBootstrap.php on line 30
- > 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 86% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Please fix the following attributes:
- Tags: Please reduce the number of tags, currently 11 tag instead of maximum 10
front-end-managed-files-block/frontend-managed-files-block.php 77% from 13 tests
The primary PHP file in "Front-End Managed Files Block" version 1.0.1 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("front-end-managed-files-block.php" instead of "frontend-managed-files-block.php")
- Description: Please don't use more than 140 characters for the plugin description (currently 150 characters long)
- 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 | Executable files are considered dangerous and should not be included with any WordPress plugin
There were no executable files found in this plugin6,274 lines of code in 39 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 18 | 745 | 2,604 | 3,566 |
JavaScript | 7 | 202 | 412 | 1,988 |
Markdown | 7 | 214 | 0 | 533 |
CSS | 2 | 13 | 0 | 66 |
JSON | 1 | 0 | 0 | 63 |
Blade | 3 | 16 | 0 | 42 |
XML | 1 | 7 | 1 | 16 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.34 |
Average class complexity | 32.50 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 271.00 |
Average method complexity | 2.16 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 12.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 6 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 360 | |
▷ Static methods | 13 | 3.61% |
▷ Public methods | 182 | 50.56% |
▷ Protected methods | 144 | 40.00% |
▷ Private methods | 34 | 9.44% |
Functions | 17 | |
▷ Named functions | 3 | 17.65% |
▷ Anonymous functions | 14 | 82.35% |
Constants | 6 | |
▷ Global constants | 1 | 16.67% |
▷ Class constants | 5 | 83.33% |
▷ Public constants | 5 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
105 compressed PNG files occupy 0.08MB
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
public/images/pl.png | 0.85KB | 0.80KB | ▼ 6.08% |
public/images/odt.png | 0.56KB | 0.51KB | ▼ 9.19% |
public/images/odg.png | 0.77KB | 0.72KB | ▼ 6.73% |
public/images/html.png | 0.73KB | 0.68KB | ▼ 7.09% |
public/images/xml.png | 0.46KB | 0.41KB | ▼ 11.79% |