Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.37MB] [CPU: ▼11.08ms] Passed 4 tests
An overview of server-side resources used by Events Calendar by FooEvents
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.08 ▲0.62 | 44.04 ▲3.50 |
Dashboard /wp-admin | 3.73 ▲0.39 | 39.34 ▼15.17 |
Posts /wp-admin/edit.php | 3.86 ▲0.50 | 42.96 ▼6.99 |
Add New Post /wp-admin/post-new.php | 5.97 ▲0.09 | 75.86 ▼22.83 |
Media Library /wp-admin/upload.php | 3.74 ▲0.51 | 36.43 ▲0.69 |
Calendar Settings /wp-admin/admin.php?page=fooevents-settings | 3.71 | 39.32 |
Server storage [IO: ▲2.23MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 59 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_fooevents_calendar_widget |
widget_recent-comments |
db_upgraded |
widget_recent-posts |
can_compress_scripts |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by Events Calendar by FooEvents
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,962 ▲215 | 15.06 ▲0.68 | 31.68 ▲30.02 | 36.51 ▼7.68 |
Dashboard /wp-admin | 2,251 ▲80 | 4.97 ▼0.64 | 98.68 ▲7.21 | 40.51 ▼0.55 |
Posts /wp-admin/edit.php | 2,164 ▲64 | 2.33 ▲0.32 | 43.68 ▲1.61 | 35.68 ▼1.13 |
Add New Post /wp-admin/post-new.php | 5,136 ▲3,599 | 23.18 ▲0.11 | 723.39 ▲34.30 | 42.80 ▼8.86 |
Media Library /wp-admin/upload.php | 1,456 ▲56 | 4.41 ▲0.23 | 100.93 ▲2.47 | 42.04 ▼0.45 |
Calendar Settings /wp-admin/admin.php?page=fooevents-settings | 1,206 | 2.17 | 33.72 | 38.21 |
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 did not uninstall successfully, leaving 7 options in the database
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- widget_fooevents_calendar_widget
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
These server-side errors were triggered
- > GET request to /wp-admin/admin.php?page=fooevents-settings
- > Warning in wp-content/plugins/fooevents-calendar/class-fooevents-calendar.php+3242
session_start(): Cannot start session when headers already sent
SRP 50% 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 take a closer look at the following
- 11× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr_e() in wp-content/plugins/fooevents-calendar/templates/eventbrite-options.php:13
- > PHP Fatal error
Uncaught Error: Call to undefined function get_the_permalink() in wp-content/plugins/fooevents-calendar/templates/event.php:16
- > PHP Fatal error
require_once(): Failed opening required 'HttpClient.php' (include_path='.:/usr/share/php') in wp-content/plugins/fooevents-calendar/vendors/eventbrite/tests/ClientTest.php on line 3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr_e() in wp-content/plugins/fooevents-calendar/templates/calendar-options-layout.php:16
- > PHP Warning
require_once(HttpClient.php): failed to open stream: No such file or directory in wp-content/plugins/fooevents-calendar/vendors/eventbrite/tests/ClientTest.php on line 3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr_e() in wp-content/plugins/fooevents-calendar/templates/eventmetabox.php:14
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr_e() in wp-content/plugins/fooevents-calendar/templates/list-of-events.php:42
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/fooevents-calendar/templates/calendar.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function settings_fields() in wp-content/plugins/fooevents-calendar/templates/calendar-options.php:11
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/fooevents-calendar/classes/class-fooevents-calendar-widget.php:10
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Please fix the following attributes:
- Screenshots: Please add an image for screenshot #7 (Using the FooEvents Calendar shortcode)
fooevents-calendar/fooevents-calendar.php Passed 13 tests
"Events Calendar by FooEvents" version 1.6.52's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
105 characters long description:
Display your events in a stylish calendar on your WordPress website using simple short codes and widgets.
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
No dangerous file extensions were detected22,411 lines of code in 41 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 7 | 1,102 | 2,439 | 17,707 |
PHP | 16 | 1,336 | 1,132 | 3,016 |
CSS | 13 | 342 | 373 | 1,333 |
PO File | 1 | 120 | 123 | 283 |
Markdown | 1 | 16 | 0 | 35 |
YAML | 1 | 4 | 0 | 20 |
JSON | 1 | 0 | 0 | 9 |
XML | 1 | 0 | 0 | 8 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.40 |
Average class complexity | 70.17 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 389.00 |
Average method complexity | 3.41 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 56.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 6 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 6 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 172 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 168 | 97.67% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 4 | 2.33% |
Functions | 5 | |
▷ Named functions | 5 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 2 | |
▷ Global constants | 1 | 50.00% |
▷ Class constants | 1 | 50.00% |
▷ Public constants | 1 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
10 PNG files occupy 0.71MB with 0.31MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-3.png | 113.51KB | 62.85KB | ▼ 44.63% |
screenshot-4.png | 112.33KB | 69.27KB | ▼ 38.33% |
screenshot-1.png | 112.90KB | 62.81KB | ▼ 44.37% |
screenshot-6.png | 109.49KB | 63.25KB | ▼ 42.24% |
images/fooevents-logo.png | 4.26KB | 2.07KB | ▼ 51.46% |