Persian Kit
Reviewed source f05b63e
Plugin comparison
Reviewed October 8, 2026Compare features, then inspect the results of specific tests.
Feature comparison
Based on documentation and source review.
What the symbols mean
SupportedNot includedNot verified — may be available
Support listed here does not mean every feature was tested.
| Feature | Persian Kit | Parsi Date |
|---|---|---|
| Dates 4 | ||
| Jalali dates in posts and admin | Included | Included |
| Show Jalali and Gregorian together | Included | Included |
| Jalali calendar and archive blocks | Included | Included |
| Jalali dates in post URLs | Optional | Optional |
| Text and editing 4 | ||
| Persian digits | Optional; off on new installs | Configurable by content type |
| Convert Arabic ي and ك to Persian ی and ک | Optional when saving text | When displaying text |
| Half-space keyboard shortcut | Classic and block editors | Not verified |
| Admin font | 3 fonts, including Vazirmatn | Vazirmatn |
| Forms and other plugins 6 | ||
| ACF date fields | Jalali date picker | Jalali date picker |
| Gravity Forms | Jalali dates and Iranian input checks | Date integration documented |
| Other form integrations | Contact Form 7, WPForms, Forminator | Elementor forms, JetEngine, Brizy, Booked |
| Iranian cities at checkout | Included | Included |
| Jalali WooCommerce Analytics | Included | Included |
| Payment gateway | Not included | Through the ParsiGate add-on |
| Requirements 2 | ||
| Minimum WordPress | 6.8 | 5.3 |
| Minimum PHP | 8.1 | 7.4 |
Form integrations may cover different fields. Changing a currency setting does not convert stored prices.
Sources & migration notes
Persian Kit documentationParsi Date
Persian Kit can review and import supported settings, widgets, blocks and ACF dates, and handle old Jalali links. Theme code calling Parsi Date functions needs the compatibility code supplied by the migration tool. Keep that step in your plan.
Try any migration on a backed-up test copy first.
Test results
Each plugin was enabled separately on the same Persian WordPress site. Results apply to these settings and examples.
| Test | Persian Kit | Parsi Date |
|---|---|---|
| Search for کتاب or كتاب | Found both sample posts | Found one sample post |
| Jalali leap day and new year | Both dates correct | Both dates correct |
| Stored dates after display | Unchanged | Unchanged |
| Date format for software¹ | Original format preserved | Format changed |
¹ One WordPress date function was tested. This does not establish how every feed or SEO plugin behaves.
Test inputs and exact output
Two posts were saved: one with Persian ک and one with Arabic ك. The saved text was not changed.
Parsi Date returned the post matching the spelling entered. Persian Kit returned both spellings.
get_the_date(DATE_W3C) · same post
2026-10-04T12:00:00+03:301405-07-12\12:00:00Visible date in both: 1405-07-12 12:00Performance
Execution times varied between the homepage, search, admin and checkout. These local measurements do not establish a general speed ranking.
Homepage
Median PHP time · millisecondsWordPress + WooCommerce45.7 ms
+ Persian Kit46 ms
+ Parsi Date48.4 ms
Search
Median PHP time · millisecondsWordPress + WooCommerce45.9 ms
+ Persian Kit52.5 ms
+ Parsi Date56.8 ms
Posts in admin
Median PHP time · millisecondsWordPress + WooCommerce62.7 ms
+ Persian Kit67.7 ms
+ Parsi Date70.9 ms
Classic checkout
Median PHP time · millisecondsWordPress + WooCommerce49.6 ms
+ Persian Kit46.7 ms
+ Parsi Date57.7 ms
All measurements & test settings4 screens · 30 samples each
The same small test site, with date features enabled. These numbers measure PHP execution on the server, not page loading in a browser. Each plugin performed somewhat different work.
Homepage
| Configuration | Median | p95 |
|---|---|---|
| WordPress + WooCommerce | 45.7 | 116.7 |
| + Persian Kit | 46 | 115.9 |
| + Parsi Date | 48.4 | 63.1 |
Search
| Configuration | Median | p95 |
|---|---|---|
| WordPress + WooCommerce | 45.9 | 78.3 |
| + Persian Kit | 52.5 | 61.7 |
| + Parsi Date | 56.8 | 63.6 |
Posts in admin
| Configuration | Median | p95 |
|---|---|---|
| WordPress + WooCommerce | 62.7 | 98 |
| + Persian Kit | 67.7 | 125.9 |
| + Parsi Date | 70.9 | 86.7 |
Classic checkout
| Configuration | Median | p95 |
|---|---|---|
| WordPress + WooCommerce | 49.6 | 57.6 |
| + Persian Kit | 46.7 | 71 |
| + Parsi Date | 57.7 | 66.4 |
Lower is better for this metric. p95 shows the slower end of the sample. Configuration and enabled work differ between plugins; close numbers are not a reliable ranking. Persian Kit’s spelling search was off for this date-focused benchmark. Memory, query counts and individual samples are included in the downloadable results.
Code checks
Plugin Check was run on all three plugins. Persian Kit’s own tests were also run; the other plugins’ test suites were not run.
Tests, coding standards & limitations
Persian Kit’s test suite
985 PHP tests and 163 JavaScript tests passed. Another 443 PHP tests and 3 JavaScript tests were skipped. These results do not validate every supported integration.
Coding standards, precisely
Persian Kit’s configured PHPCS checks passed: selected WordPress security, database, translation and API rules. Its formatting uses PSR-12. This is not full WordPress coding-style compliance or a security audit.
Plugin Check results and their limits
The same Plugin Check 2.1.0 static scan reported 0 errors / 8 warnings for Persian Kit, 131 errors / 316 warnings for Parsi Date.
These counts are messages from an automated tool. They have not been individually reviewed and do not show which plugin is more secure. Persian Kit’s eight warnings concern integration hook names. Runtime checks and a manual security review were not performed.
About Plugin CheckMETHOD & LIMITS
This comparison was prepared by Eram, the maker of Persian Kit, on October 8, 2026. The versions reviewed are shown at the top of this page.
Environment, limitations & downloads
- WordPress 7.0.2 · PHP 8.3.33 · WooCommerce 9.9.7 · MariaDB 11.8.8 · fa_IR · Asia/Tehran.
- A minimal theme, synthetic posts, one virtual product and classic checkout. WooCommerce was active in every run; each candidate was enabled separately. External requests and scheduled cron were disabled.
- Not tested: real payments, checkout submission, block checkout, migration on a live site, large catalogs, every theme or the full PHP/WordPress compatibility matrix.