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: ▲2.54MB] [CPU: ▲9.61ms] Passed 4 tests
A check of server-side resources used by Woning Website Uitbreiding
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 5.98 ▲2.51 | 53.74 ▲3.60 |
Dashboard /wp-admin | 5.89 ▲2.59 | 61.56 ▲7.64 |
Posts /wp-admin/edit.php | 5.95 ▲2.59 | 69.26 ▲17.38 |
Add New Post /wp-admin/post-new.php | 8.41 ▲2.53 | 107.93 ▲9.80 |
Media Library /wp-admin/upload.php | 5.75 ▲2.52 | 56.77 ▲21.93 |
Server storage [IO: ▲2.86MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 1,115 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
db_upgraded |
can_compress_scripts |
Browser metrics Passed 4 tests
Woning Website Uitbreiding: 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,806 ▲20 | 14.10 ▼0.51 | 1.87 ▼0.08 | 37.97 ▼5.61 |
Dashboard /wp-admin | 2,212 ▲35 | 5.63 ▼0.05 | 94.22 ▼7.59 | 45.43 ▲1.32 |
Posts /wp-admin/edit.php | 2,118 ▲18 | 2.02 ▲0.01 | 41.44 ▲4.25 | 36.96 ▲0.10 |
Add New Post /wp-admin/post-new.php | 1,543 ▲15 | 23.23 ▲0.12 | 650.83 ▼58.38 | 60.59 ▲8.94 |
Media Library /wp-admin/upload.php | 1,417 ▲23 | 4.20 ▲0.02 | 101.52 ▼0.57 | 45.90 ▲2.14 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
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
Please take a closer look at the following
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/woning-website-uitbreiding/assets/views/admin.metabox.php
- 149× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught ReflectionException: Class PHPStan\\Reflection\\Php\\BuiltinMethodReflection does not exist in wp-content/plugins/woning-website-uitbreiding/vendor/nesbot/carbon/src/Carbon/PHPStan/Macro.php:20
- > PHP Fatal error
Uncaught Error: Interface 'Carbon\\Exceptions\\InvalidArgumentException' not found in wp-content/plugins/woning-website-uitbreiding/vendor/nesbot/carbon/src/Carbon/Exceptions/InvalidTypeException.php:16
- > PHP Fatal error
Trait 'Carbon\\Traits\\IntervalRounding' not found in wp-content/plugins/woning-website-uitbreiding/vendor/nesbot/carbon/src/Carbon/Traits/Rounding.php on line 27
- > PHP Fatal error
Uncaught Error: Interface 'Tussendoor\\Settings\\Providers\\SettingsProviderInterface' not found in wp-content/plugins/woning-website-uitbreiding/vendor/tussendoor/settings/src/Providers/SettingsProviderOption.php:5
- > PHP Fatal error
Uncaught Error: Interface 'Symfony\\Component\\Translation\\Provider\\ProviderFactoryInterface' not found in wp-content/plugins/woning-website-uitbreiding/vendor/symfony/translation/Provider/AbstractProviderFactory.php:16
- > PHP Fatal error
Uncaught Exception: This script must be run from the command line. in wp-content/plugins/woning-website-uitbreiding/vendor/symfony/translation/Resources/bin/translation-status.php:13
- > PHP Fatal error
Uncaught Error: Interface 'Carbon\\Exceptions\\InvalidArgumentException' not found in wp-content/plugins/woning-website-uitbreiding/vendor/nesbot/carbon/src/Carbon/Exceptions/InvalidTimeZoneException.php:16
- > PHP Fatal error
Uncaught Error: Class 'Symfony\\Component\\Translation\\Loader\\FileLoader' not found in wp-content/plugins/woning-website-uitbreiding/vendor/symfony/translation/Loader/CsvFileLoader.php:21
- > PHP Fatal error
Uncaught Error: Interface 'Symfony\\Component\\Translation\\Formatter\\IntlFormatterInterface' not found in wp-content/plugins/woning-website-uitbreiding/vendor/symfony/translation/Formatter/IntlFormatter.php:21
- > PHP Fatal error
Uncaught Error: Class 'Symfony\\Component\\Translation\\Dumper\\FileDumper' not found in wp-content/plugins/woning-website-uitbreiding/vendor/symfony/translation/Dumper/IcuResFileDumper.php:21
- > 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 83% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that require attention:
- Tags: Please delete some tags, you are using 14 tag instead of maximum 10
woning-website-uitbreiding/index.php 69% from 13 tests
The principal PHP file in "Woning Website Uitbreiding" v. 1.1.3 is loaded by WordPress automatically on each request
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
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 142 characters long)
- Main file name: The principal plugin file should be the same as the plugin slug ("woning-website-uitbreiding.php" instead of "index.php")
- Requires at least: Required version does not match the one declared in readme.txt ("4.7" instead of "5.9")
Code Analysis 3% from 3 tests
File types 0% from 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
It is important to fix the following items
- Even if your plugin relies on executable files (for example a companion app), never distribute executable files with your plugin
- .bat - Batch File in Windows
- ☣ wp-content/plugins/woning-website-uitbreiding/vendor/nesbot/carbon/bin/carbon.bat
- .bat - Batch File in Windows
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 875 | 7,399 | 25,694 | 37,701 |
XSD | 3 | 92 | 48 | 2,803 |
JSON | 9 | 0 | 0 | 1,140 |
Markdown | 11 | 183 | 0 | 456 |
CSS | 1 | 67 | 1 | 338 |
JavaScript | 1 | 6 | 3 | 33 |
PO File | 1 | 9 | 14 | 31 |
XML | 1 | 2 | 2 | 22 |
YAML | 2 | 1 | 5 | 12 |
DOS Batch | 1 | 0 | 0 | 4 |
PHP code 50% from 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Please tend to the following items
- Cyclomatic complexity of methods should be reduced to less than 100 (currently 140)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.47 |
Average class complexity | 13.68 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 323.00 |
Average method complexity | 2.85 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 140.00 |
Code structure | ||
---|---|---|
Namespaces | 40 | |
Interfaces | 28 | |
Traits | 28 | |
Classes | 165 | |
▷ Abstract classes | 17 | 10.30% |
▷ Concrete classes | 148 | 89.70% |
▷ Final classes | 15 | 10.14% |
Methods | 1,809 | |
▷ Static methods | 394 | 21.78% |
▷ Public methods | 1,528 | 84.47% |
▷ Protected methods | 155 | 8.57% |
▷ Private methods | 126 | 6.97% |
Functions | 353 | |
▷ Named functions | 104 | 29.46% |
▷ Anonymous functions | 249 | 70.54% |
Constants | 110 | |
▷ Global constants | 7 | 6.36% |
▷ Class constants | 103 | 93.64% |
▷ Public constants | 100 | 97.09% |
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
No PNG images were found in this plugin