Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.08MB] [CPU: ▼6.64ms] Passed 4 tests
Analyzing server-side resources used by Pie Calendar
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.57 ▲0.10 | 39.27 ▼2.75 |
| Dashboard /wp-admin | 3.40 ▲0.10 | 47.92 ▼3.93 |
| Posts /wp-admin/edit.php | 3.45 ▲0.09 | 48.30 ▼6.24 |
| Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 88.45 ▼13.62 |
| Media Library /wp-admin/upload.php | 3.33 ▲0.09 | 38.39 ▲2.72 |
Server storage [IO: ▲0.87MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 20 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Pie Calendar
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.72 ▲0.15 | 1.73 ▼0.20 | 44.03 ▲0.98 |
| Dashboard /wp-admin | 2,198 ▲21 | 5.61 ▼0.06 | 82.16 ▼9.14 | 40.80 ▲0.32 |
| Posts /wp-admin/edit.php | 2,100 ▼3 | 2.00 ▲0.02 | 39.01 ▼1.09 | 34.27 ▼1.60 |
| Add New Post /wp-admin/post-new.php | 1,698 ▲172 | 22.30 ▼1.39 | 643.25 ▼17.51 | 57.50 ▲1.06 |
| Media Library /wp-admin/upload.php | 1,403 ▲6 | 4.20 ▲0.10 | 101.05 ▲1.06 | 47.48 ▲2.05 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
Smoke tests 75% 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)
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please take a closer look at the following
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/pie-calendar/includes/shortcode.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/pie-calendar/includes/metabox.php:39
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
4 plugin tags: fullcalendar, custom calendar, calendar, events
pie-calendar/plugin.php 85% from 13 tests
The entry point to "Pie Calendar" version 1.1.1 is a PHP file that has certain tags in its header comment area
Please make the necessary changes and fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Main file name: It is recommended to name the main PHP file as the plugin slug ("pie-calendar.php" instead of "plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected12,742 lines of code in 16 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JSON | 2 | 0 | 0 | 11,910 |
| PHP | 4 | 118 | 77 | 488 |
| CSS | 3 | 34 | 1 | 179 |
| JavaScript | 7 | 8 | 19 | 165 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.36 |
| 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 | 17 | |
| ▷ Named functions | 10 | 58.82% |
| ▷ Anonymous functions | 7 | 41.18% |
| Constants | 3 | |
| ▷ Global constants | 3 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.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
No PNG files were detected