Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
You still need to fix the following installer errors
- This plugin did not install gracefully
- > Parse error in wp-content/plugins/ebot-matches-viewer/ebot-matches-viewer.php+288
syntax error, unexpected end of file
Server metrics [RAM: ▲0.00MB] [CPU: ▼1.68ms] Passed 4 tests
This is a short check of server-side resources used by eBot Matches Viewer
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 39.85 ▲0.83 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 53.13 ▼2.44 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 55.60 ▼3.47 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 91.44 ▼1.65 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 49.42 ▲13.92 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
| db_upgraded |
Browser metrics Passed 4 tests
eBot Matches Viewer: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲11 | 13.20 ▼1.28 | 4.91 ▲2.44 | 41.27 ▲0.45 |
| Dashboard /wp-admin | 2,200 ▼6 | 4.84 ▼1.01 | 104.89 ▼6.21 | 40.77 ▲2.12 |
| Posts /wp-admin/edit.php | 2,089 ▲3 | 2.04 ▲0.01 | 36.51 ▼1.21 | 32.50 ▼2.35 |
| Add New Post /wp-admin/post-new.php | 1,546 ▲13 | 23.97 ▲0.67 | 661.16 ▼117.80 | 52.56 ▼12.74 |
| Media Library /wp-admin/upload.php | 1,382 ▼3 | 4.20 ▼0.02 | 94.63 ▼7.92 | 41.11 ▼1.60 |
Uninstaller [IO: ✅] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% 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 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Parse error
syntax error, unexpected end of file in wp-content/plugins/ebot-matches-viewer/ebot-matches-viewer.php on line 288
- > PHP Parse 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)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that need to be fixed:
- License: Empty string
ebot-matches-viewer/ebot-matches-viewer.php Passed 13 tests
Analyzing the main PHP file in "eBot Matches Viewer" version 1.6
82 characters long description:
Un simple widget pour intégrer les matchs de l'eBot sur votre site communautaire.
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
Success! There were no dangerous files found in this plugin1 line of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 0 | 0 | 1 |
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.10 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 3.67 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 4 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 4 | 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 | 0 | |
| ▷ Global constants | 0 | 0.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
PNG images were not found in this plugin