Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼5.73ms] Passed 4 tests
This is a short check of server-side resources used by Always Edit In HTML
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 36.44 ▼7.13 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 45.03 ▼3.54 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 43.59 ▼4.64 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 84.95 ▼7.59 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 37.67 ▲0.37 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 8 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
| can_compress_scripts |
| widget_theysaidso_widget |
| db_upgraded |
Browser metrics Passed 4 tests
Always Edit In HTML: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲65 | 13.24 ▼1.14 | 1.78 ▲0.05 | 44.06 ▼0.63 |
| Dashboard /wp-admin | 2,203 ▲14 | 4.84 ▼0.06 | 96.50 ▼27.62 | 37.51 ▼5.56 |
| Posts /wp-admin/edit.php | 2,091 ▲2 | 2.15 ▲0.12 | 33.85 ▲0.58 | 33.35 ▼8.49 |
| Add New Post /wp-admin/post-new.php | 6,466 ▲4,947 | 20.27 ▼2.71 | 963.94 ▲314.50 | 70.29 ▲13.57 |
| Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.19 ▲0.02 | 110.59 ▲8.85 | 44.84 ▲2.39 |
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
These items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
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 load_plugin_textdomain() in wp-content/plugins/always-edit-in-html/always-edit-in-html.php:32
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that require attention:
- Screenshots: Add images for these screenshots: #1 (Always edit in HTML options box. Check to turn on.), #2 (Option turned on and page/post is in HTML mode. Visual and Text tabs removed.)
always-edit-in-html/always-edit-in-html.php Passed 13 tests
"Always Edit In HTML" version 2.4.5's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
107 characters long description:
Opens page and post editor in HTML mode to preserve formatting. Hides Visual editor tab on Classic Editor.
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 detected107 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 34 | 64 | 84 |
| PO File | 1 | 3 | 3 | 23 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.37 |
| 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 | 6 | |
| ▷ Named functions | 5 | 83.33% |
| ▷ Anonymous functions | 1 | 16.67% |
| 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
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/zeropointdevelopment-mark.png | 2.05KB | 1.30KB | ▼ 36.85% |