Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼3.40ms] Passed 4 tests
This is a short check of server-side resources used by Pride Kalender
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 36.02 ▼8.40 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 47.04 ▼1.42 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 46.61 ▲2.94 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 86.51 ▼6.71 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 39.68 ▲4.50 |
| Pridecalendar /wp-admin/options-general.php?page=pridecal-list | 3.27 | 33.34 |
Server storage [IO: ▲0.26MB] [DB: ▲0.07MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 8 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
| travel.gayguide.options |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Pride Kalender
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,822 ▲87 | 13.53 ▼0.77 | 1.75 ▼0.07 | 40.95 ▼2.86 |
| Dashboard /wp-admin | 2,228 ▲42 | 4.88 ▼1.03 | 112.65 ▲4.54 | 43.93 ▲0.71 |
| Posts /wp-admin/edit.php | 2,107 ▲18 | 2.03 ▼0.02 | 40.42 ▲3.44 | 35.74 ▲5.15 |
| Add New Post /wp-admin/post-new.php | 1,549 ▲16 | 23.76 ▲0.63 | 672.58 ▲10.20 | 51.89 ▼11.69 |
| Media Library /wp-admin/upload.php | 1,407 ▲19 | 4.20 ▼0.12 | 108.80 ▲11.86 | 50.43 ▲9.53 |
| Pridecalendar /wp-admin/options-general.php?page=pridecal-list | 843 | 2.16 | 25.81 | 27.65 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 0% 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
Please take a closer look at the following
- 2× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/pridecalendar/functions.php
- > /wp-content/plugins/pridecalendar/pridecalendar.php
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_die() in wp-content/plugins/pridecalendar/options.php:4
- > 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)
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 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
7 plugin tags: calendar, lgbt, pride, travel, spartacus...
pridecalendar/pridecalendar.php 92% from 13 tests
The entry point to "Pride Kalender" version 1.0.3 is a PHP file that has certain tags in its header comment area
The following require your attention:
- 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 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
There were no executable files found in this plugin327 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 33 | 20 | 306 |
| JavaScript | 1 | 0 | 1 | 21 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.52 |
| 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 | 11 | |
| ▷ Named functions | 11 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 7 | |
| ▷ Global constants | 7 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.24MB with 0.15MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| pridecal_button.png | 15.05KB | 7.19KB | ▼ 52.23% |
| wordpress_example.png | 231.43KB | 65.64KB | ▼ 71.64% |