Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼5.19ms] Passed 4 tests
Server-side resources used by AL Frontend Publish Editor
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.03 | 39.38 ▼5.09 |
| Dashboard /wp-admin | 3.37 ▲0.03 | 49.67 ▲1.31 |
| Posts /wp-admin/edit.php | 3.42 ▲0.03 | 50.13 ▲0.35 |
| Add New Post /wp-admin/post-new.php | 5.95 ▲0.03 | 83.40 ▼17.31 |
| Media Library /wp-admin/upload.php | 3.29 ▲0.03 | 37.12 ▲2.73 |
Server storage [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: no files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-posts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for AL Frontend Publish Editor
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,814 ▲68 | 13.24 ▼1.12 | 1.66 ▼0.21 | 40.38 ▼2.12 |
| Dashboard /wp-admin | 2,215 ▲27 | 5.85 ▲0.96 | 99.41 ▼5.66 | 38.38 ▼5.23 |
| Posts /wp-admin/edit.php | 2,098 ▲9 | 2.01 ▼0.01 | 33.82 ▼7.03 | 32.05 ▼4.81 |
| Add New Post /wp-admin/post-new.php | 1,524 ▼4 | 17.79 ▼0.39 | 655.50 ▲31.44 | 43.34 ▼8.30 |
| Media Library /wp-admin/upload.php | 1,394 ▲3 | 4.20 ▲0.03 | 94.29 ▼4.51 | 40.20 ▼3.26 |
Uninstaller [IO: ✅] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP Passed 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
No output text or server-side errors detected on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
7 plugin tags: wp, editor, post, frontend, publishing...
wp-frontend-publish-editor/alshc_frontend_edit.php 85% from 13 tests
"AL Frontend Publish Editor" version 1.0.2's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
It is important to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("wp-frontend-publish-editor.php" instead of "alshc_frontend_edit.php")
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
No dangerous file extensions were detected952 lines of code in 29 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 15 | 50 | 158 | 376 |
| PHP | 8 | 155 | 122 | 338 |
| PO File | 1 | 28 | 28 | 89 |
| CSS | 3 | 18 | 24 | 82 |
| SVG | 1 | 10 | 0 | 37 |
| Markdown | 1 | 6 | 0 | 30 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity issues
| 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 | 11 | |
| ▷ Named functions | 11 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.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
8 PNG files occupy 0.11MB with 0.06MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-7.png | 21.68KB | 10.45KB | ▼ 51.79% |
| assets/icon-128x128.png | 5.46KB | 3.13KB | ▼ 42.69% |
| assets/screenshot-6.png | 10.47KB | 5.07KB | ▼ 51.57% |
| assets/screenshot-2.png | 19.76KB | 9.50KB | ▼ 51.91% |
| assets/screenshot-5.png | 14.88KB | 7.54KB | ▼ 49.32% |