Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.06MB] [CPU: ▼2.45ms] Passed 4 tests
Analyzing server-side resources used by Pretty Google Calendar
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.06 | 38.26 ▲1.60 |
| Dashboard /wp-admin | 3.37 ▲0.06 | 52.16 ▼1.03 |
| Posts /wp-admin/edit.php | 3.48 ▲0.12 | 50.29 ▼3.28 |
| Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 93.48 ▼7.07 |
| Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 39.30 ▲4.59 |
| Pretty Google Calendar Settings /wp-admin/options-general.php?page=pgcal-setting-admin | 3.25 | 30.42 |
Server storage [IO: ▲1.15MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 28 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| can_compress_scripts |
| widget_recent-posts |
| widget_theysaidso_widget |
| widget_recent-comments |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for Pretty Google Calendar
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,806 ▲60 | 13.22 ▼1.13 | 5.67 ▲4.02 | 41.05 ▲0.71 |
| Dashboard /wp-admin | 2,212 ▲20 | 4.86 ▼0.07 | 109.17 ▼6.23 | 44.42 ▲4.68 |
| Posts /wp-admin/edit.php | 2,095 ▲3 | 2.06 ▲0.02 | 40.65 ▲0.22 | 36.54 ▼0.15 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲19 | 23.32 ▲5.77 | 626.55 ▲4.71 | 60.49 ▲9.44 |
| Media Library /wp-admin/upload.php | 1,394 ▲3 | 4.18 ▼0.01 | 100.33 ▲0.40 | 45.42 ▼2.13 |
| Pretty Google Calendar Settings /wp-admin/options-general.php?page=pgcal-setting-admin | 848 | 2.02 | 25.84 | 42.26 |
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
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
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
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/pretty-google-calendar/pretty-google-calendar.php:29
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/pretty-google-calendar/init/init.php:63
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
8 plugin tags: google calendar, calendar, pretty calendar, fullcalendar, gcal...
pretty-google-calendar/pretty-google-calendar.php Passed 13 tests
The primary PHP file in "Pretty Google Calendar" version 1.6.2 is used by WordPress to initiate all plugin functionality
34 characters long description:
Google Calendars that aren't ugly.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Good job! No executable or dangerous file extensions detected2,910 lines of code in 21 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 9 | 47 | 113 | 2,568 |
| PHP | 5 | 56 | 95 | 228 |
| CSS | 6 | 16 | 4 | 105 |
| SVG | 1 | 0 | 0 | 9 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.13 |
| Average class complexity | 7.00 |
| ▷ Minimum class complexity | 7.00 |
| ▷ Maximum class complexity | 7.00 |
| Average method complexity | 1.67 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 4.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 9 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 9 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 8 | |
| ▷ Named functions | 8 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
4 PNG files occupy 0.44MB with 0.28MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-1.png | 105.38KB | 38.14KB | ▼ 63.81% |
| assets/screenshot-2.png | 129.79KB | 46.08KB | ▼ 64.49% |
| assets/screenshot-4.png | 40.42KB | 13.58KB | ▼ 66.40% |
| assets/screenshot-3.png | 176.52KB | 67.98KB | ▼ 61.49% |