88% avayo-ticketshop

Code Review | Avayo ticketshop

WordPress plugin Avayo ticketshop scored 88% from 54 tests.

About plugin

  • Plugin page: avayo-ticketshop
  • Plugin version: 1.0.3
  • PHP version: 7.4.16
  • WordPress compatibility: 4.0-5.7
  • WordPress version: 5.8.1
  • First release: Feb 22, 2018
  • Latest release: Mar 10, 2021
  • Number of updates: 9
  • Update frequency: every 123.8 days
  • Top authors: avayo (100%)

Code review

54 tests

User reviews

1 review

Install metrics

20+ active / 612 total downloads

Benchmarks

Plugin footprint Passed 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.03MB] [CPU: ▼140.54ms] Passed 4 tests

An overview of server-side resources used by Avayo ticketshop
This plugin has minimal impact on server resources
PageMemory (MB)CPU Time (ms)
Home /2.87 ▲0.0334.31 ▲1.55
Dashboard /wp-admin3.09 ▲0.0441.04 ▲3.91
Posts /wp-admin/edit.php3.15 ▲0.0343.93 ▼0.64
Add New Post /wp-admin/post-new.php5.45 ▲0.0189.66 ▼566.98
Media Library /wp-admin/upload.php3.04 ▲0.0333.76 ▲7.72

Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests

Filesystem and database footprint
This plugin installed successfully
Filesystem: 10 new files
Database: no new tables, no new options

Browser metrics Passed 4 tests

A check of browser resources used by Avayo ticketshop
This plugin has a minimal impact on browser resources
PageNodesMemory (MB)Script (ms)Layout (ms)
Home /3,732 ▲13615.92 ▲0.2010.10 ▲0.3047.99 ▲4.02
Dashboard /wp-admin2,982 ▲515.89 ▼0.10133.33 ▼12.51139.35 ▲23.43
Posts /wp-admin/edit.php2,759 ▲202.59 ▼0.1165.13 ▼0.7590.24 ▲5.70
Add New Post /wp-admin/post-new.php1,885 ▲38719.17 ▲0.32380.52 ▼1.62106.91 ▼3.83
Media Library /wp-admin/upload.php1,767 ▼435.02 ▼0.00139.16 ▼17.14143.52 ▲24.56

Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests

🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Uninstaller ran successfully

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

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: kaartverkoop, avayo, ticketing, ticket sales, etickets...

avayo-ticketshop/avayo.php 85% from 13 tests

"Avayo ticketshop" version 1.0.3'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:
  • 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
  • Main file name: The principal plugin file should be the same as the plugin slug ("avayo-ticketshop.php" instead of "avayo.php")

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 detected264 lines of code in 5 files:
LanguageFilesBlank linesComment linesLines of code
PHP32911203
JavaScript18031
CSS15030

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 code0.38
Average class complexity0.00
▷ Minimum class complexity0.00
▷ Maximum class complexity0.00
Average method complexity0.00
▷ Minimum method complexity0.00
▷ Maximum method complexity0.00
Code structure
Namespaces0
Interfaces0
Traits0
Classes0
▷ Abstract classes00.00%
▷ Concrete classes00.00%
▷ Final classes00.00%
Methods0
▷ Static methods00.00%
▷ Public methods00.00%
▷ Protected methods00.00%
▷ Private methods00.00%
Functions7
▷ Named functions685.71%
▷ Anonymous functions114.29%
Constants0
▷ Global constants00.00%
▷ Class constants00.00%
▷ Public constants00.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
4 PNG files occupy 0.07MB with 0.03MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant
FileSize - originalSize - compressedSavings
assets/icon-128x128.png18.01KB7.10KB▼ 60.61%
assets/img/icon.png1.18KB0.86KB▼ 27.22%
assets/icon-256x256.png50.03KB18.69KB▼ 62.65%
assets/img/avayo.png3.40KB3.33KB▼ 1.84%