Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.05MB] [CPU: ▲0.56ms] Passed 4 tests
A check of server-side resources used by Balfolk Tickets
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.78 ▲0.05 | 45.53 ▲2.94 |
Dashboard /wp-admin | 3.68 ▲0.11 | 53.26 ▲1.75 |
Posts /wp-admin/edit.php | 3.73 ▲0.05 | 54.15 ▲1.37 |
Add New Post /wp-admin/post-new.php | 6.20 ▲0.05 | 91.39 ▲0.25 |
Media Library /wp-admin/upload.php | 3.54 ▲0.05 | 39.46 ▼1.15 |
Server storage [IO: ▲9.62MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 260 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-posts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Balfolk Tickets
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,801 ▲40 | 14.28 ▼0.28 | 1.75 ▲0.11 | 44.08 ▲2.50 |
Dashboard /wp-admin | 2,204 ▲27 | 5.62 ▼0.08 | 101.10 ▲13.82 | 58.18 ▲15.89 |
Posts /wp-admin/edit.php | 2,113 ▲10 | 2.01 ▼0.03 | 38.51 ▼0.61 | 33.34 ▼4.49 |
Add New Post /wp-admin/post-new.php | 1,538 ▲12 | 17.46 ▼0.03 | 676.75 ▼29.22 | 49.40 ▼11.92 |
Media Library /wp-admin/upload.php | 1,415 ▲18 | 4.24 ▼0.02 | 100.33 ▼16.98 | 48.78 ▼0.72 |
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
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
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
The following issues need your attention
- 122× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'FontLib\\TrueType\\File' not found in wp-content/plugins/balfolk-tickets/dompdf/lib/php-font-lib/src/FontLib/OpenType/File.php:16
- > PHP Fatal error
Uncaught Error: Class 'Svg\\Tag\\AbstractTag' not found in wp-content/plugins/balfolk-tickets/dompdf/lib/php-svg-lib/src/Svg/Tag/Image.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function get_header() in wp-content/plugins/balfolk-tickets/tickets-template.php:176
- > PHP Fatal error
Uncaught Error: Class 'Svg\\Tag\\AbstractTag' not found in wp-content/plugins/balfolk-tickets/dompdf/lib/php-svg-lib/src/Svg/Document.php:30
- > PHP Fatal error
Uncaught Error: Class 'Dompdf\\FrameReflower\\AbstractFrameReflower' not found in wp-content/plugins/balfolk-tickets/dompdf/src/FrameReflower/TableRow.php:20
- > PHP Fatal error
Uncaught Error: Class 'Dompdf\\Renderer\\Block' not found in wp-content/plugins/balfolk-tickets/dompdf/src/Renderer/TableRowGroup.php:17
- > PHP Fatal error
Uncaught Error: Class 'FontLib\\Table\\Table' not found in wp-content/plugins/balfolk-tickets/dompdf/lib/php-font-lib/src/FontLib/Table/Type/post.php:18
- > PHP Fatal error
Uncaught Error: Class 'Dompdf\\FrameDecorator\\AbstractFrameDecorator' not found in wp-content/plugins/balfolk-tickets/dompdf/src/FrameDecorator/TableRow.php:19
- > PHP Fatal error
Uncaught Error: Class 'Dompdf\\FrameDecorator\\AbstractFrameDecorator' not found in wp-content/plugins/balfolk-tickets/dompdf/src/FrameDecorator/Inline.php:22
- > PHP Fatal error
Uncaught Error: Class 'FontLib\\Table\\Table' not found in wp-content/plugins/balfolk-tickets/dompdf/lib/php-font-lib/src/FontLib/Table/Type/loca.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There were no browser issues found
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 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
5 plugin tags: bal folk, ticketing, tickets, event, balfolk
balfolk-tickets/balfolk-tickets.php Passed 13 tests
The main file in "Balfolk Tickets" v. 1.3.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
45 characters long description:
WordPress ticketing plugin for balfolk events
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Good job! No executable or dangerous file extensions detected33,942 lines of code in 190 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 169 | 8,164 | 15,341 | 32,797 |
CSS | 3 | 127 | 44 | 515 |
Markdown | 5 | 86 | 0 | 231 |
XML | 4 | 3 | 2 | 191 |
JSON | 4 | 0 | 0 | 115 |
YAML | 3 | 15 | 4 | 52 |
JavaScript | 1 | 4 | 0 | 24 |
HTML | 1 | 0 | 0 | 17 |
PHP code 50% from 2 tests
This is a very shot review of cyclomatic complexity and code structure
These items need your attention
- Cyclomatic complexity of methods should be reduced to less than 100 (currently 652)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.43 |
Average class complexity | 37.81 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 765.00 |
Average method complexity | 4.54 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 652.00 |
Code structure | ||
---|---|---|
Namespaces | 25 | |
Interfaces | 2 | |
Traits | 0 | |
Classes | 162 | |
▷ Abstract classes | 7 | 4.32% |
▷ Concrete classes | 155 | 95.68% |
▷ Final classes | 0 | 0.00% |
Methods | 1,763 | |
▷ Static methods | 131 | 7.43% |
▷ Public methods | 1,485 | 84.23% |
▷ Protected methods | 210 | 11.91% |
▷ Private methods | 68 | 3.86% |
Functions | 21 | |
▷ Named functions | 5 | 23.81% |
▷ Anonymous functions | 16 | 76.19% |
Constants | 158 | |
▷ Global constants | 2 | 1.27% |
▷ Class constants | 156 | 98.73% |
▷ Public constants | 156 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
dompdf/lib/res/broken_image.png | 0.60KB | 0.47KB | ▼ 22.33% |