Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.14MB] [CPU: ▼290.10ms] Passed 4 tests
Analyzing server-side resources used by EventMatches
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.73 ▲0.21 | 58.02 ▲6.75 |
| Dashboard /wp-admin | 3.57 ▲0.17 | 119.50 ▲84.67 |
| Posts /wp-admin/edit.php | 3.80 ▲0.16 | 40.22 ▲4.94 |
| Add New Post /wp-admin/post-new.php | 7.07 ▲0.08 | 101.57 ▼1,165.93 |
| Media Library /wp-admin/upload.php | 3.46 ▲0.16 | 25.12 ▼6.15 |
| Custom Events /wp-admin/edit.php?post_type=em_custom_event | 3.56 | 26.39 |
| Settings /wp-admin/admin.php?page=ccs-event-matches | 3.44 | 23.97 |
Server storage [IO: ▲0.41MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 27 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for EventMatches
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 4,006 ▲280 | 17.31 ▲1.26 | 21.66 ▲14.00 | 2.72 ▲0.26 |
| Dashboard /wp-admin | 2,965 ▲104 | 6.87 ▲0.78 | 135.61 ▼0.35 | 168.04 ▲3.59 |
| Posts /wp-admin/edit.php | 2,764 ▲76 | 3.23 ▼0.00 | 74.08 ▲8.09 | 199.67 ▲57.35 |
| Add New Post /wp-admin/post-new.php | 1,721 ▲10 | 19.67 ▼2.03 | 393.30 ▼56.90 | 166.32 ▲6.93 |
| Media Library /wp-admin/upload.php | 1,768 ▲70 | 5.93 ▲0.43 | 126.78 ▼15.88 | 183.83 ▼13.92 |
| Custom Events /wp-admin/edit.php?post_type=em_custom_event | 1,437 | 3.47 | 63.07 | 133.51 |
| Settings /wp-admin/admin.php?page=ccs-event-matches | 1,157 | 3.14 | 58.75 | 117.16 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
This plugin's uninstaller ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Cannot access self:: when no class scope is active in wp-content/plugins/eventmatches-calendar/views/setting.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/eventmatches-calendar/views/calendar.php:30
- > PHP Notice
Undefined variable: auth_token in wp-content/plugins/eventmatches-calendar/views/calendar.php on line 1
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
3 plugin tags: events, eventmatches, calendar
eventmatches-calendar/event-matches-calendar.php 77% from 13 tests
Analyzing the main PHP file in "EventMatches" version 1.0.5
You should first fix the following items:
- Domain Path: The domain path points to a folder that does not exist ("/languages")
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("eventmatches-calendar.php" instead of "event-matches-calendar.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Success! There were no dangerous files found in this plugin3,279 lines of code in 24 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 7 | 110 | 26 | 1,475 |
| CSS | 6 | 137 | 32 | 948 |
| PHP | 10 | 203 | 233 | 847 |
| Markdown | 1 | 4 | 0 | 9 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| Average class complexity | 12.71 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 45.00 |
| Average method complexity | 3.22 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 33.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 7 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 7 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 37 | |
| ▷ Static methods | 9 | 24.32% |
| ▷ Public methods | 34 | 91.89% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 3 | 8.11% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 12 | |
| ▷ Global constants | 1 | 8.33% |
| ▷ Class constants | 11 | 91.67% |
| ▷ Public constants | 11 | 100.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