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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.07MB] [CPU: ▼0.36ms] Passed 4 tests
A check of server-side resources used by AJAX Calendar Future POSTS
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.54 ▲0.08 | 40.69 ▲0.53 |
| Dashboard /wp-admin | 3.37 ▲0.07 | 48.06 ▼0.86 |
| Posts /wp-admin/edit.php | 3.49 ▲0.13 | 48.96 ▼1.20 |
| Add New Post /wp-admin/post-new.php | 5.95 ▲0.07 | 95.13 ▲0.08 |
| Media Library /wp-admin/upload.php | 3.30 ▲0.07 | 41.42 ▲5.44 |
Server storage [IO: ▲0.30MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 26 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_ajax_calendar_future_widget |
| can_compress_scripts |
| widget_recent-posts |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by AJAX Calendar Future POSTS
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,908 ▲162 | 13.69 ▼0.62 | 7.60 ▲5.93 | 42.37 ▼4.44 |
| Dashboard /wp-admin | 2,206 ▲20 | 4.84 ▼0.15 | 119.40 ▲8.47 | 41.31 ▼1.64 |
| Posts /wp-admin/edit.php | 2,092 ▲6 | 2.04 ▲0.03 | 39.06 ▲1.19 | 37.95 ▲4.29 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼19 | 23.36 ▲0.07 | 628.63 ▼32.91 | 50.46 ▲3.11 |
| Media Library /wp-admin/upload.php | 1,385 ▼6 | 4.25 ▲0.08 | 98.94 ▼2.51 | 44.56 ▲1.38 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- This plugin does not fully uninstall, leaving 7 options in the database
- theysaidso_admin_options
- db_upgraded
- widget_ajax_calendar_future_widget
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
SRP 50% from 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 following issues need your attention
- 10× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wordpress-plugin-ajax-calendar-with-future-posts/jss.php:9
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/wordpress-plugin-ajax-calendar-with-future-posts/old/ajax-calendar-future_101.php:10
- > PHP Fatal error
'break' not in the 'loop' or 'switch' context in wp-content/plugins/wordpress-plugin-ajax-calendar-with-future-posts/include/admin-page-framework/classes/admin-page-framework.php on line 2338
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/wordpress-plugin-ajax-calendar-with-future-posts/old/ajax-calendar-future_old.php:11
- > PHP Fatal error
'break' not in the 'loop' or 'switch' context in wp-content/plugins/wordpress-plugin-ajax-calendar-with-future-posts/include/admin-page-framework/classes/admin-page-framework.php on line 2338
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/wordpress-plugin-ajax-calendar-with-future-posts/old/ajax-calendar-future_jq-try.php:11
- > PHP Fatal error
'break' not in the 'loop' or 'switch' context in wp-content/plugins/wordpress-plugin-ajax-calendar-with-future-posts/include/admin-page-framework/classes/admin-page-framework.php on line 2338
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/wordpress-plugin-ajax-calendar-with-future-posts/ajax-calendar-future.php:10
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/wordpress-plugin-ajax-calendar-with-future-posts/include/widget.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/wordpress-plugin-ajax-calendar-with-future-posts/include/query.php:8
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 87% 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
These attributes need your attention:
- Screenshots: Screenshot #1 (Example screenshot) image missing
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== wordpress-plugin-ajax-calendar-with-future-posts ===)
wordpress-plugin-ajax-calendar-with-future-posts/ajax-calendar-future.php 85% from 13 tests
Analyzing the main PHP file in "AJAX Calendar Future POSTS" version 1.3.5
Please take the time to fix the following:
- Description: Please don't use more than 140 characters for the plugin description (currently 322 characters long)
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wordpress-plugin-ajax-calendar-with-future-posts.php" instead of "ajax-calendar-future.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
There were no executable files found in this plugin3,175 lines of code in 13 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 11 | 1,016 | 883 | 3,148 |
| CSS | 1 | 1 | 0 | 14 |
| JavaScript | 1 | 8 | 1 | 13 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.43 |
| Average class complexity | 33.78 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 179.00 |
| Average method complexity | 4.47 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 41.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 18 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 18 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 170 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 117 | 68.82% |
| ▷ Protected methods | 53 | 31.18% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 18 | |
| ▷ Named functions | 18 | 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 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
7 PNG files occupy 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| (invalid) images/._arrow_left-sq.png | 4.00KB | 0.00KB | ▼ 100.00% |
| include/admin-page-framework/img/demo_02_32x32.png | 0.62KB | 0.74KB | 0.00% |
| images/arrow_left-sq.png | 1.39KB | 0.59KB | ▼ 57.38% |
| include/admin-page-framework/img/demo_01_32x32.png | 1.76KB | 1.09KB | ▼ 38.17% |
| include/admin-page-framework/img/demo_03_32x32.png | 0.72KB | 0.86KB | 0.00% |