Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼7.95ms] Passed 4 tests
This is a short check of server-side resources used by Frontend Add Post
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.05 | 34.48 ▼4.21 |
| Dashboard /wp-admin | 3.27 ▼0.08 | 36.17 ▼20.02 |
| Posts /wp-admin/edit.php | 3.40 ▲0.04 | 44.75 ▼6.07 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 87.56 ▼1.51 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 33.69 ▲3.17 |
Server storage [IO: ▲0.22MB] [DB: ▲0.07MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 11 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for Frontend Add Post
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,885 ▲124 | 13.92 ▲0.68 | 10.62 ▲6.41 | 50.84 ▲10.76 |
| Dashboard /wp-admin | 2,189 ▲12 | 5.63 ▲0.06 | 93.40 ▲6.19 | 41.95 ▲0.93 |
| Posts /wp-admin/edit.php | 2,103 ▲3 | 1.97 ▲0.00 | 40.42 ▼1.05 | 36.08 ▼4.20 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼9 | 23.57 ▼1.22 | 617.69 ▼6.58 | 52.53 ▼26.91 |
| Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.25 ▲0.07 | 93.48 ▼1.22 | 43.94 ▲4.48 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% 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
The following issues need your attention
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/frontend-add-post/frontend-add-post.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
9 plugin tags: add post, post, shortcode post, ajax frontend, frontend...
frontend-add-post/frontend-add-post.php Passed 13 tests
The entry point to "Frontend Add Post" version 1.0 is a PHP file that has certain tags in its header comment area
97 characters long description:
Add a post on frontend with ajax also list down published post with simple yet attractive layout.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected895 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 3 | 101 | 116 | 519 |
| CSS | 3 | 16 | 9 | 209 |
| PHP | 1 | 53 | 24 | 167 |
PHP code Passed 2 tests
A brief analysis 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.17 |
| 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 | 6 | 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 50% from 2 tests
Image compression 50% from 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 |
| (invalid) images/user-icon.png | 1.30KB | 0.00KB | ▼ 100.00% |