Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
You still need to fix the following installer errors
- Install procedure had errors
- > Parse error in wp-content/plugins/filter-calendar-admin/dashboard-calendar.php+66
syntax error, unexpected end of file
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.71ms] Passed 4 tests
A check of server-side resources used by Filter Calendar Admin
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 37.79 ▼10.27 |
Dashboard /wp-admin | 3.31 ▲0.00 | 58.41 ▲6.13 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 54.31 ▼0.06 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 91.58 ▼6.35 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.66 ▼6.17 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 6 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
db_upgraded |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for Filter Calendar Admin
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.36 ▼0.04 | 1.89 ▼0.04 | 43.58 ▼5.61 |
Dashboard /wp-admin | 2,198 ▲21 | 5.63 ▼0.04 | 85.99 ▼1.35 | 43.32 ▲3.21 |
Posts /wp-admin/edit.php | 2,100 ▼3 | 2.02 ▲0.06 | 36.84 ▼7.13 | 33.81 ▼4.56 |
Add New Post /wp-admin/post-new.php | 1,526 ▼2 | 23.52 ▲0.46 | 691.83 ▲38.40 | 56.59 ▼3.13 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.20 ▲0.03 | 106.70 ▲0.47 | 42.73 ▼0.86 |
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
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
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 everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Parse error
syntax error, unexpected end of file in wp-content/plugins/filter-calendar-admin/dashboard-calendar.php on line 66
- > PHP Parse 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 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Please fix the following attributes:
- Screenshots: Screenshot #1 (Selecciona un día especifico, select to day in filter post) image required
- Plugin Name: Please specify the plugin name on the first line (
=== filter-calendar-admin ===
)
filter-calendar-admin/dashboard-calendar.php 92% from 13 tests
"Filter Calendar Admin" version 0.1'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: The principal plugin file should be the same as the plugin slug ("filter-calendar-admin.php" instead of "dashboard-calendar.php")
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
Success! There were no dangerous files found in this plugin1,916 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 1 | 157 | 171 | 1,721 |
CSS | 1 | 32 | 1 | 160 |
PHP | 1 | 15 | 16 | 35 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.00 |
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 | 3 | |
▷ Named functions | 3 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 9.25KB | 4.67KB | ▼ 49.51% |