Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼2.86ms] Passed 4 tests
An overview of server-side resources used by MD5 Media Renamer
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 44.23 ▼0.41 |
Dashboard /wp-admin | 3.32 ▲0.02 | 50.70 ▲0.69 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 48.05 ▼1.05 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 86.30 ▼10.67 |
Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 34.74 ▲1.00 |
Server storage [IO: ▲0.22MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 20 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for MD5 Media Renamer
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 14.50 ▲0.12 | 1.74 ▼0.20 | 43.40 ▼3.66 |
Dashboard /wp-admin | 2,206 ▲21 | 4.87 ▼1.04 | 108.38 ▲5.11 | 42.85 ▼2.73 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.01 ▲0.00 | 34.37 ▼1.70 | 33.36 ▼0.63 |
Add New Post /wp-admin/post-new.php | 1,542 ▲9 | 18.56 ▼4.62 | 658.70 ▼43.72 | 51.22 ▼6.70 |
Media Library /wp-admin/upload.php | 1,382 ▼3 | 4.24 ▲0.02 | 99.56 ▼11.14 | 41.94 ▼4.57 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for 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
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/md5-media-renamer/md5-media-renamer.php
- 38× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Warning
Use of undefined constant ML79_PLUGIN_AUTHOR_URL - assumed 'ML79_PLUGIN_AUTHOR_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/md5-media-renamer/notices/notice-activate.php on line 22
- > PHP Warning
Use of undefined constant ML79_PLUGIN_URL - assumed 'ML79_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/md5-media-renamer/notices/notice-activate.php on line 125
- > PHP Warning
Use of undefined constant ML79_PLUGIN_URL - assumed 'ML79_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/md5-media-renamer/notices/notice-activate.php on line 111
- > PHP Warning
Use of undefined constant ML79_PLUGIN_URL - assumed 'ML79_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/md5-media-renamer/notices/notice-activate.php on line 90
- > PHP Warning
Use of undefined constant ML79_PLUGIN_URL - assumed 'ML79_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/md5-media-renamer/notices/notice-activate.php on line 122
- > PHP Warning
Use of undefined constant ML79_PLUGIN_URL - assumed 'ML79_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/md5-media-renamer/notices/notice-activate.php on line 99
- > PHP Warning
Use of undefined constant ML79_PLUGIN_URL - assumed 'ML79_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/md5-media-renamer/notices/notice-activate.php on line 96
- > PHP Warning
Use of undefined constant ML79_PLUGIN_URL - assumed 'ML79_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/md5-media-renamer/notices/notice-activate.php on line 85
- > PHP Warning
Use of undefined constant ML79_PLUGIN_URL - assumed 'ML79_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/md5-media-renamer/notices/notice-activate.php on line 47
- > PHP Warning
Use of undefined constant ML79_PLUGIN_URL - assumed 'ML79_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/md5-media-renamer/notices/notice-activate.php on line 114
- > PHP Warning
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)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Attributes that need to be fixed:
- Donate link: Please fix this invalid url: ""
md5-media-renamer/md5-media-renamer.php Passed 13 tests
"MD5 Media Renamer" version 1.5's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
134 characters long description:
Sanitize and rename automatically media files during upload using PHP time() as prefix and the file name encrypted in MD5() as suffix.
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 detected202 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 23 | 53 | 202 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.59 |
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 | 9 | |
▷ Global constants | 9 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
13 PNG files occupy 0.20MB with 0.10MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
cpanel/images/notices/logo.png | 13.63KB | 6.03KB | ▼ 55.74% |
cpanel/images/notices/tumblr.png | 4.37KB | 1.59KB | ▼ 63.70% |
cpanel/images/notices/googleplus.png | 2.71KB | 1.70KB | ▼ 37.16% |
cpanel/images/notices/stumble.png | 3.09KB | 1.72KB | ▼ 44.34% |
cpanel/images/notices/linkedin.png | 2.35KB | 1.55KB | ▼ 34.15% |