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.03MB] [CPU: ▼4.05ms] Passed 4 tests
Server-side resources used by Speisekarte
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 40.80 ▼2.87 |
| Dashboard /wp-admin | 3.34 ▲0.03 | 45.19 ▼7.30 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 46.32 ▼4.03 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 92.74 ▼2.00 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 37.21 ▲3.81 |
Server storage [IO: ▲0.11MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 9 new files
Database: 1 new table, 7 new options
| New tables |
|---|
| wp_menu_cards |
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
| jal_db_version |
Browser metrics Passed 4 tests
An overview of browser requirements for Speisekarte
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,812 ▲55 | 13.15 ▼1.15 | 1.79 ▼0.86 | 44.67 ▼2.05 |
| Dashboard /wp-admin | 2,212 ▲24 | 5.83 ▲0.91 | 98.12 ▼2.95 | 40.95 ▼1.87 |
| Posts /wp-admin/edit.php | 2,101 ▲12 | 2.06 ▲0.06 | 40.41 ▼4.02 | 35.40 ▼0.30 |
| Add New Post /wp-admin/post-new.php | 1,552 ▲19 | 18.19 ▼5.06 | 638.01 ▼44.31 | 50.29 ▼13.53 |
| Media Library /wp-admin/upload.php | 1,400 ▲12 | 4.21 ▼0.01 | 93.91 ▼20.58 | 41.65 ▼7.35 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie WordPress options were found after uninstall: 7 options
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- jal_db_version
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% 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
Almost there! Just fix the following items
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/speisekarte/Speisekarte.php:33
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
These attributes need to be fixed:
- Screenshots: Add descriptions for screenshots #0, #0 in speisekarte/assets to your readme.txt
speisekarte/Speisekarte.php 92% from 13 tests
"Speisekarte" version 1.0.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("speisekarte.php" instead of "Speisekarte.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
There were no executable files found in this plugin232 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 5 | 31 | 35 | 195 |
| Markdown | 1 | 12 | 0 | 37 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.17 |
| Average class complexity | 4.50 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 8.00 |
| Average method complexity | 1.58 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 4.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 12 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 12 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| 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
PNG files should be compressed to save space and minimize bandwidth usage
2 PNG files occupy 0.10MB with 0.07MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot_2.png | 60.44KB | 14.03KB | ▼ 76.78% |
| screenshot_1.png | 37.22KB | 9.82KB | ▼ 73.62% |