Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.37MB] [CPU: ▲3.84ms] Passed 4 tests
A check of server-side resources used by Perfect Tense - Spelling and Grammar Checker
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.87 ▲0.40 | 42.92 ▲1.70 |
| Dashboard /wp-admin | 3.71 ▲0.40 | 54.75 ▲7.67 |
| Posts /wp-admin/edit.php | 3.76 ▲0.40 | 49.97 ▲8.48 |
| Add New Post /wp-admin/post-new.php | 6.23 ▲0.34 | 97.73 ▼0.11 |
| Media Library /wp-admin/upload.php | 3.57 ▲0.34 | 38.43 ▲6.11 |
| Jobs /wp-admin/admin.php?page=perfect_tense_jobs | 3.54 | 32.83 |
| Settings /wp-admin/admin.php?page=perfect_tense_settings | 3.54 | 36.42 |
Server storage [IO: ▲0.30MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 17 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Perfect Tense - Spelling and Grammar Checker
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,877 ▲131 | 13.39 ▼1.02 | 2.02 ▼0.25 | 43.18 ▼1.23 |
| Dashboard /wp-admin | 2,246 ▲64 | 5.11 ▼0.92 | 104.92 ▼10.45 | 74.67 ▲37.38 |
| Posts /wp-admin/edit.php | 2,228 ▲139 | 2.47 ▲0.48 | 41.24 ▲0.73 | 36.64 ▲0.48 |
| Add New Post /wp-admin/post-new.php | 1,560 ▲28 | 23.35 ▲0.08 | 765.32 ▲172.21 | 38.54 ▼20.75 |
| Media Library /wp-admin/upload.php | 1,443 ▲55 | 4.44 ▲0.22 | 102.85 ▼4.87 | 74.01 ▲31.21 |
| Jobs /wp-admin/admin.php?page=perfect_tense_jobs | 718 | 1.53 | 7.02 | 23.61 |
| Settings /wp-admin/admin.php?page=perfect_tense_settings | 889 | 2.03 | 27.43 | 28.45 |
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
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
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
- 8× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/perfect-tense/background_processing/wp-background-processing.php:19
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/perfect-tense/ptense_functionality_1.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/perfect-tense/perfect_tense.php:15
- > PHP Notice
Trying to access array offset on value of type null in wp-content/plugins/perfect-tense/ptense_functionality_3.php on line 7
- > PHP Fatal error
Uncaught Error: Class 'WP_Async_Request' not found in wp-content/plugins/perfect-tense/background_processing/classes/wp-background-process.php:16
- > PHP Notice
Trying to access array offset on value of type null in wp-content/plugins/perfect-tense/ptense_functionality_3.php on line 14
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/perfect-tense/ptense_functionality_3.php:59
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/perfect-tense/ptense_functionality_2.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
5 plugin tags: spelling, spell check, proofreading, grammar, seo
perfect-tense/perfect_tense.php 77% from 13 tests
The main file in "Perfect Tense - Spelling and Grammar Checker" v. 1.0.1 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:
- Main file name: Name the main plugin file the same as the plugin slug ("perfect-tense.php" instead of "perfect_tense.php")
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 197 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Good job! No executable or dangerous file extensions detected2,202 lines of code in 11 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 9 | 739 | 1,343 | 2,080 |
| Markdown | 1 | 54 | 0 | 104 |
| JSON | 1 | 0 | 0 | 18 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.30 |
| Average class complexity | 21.00 |
| ▷ Minimum class complexity | 4.00 |
| ▷ Maximum class complexity | 58.00 |
| Average method complexity | 1.97 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 11.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 6 | |
| ▷ Abstract classes | 2 | 33.33% |
| ▷ Concrete classes | 4 | 66.67% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 125 | |
| ▷ Static methods | 3 | 2.40% |
| ▷ Public methods | 89 | 71.20% |
| ▷ Protected methods | 19 | 15.20% |
| ▷ Private methods | 17 | 13.60% |
| Functions | 51 | |
| ▷ Named functions | 42 | 82.35% |
| ▷ Anonymous functions | 9 | 17.65% |
| 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
4 PNG files occupy 0.16MB with 0.10MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/PTENSE_logo_no_bg.png | 66.75KB | 15.45KB | ▼ 76.86% |
| images/PTENSE_logo_tall_no_bg.png | 47.20KB | 21.13KB | ▼ 55.24% |
| images/PTENSE_bulb_no_bg.png | 44.16KB | 11.64KB | ▼ 73.63% |
| images/PTENSE_bulb_small_no_bg.png | 1.42KB | 0.76KB | ▼ 46.59% |