Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.06MB] [CPU: ▼0.66ms] Passed 4 tests
A check of server-side resources used by Styled Calendar - Customizable, Mobile Responsive Google Calendar Embeds
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.06 | 38.06 ▼2.52 |
Dashboard /wp-admin | 3.37 ▲0.06 | 46.87 ▼6.34 |
Posts /wp-admin/edit.php | 3.42 ▲0.06 | 49.67 ▲3.59 |
Add New Post /wp-admin/post-new.php | 5.98 ▲0.09 | 94.24 ▲2.69 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 38.43 ▲3.55 |
Server storage [IO: ▲1.83MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 17 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for Styled Calendar - Customizable, Mobile Responsive Google Calendar Embeds
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,868 ▲106 | 14.59 ▼0.13 | 1.89 ▲0.20 | 37.88 ▼8.54 |
Dashboard /wp-admin | 2,251 ▲81 | 5.67 ▼0.07 | 94.02 ▼6.03 | 41.87 ▲2.68 |
Posts /wp-admin/edit.php | 2,132 ▲29 | 2.00 ▲0.03 | 38.83 ▼0.48 | 34.97 ▼3.49 |
Add New Post /wp-admin/post-new.php | 1,547 ▲16 | 25.17 ▲2.00 | 598.80 ▼86.67 | 64.54 ▲10.00 |
Media Library /wp-admin/upload.php | 1,453 ▲59 | 4.16 ▲0.02 | 94.14 ▼0.64 | 41.38 ▼1.55 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- Uninstall procedure had uncaught errors
- > Warning in wp-includes/class-wp-hook.php+310
call_user_func_array() expects parameter 1 to be a valid callback, function 'uninstall_styled_calendar' not found or invalid function name
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
Smoke tests Passed 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)
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 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
The SRP test was a success
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 90% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
8 plugin tags: css, google calendar, event, responsive, customize...
styled-calendar-customized-google-calendars/styled-calendar.php 77% from 13 tests
The main file in "Styled Calendar - Customizable, Mobile Responsive Google Calendar Embeds" v. 1.0.8 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("styled-calendar-customized-google-calendars.php" instead of "styled-calendar.php")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 164 characters long)
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
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 detected1,826 lines of code in 10 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 1 | 212 | 55 | 1,290 |
SVG | 3 | 1 | 1 | 378 |
PHP | 4 | 40 | 64 | 143 |
HTML | 1 | 1 | 0 | 14 |
CSS | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
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 | 1 | |
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 | 16 | |
▷ Named functions | 1 | 6.25% |
▷ Anonymous functions | 15 | 93.75% |
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
PNG images were not found in this plugin