Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼6.29ms] Passed 4 tests
An overview of server-side resources used by Avayo ticketshop
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.04 | 40.55 ▲3.92 |
| Dashboard /wp-admin | 3.35 ▲0.04 | 45.14 ▼3.38 |
| Posts /wp-admin/edit.php | 3.40 ▲0.04 | 43.89 ▼3.29 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 82.51 ▼17.11 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 34.97 ▼1.36 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 8 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Avayo ticketshop
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,833 ▲72 | 14.24 ▼0.11 | 2.10 ▲0.54 | 42.60 ▲0.43 |
| Dashboard /wp-admin | 2,213 ▲36 | 5.56 ▼0.06 | 81.59 ▼4.79 | 65.29 ▲24.27 |
| Posts /wp-admin/edit.php | 2,112 ▲12 | 1.96 ▼0.01 | 35.55 ▲0.09 | 35.57 ▼3.89 |
| Add New Post /wp-admin/post-new.php | 1,692 ▲166 | 22.38 ▼0.77 | 760.18 ▲54.27 | 56.88 ▲4.14 |
| Media Library /wp-admin/upload.php | 1,418 ▲18 | 4.21 ▲0.01 | 97.15 ▲2.52 | 68.37 ▲25.17 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
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)
Everything seems fine, however this is by no means an exhaustive test
SRP 0% 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 return non-empty strings:
- > /wp-content/plugins/avayo-ticketshop/avayo.php
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/avayo-ticketshop/includes/shortcode.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/avayo-ticketshop/includes/initialize.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
8 plugin tags: etickets, tickets, events, kaartverkoop, registration...
avayo-ticketshop/avayo.php 85% from 13 tests
"Avayo ticketshop" version 1.1.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("avayo-ticketshop.php" instead of "avayo.php")
- 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
Good job! No executable or dangerous file extensions detected316 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 33 | 11 | 243 |
| JavaScript | 1 | 9 | 0 | 43 |
| CSS | 1 | 5 | 0 | 30 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.39 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 7 | |
| ▷ Named functions | 6 | 85.71% |
| ▷ Anonymous functions | 1 | 14.29% |
| 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
2 compressed PNG files occupy 0.00MB
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/img/avayo.png | 3.40KB | 3.33KB | ▼ 1.84% |
| assets/img/icon.png | 1.18KB | 0.86KB | ▼ 27.22% |