Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.12MB] [CPU: ▼4.52ms] Passed 4 tests
A check of server-side resources used by Evangelische Termine für The Events Calendar
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.59 ▲0.12 | 41.35 ▼1.77 |
Dashboard /wp-admin | 3.49 ▲0.15 | 72.53 ▲9.03 |
Posts /wp-admin/edit.php | 3.53 ▲0.17 | 51.84 ▲3.43 |
Add New Post /wp-admin/post-new.php | 6.00 ▲0.11 | 83.10 ▼18.61 |
Media Library /wp-admin/upload.php | 3.34 ▲0.11 | 35.98 ▼1.11 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 9 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
db_upgraded |
widget_theysaidso_widget |
widget_recent-comments |
widget_recent-posts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Evangelische Termine für The Events Calendar: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,801 ▲40 | 14.20 ▼0.15 | 1.65 ▲0.08 | 39.11 ▼3.24 |
Dashboard /wp-admin | 2,207 ▲27 | 5.65 ▼0.02 | 91.28 ▼7.60 | 39.32 ▼5.43 |
Posts /wp-admin/edit.php | 2,109 ▲9 | 1.99 ▼0.03 | 39.12 ▲4.34 | 38.69 ▲4.24 |
Add New Post /wp-admin/post-new.php | 1,538 ▲10 | 22.94 ▼0.41 | 653.44 ▲16.71 | 53.28 ▲3.98 |
Media Library /wp-admin/upload.php | 1,415 ▲15 | 4.11 ▼0.12 | 96.25 ▲2.31 | 45.41 ▲5.78 |
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
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% 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 items
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/evangelische-termine-for-the-events-calendar/assets/inc/yspeechetftec-style-functions.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function get_the_ID() in wp-content/plugins/evangelische-termine-for-the-events-calendar/src/views/v2/list/event-target-group.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% 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
These attributes need your attention:
- Screenshots: These screenshots require images: #1 (Import Einstellungen), #2 (Lizenz Einstellungen)
evangelische-termine-for-the-events-calendar/evangelische-termine-for-the-events-calendar.php 92% from 13 tests
"Evangelische Termine für The Events Calendar" version 0.0.6's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
The following require your attention:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected614 lines of code in 7 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 7 | 126 | 185 | 614 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.43 |
Average class complexity | 17.50 |
▷ Minimum class complexity | 7.00 |
▷ Maximum class complexity | 28.00 |
Average method complexity | 3.20 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 8.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 16 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 16 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 14 | |
▷ Named functions | 13 | 92.86% |
▷ Anonymous functions | 1 | 7.14% |
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
No PNG images were found in this plugin