Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.11MB] [CPU: ▼6.34ms] Passed 4 tests
Analyzing server-side resources used by MetaTrader Web Terminal
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.58 ▲0.12 | 43.88 ▲5.37 |
| Dashboard /wp-admin | 3.41 ▲0.11 | 44.57 ▼5.12 |
| Posts /wp-admin/edit.php | 3.53 ▲0.17 | 47.70 ▼4.76 |
| Add New Post /wp-admin/post-new.php | 5.99 ▲0.10 | 95.35 ▼12.14 |
| Media Library /wp-admin/upload.php | 3.34 ▲0.10 | 36.77 ▼3.34 |
Server storage [IO: ▲0.35MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 33 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| widget_metatrader_widget |
| widget_recent-comments |
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
MetaTrader Web Terminal: an overview of browser usage
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,845 ▲110 | 13.26 ▼1.12 | 5.03 ▲3.23 | 35.98 ▼7.03 |
| Dashboard /wp-admin | 2,208 ▲20 | 4.86 ▼1.04 | 107.32 ▼2.18 | 36.43 ▼7.07 |
| Posts /wp-admin/edit.php | 2,094 ▲8 | 2.01 ▲0.02 | 38.57 ▼1.46 | 36.18 ▲2.14 |
| Add New Post /wp-admin/post-new.php | 6,592 ▲5,078 | 29.35 ▲11.85 | 838.93 ▲151.83 | 52.97 ▼4.80 |
| Media Library /wp-admin/upload.php | 1,387 ▼1 | 4.28 ▲0.08 | 96.79 ▼18.26 | 41.65 ▼6.89 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 7 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- widget_metatrader_widget
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
- widget_recent-comments
Smoke tests 50% 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 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
Please fix the following items
- 3× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/metatrader-web-terminal/inc/class.metatrader.php
- > /wp-content/plugins/metatrader-web-terminal/metatrader.php
- > /wp-content/plugins/metatrader-web-terminal/inc/class.shortcode.php
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/metatrader-web-terminal/views/widget-settings.php:3
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/metatrader-web-terminal/inc/class.widget.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
5 plugin tags: mt5, webterminal, trading, metatrader, mt4
metatrader-web-terminal/metatrader.php 85% from 13 tests
"MetaTrader Web Terminal" version 1.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("metatrader-web-terminal.php" instead of "metatrader.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; 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
Good job! No executable or dangerous file extensions detected8,642 lines of code in 26 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JSON | 5 | 0 | 0 | 7,322 |
| PHP | 7 | 74 | 25 | 616 |
| JavaScript | 5 | 42 | 30 | 580 |
| PO File | 1 | 32 | 53 | 98 |
| Sass | 2 | 0 | 0 | 12 |
| SVG | 3 | 0 | 0 | 7 |
| HTML | 1 | 0 | 0 | 4 |
| CSS | 2 | 0 | 11 | 3 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.28 |
| Average class complexity | 14.75 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 39.00 |
| Average method complexity | 3.20 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 17.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 25 | |
| ▷ Static methods | 3 | 12.00% |
| ▷ Public methods | 25 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 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
No PNG images were found in this plugin