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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.47MB] [CPU: ▲4.18ms] Passed 4 tests
A check of server-side resources used by Parsi Date
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.89 ▲0.43 | 46.01 ▲3.24 |
| Dashboard /wp-admin | 3.81 ▲0.51 | 52.88 ▲4.43 |
| Posts /wp-admin/edit.php | 3.86 ▲0.51 | 53.95 ▲5.59 |
| Add New Post /wp-admin/post-new.php | 6.42 ▲0.54 | 102.72 ▲3.47 |
| Media Library /wp-admin/upload.php | 3.67 ▲0.44 | 41.87 ▲7.12 |
Server storage [IO: ▲0.92MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 75 new files
Database: no new tables, 9 new options
| New WordPress options |
|---|
| widget_parsidate_archive |
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| widget_theysaidso_widget |
| wpp_settings |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_parsidate_calendar |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Parsi Date
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,827 ▲81 | 13.25 ▼1.34 | 5.00 ▲3.22 | 45.45 ▲3.86 |
| Dashboard /wp-admin | 2,233 ▲45 | 5.82 ▼0.06 | 107.66 ▲4.70 | 42.21 ▼3.88 |
| Posts /wp-admin/edit.php | 2,135 ▲43 | 2.04 ▼0.00 | 42.62 ▲1.42 | 42.41 ▲4.02 |
| Add New Post /wp-admin/post-new.php | 1,563 ▲16 | 18.38 ▲0.21 | 636.04 ▼3.81 | 54.19 ▼3.01 |
| Media Library /wp-admin/upload.php | 1,412 ▲24 | 4.25 ▲0.02 | 101.53 ▼2.89 | 47.19 ▲0.52 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- Zombie WordPress options detected upon uninstall: 9 options
- widget_parsidate_archive
- can_compress_scripts
- widget_parsidate_calendar
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
- wpp_settings
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following items
- 25× PHP files output text when accessed directly (only 10 are shown):
- > /wp-content/plugins/wp-parsidate/includes/settings.php
- > /wp-content/plugins/wp-parsidate/includes/fixes-archives.php
- > /wp-content/plugins/wp-parsidate/includes/admin/widgets.php
- > /wp-content/plugins/wp-parsidate/includes/fixes-misc.php
- > /wp-content/plugins/wp-parsidate/includes/admin/gutenberg-jalali-calendar.php
- > /wp-content/plugins/wp-parsidate/includes/fixes-calendar.php
- > /wp-content/plugins/wp-parsidate/includes/general.php
- > /wp-content/plugins/wp-parsidate/includes/plugins/acf-fields/class-wpp-acf-datepicker-v4.php
- > /wp-content/plugins/wp-parsidate/includes/install.php
- > /wp-content/plugins/wp-parsidate/includes/plugins/acf-fields/class-wpp-acf-timepicker-v4.php
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-parsidate/includes/admin/datepicker-rtl.php:28
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/wp-parsidate/languages/common-strings.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/wp-parsidate/includes/plugins/fixes-woo.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 83% 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: These screenshots require images: #1 (Plugin main settings), #2 (Number conversions settings), #3 (Other plugin compatibility), #4 (Persian datepicker in WooCommerce), #5 (Persian date type in ACF)
- Tags: You are using too many tags: 18 tag instead of maximum 10
wp-parsidate/wp-parsidate.php 77% from 13 tests
The main file in "Parsi Date" v. 4.0.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Description: Please keep the plugin description shorter than 140 characters (currently 246 characters long)
- Domain Path: Prefix the domain path with a forward slash character ("/parsi-languages")
- Domain Path: Note that the domain path follows the same naming rules as the domain name, using only dashes and lowercase characters ("parsi-languages")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Success! There were no dangerous files found in this plugin4,710 lines of code in 54 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 28 | 714 | 1,326 | 2,838 |
| JavaScript | 8 | 238 | 183 | 1,068 |
| CSS | 16 | 77 | 12 | 585 |
| PO File | 1 | 76 | 97 | 204 |
| SVG | 1 | 3 | 0 | 15 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.52 |
| Average class complexity | 19.92 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 116.00 |
| Average method complexity | 3.67 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 67.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 12 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 12 | 100.00% |
| ▷ Final classes | 1 | 8.33% |
| Methods | 85 | |
| ▷ Static methods | 7 | 8.24% |
| ▷ Public methods | 76 | 89.41% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 9 | 10.59% |
| Functions | 74 | |
| ▷ Named functions | 74 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
13 PNG files occupy 0.24MB with 0.13MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/arrow-down.png | 1.35KB | 0.43KB | ▼ 68.07% |
| screenshot-5.png | 13.54KB | 6.55KB | ▼ 51.67% |
| screenshot-3.png | 33.79KB | 15.46KB | ▼ 54.26% |
| assets/css/images/ui-icons_444444_256x240.png | 6.83KB | 4.17KB | ▼ 38.86% |
| screenshot-4.png | 34.82KB | 16.64KB | ▼ 52.22% |