Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼8.04ms] Passed 4 tests
Server-side resources used by Localist Calendar for WordPress
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 41.08 ▼0.97 |
Dashboard /wp-admin | 3.31 ▲0.01 | 49.82 ▼2.25 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 45.30 ▼7.52 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 93.30 ▼17.44 |
Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 34.51 ▼4.94 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 4 new files
Database: 1 new table, 7 new options
New tables |
---|
wp_localistCalendar |
New WordPress options |
---|
db_upgraded |
widget_theysaidso_widget |
jal_db_version |
widget_recent-comments |
can_compress_scripts |
widget_recent-posts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Localist Calendar for WordPress
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,835 ▲74 | 13.12 ▼1.25 | 1.78 ▼0.38 | 42.54 ▲0.19 |
Dashboard /wp-admin | 2,241 ▲41 | 4.94 ▼0.96 | 108.79 ▲4.83 | 44.92 ▼9.02 |
Posts /wp-admin/edit.php | 2,123 ▲23 | 2.06 ▲0.05 | 36.42 ▼6.73 | 35.88 ▼4.52 |
Add New Post /wp-admin/post-new.php | 1,543 ▲9 | 23.23 ▼0.05 | 678.23 ▼11.11 | 57.12 ▼0.75 |
Media Library /wp-admin/upload.php | 1,420 ▲23 | 4.24 ▲0.01 | 101.37 ▼10.71 | 44.68 ▼2.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
The following items require your attention
- This plugin does not fully uninstall, leaving 7 options in the database
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- jal_db_version
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
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
Almost there! Just fix the following items
- 1× 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/localist-calendar/localist.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need your attention:
- Screenshots: Please a description for screenshot #1 in localist-calendar/assets to your readme.txt
localist-calendar/localist.php 92% from 13 tests
The primary PHP file in "Localist Calendar for WordPress" version 1.0 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("localist-calendar.php" instead of "localist.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Good job! No executable or dangerous file extensions detected1,332 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 120 | 106 | 901 |
JavaScript | 1 | 22 | 8 | 321 |
CSS | 1 | 8 | 15 | 110 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.45 |
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 | 11 | |
▷ Named functions | 11 | 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
PNG files should be compressed to save space and minimize bandwidth usage
There are no PNG files in this plugin