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.03MB] [CPU: ▼3.09ms] Passed 4 tests
Server-side resources used by Wordpress logo changer
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.02 | 35.42 ▼8.45 |
| Dashboard /wp-admin | 3.34 ▲0.03 | 49.30 ▼3.24 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 48.72 ▲0.77 |
| Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 95.10 ▼1.44 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 37.65 ▲2.98 |
| Wordpress Logo Changer /wp-admin/admin.php?page=mlchanger_setting | 3.29 | 40.76 |
Server storage [IO: ▲0.25MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 25 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
Wordpress logo changer: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,837 ▲102 | 13.18 ▼1.47 | 1.70 ▼0.34 | 42.17 ▼9.59 |
| Dashboard /wp-admin | 2,229 ▲41 | 5.09 ▼0.79 | 101.84 ▲2.18 | 38.86 ▼5.26 |
| Posts /wp-admin/edit.php | 2,112 ▲20 | 2.03 ▼0.02 | 38.98 ▼2.08 | 35.89 ▼2.01 |
| Add New Post /wp-admin/post-new.php | 1,546 ▲13 | 18.45 ▼4.75 | 605.19 ▲18.99 | 60.70 ▲8.44 |
| Media Library /wp-admin/upload.php | 1,408 ▲20 | 4.19 ▼0.01 | 93.58 ▼4.02 | 41.44 ▼7.32 |
| Wordpress Logo Changer /wp-admin/admin.php?page=mlchanger_setting | 1,208 | 3.19 | 41.65 | 62.58 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP 0% 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
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/mimo-logo-changer/logo-changer.php
- 22× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Warning
Use of undefined constant MLCHANGER_CORE_DIR - assumed 'MLCHANGER_CORE_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/mimo-logo-changer/core/autoload.php on line 5
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/mimo-logo-changer/admin/page.php:3
- > PHP Warning
include(MLCHANGER_CORE_DIRimg_changer.php): failed to open stream: No such file or directory in wp-content/plugins/mimo-logo-changer/core/autoload.php on line 3
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/mimo-logo-changer/core/autoload.php:8
- > PHP Warning
include(): Failed opening 'MLCHANGER_CORE_DIRtitle_changer.php' for inclusion (include_path='.:/usr/share/php') in wp-content/plugins/mimo-logo-changer/core/autoload.php on line 5
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/mimo-logo-changer/core/img_changer.php:3
- > PHP Warning
include(): Failed opening 'MLCHANGER_CORE_DIRmessage_changer.php' for inclusion (include_path='.:/usr/share/php') in wp-content/plugins/mimo-logo-changer/core/autoload.php on line 6
- > PHP Warning
Use of undefined constant MLCHANGER_CORE_DIR - assumed 'MLCHANGER_CORE_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/mimo-logo-changer/core/autoload.php on line 3
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/mimo-logo-changer/templates/main-page-html.php:2
- > PHP Warning
include(): Failed opening 'MLCHANGER_CORE_DIRurl_changer.php' for inclusion (include_path='.:/usr/share/php') in wp-content/plugins/mimo-logo-changer/core/autoload.php on line 4
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need to be fixed:
- Screenshots: These screenshots require images: #1 (mimo logo changer configuration part 1), #2 (mimo logo changer configuration part 2 - use default message style), #3 (Wordpress Login Page with default message style), #4 (mimo logo changer configuration use custom HTML), #5 (Wordpress Login Page with custom HTML)
mimo-logo-changer/logo-changer.php 92% from 13 tests
The principal PHP file in "Wordpress logo changer" v. 1.4.1 is loaded by WordPress automatically on each request
It is important to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("mimo-logo-changer.php" instead of "logo-changer.php")
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 detected501 lines of code in 15 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 11 | 77 | 29 | 311 |
| PO File | 2 | 50 | 51 | 143 |
| CSS | 1 | 13 | 9 | 28 |
| JavaScript | 1 | 2 | 0 | 19 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.27 |
| 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 | 9 | |
| ▷ Named functions | 9 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 8 | |
| ▷ Global constants | 8 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.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
5 PNG files occupy 0.21MB with 0.14MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-5.png | 34.18KB | 13.93KB | ▼ 59.23% |
| screenshot-3.png | 33.19KB | 13.42KB | ▼ 59.56% |
| screenshot-2.png | 29.90KB | 8.40KB | ▼ 71.92% |
| screenshot-1.png | 90.95KB | 26.20KB | ▼ 71.19% |
| screenshot-4.png | 26.47KB | 8.26KB | ▼ 68.80% |