Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.13MB] [CPU: ▼3.07ms] Passed 4 tests
Analyzing server-side resources used by Froont for WordPress
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.58 ▲0.13 | 45.47 ▼4.46 |
| Dashboard /wp-admin | 3.43 ▲0.12 | 47.00 ▼0.49 |
| Posts /wp-admin/edit.php | 3.54 ▲0.18 | 48.23 ▼0.79 |
| Add New Post /wp-admin/post-new.php | 6.03 ▲0.15 | 98.96 ▼6.55 |
| Media Library /wp-admin/upload.php | 3.35 ▲0.12 | 34.04 ▲1.64 |
| Froont /wp-admin/options-general.php?page=froont | 3.32 | 31.96 |
Server storage [IO: ▲0.49MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 29 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by Froont for WordPress
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,808 ▲51 | 13.22 ▼1.22 | 1.58 ▼0.37 | 43.33 ▲6.23 |
| Dashboard /wp-admin | 2,211 ▲23 | 4.87 ▼0.99 | 110.28 ▲4.26 | 42.50 ▼7.11 |
| Posts /wp-admin/edit.php | 2,100 ▲11 | 2.04 ▲0.03 | 40.11 ▼1.06 | 34.50 ▼0.44 |
| Add New Post /wp-admin/post-new.php | 6,174 ▲4,632 | 22.68 ▲4.37 | 906.57 ▲298.07 | 57.93 ▼3.26 |
| Media Library /wp-admin/upload.php | 1,396 ▲8 | 4.24 ▲0.06 | 102.37 ▲6.94 | 44.70 ▲1.54 |
| Froont /wp-admin/options-general.php?page=froont | 821 | 2.04 | 22.85 | 29.63 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- widget_recent-posts
Smoke tests 50% from 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 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
The following issues need your attention
- 2× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/froont/public/partials/froont-public-display.php
- > /wp-content/plugins/froont/admin/partials/froont-admin-display.php
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_post_meta() in wp-content/plugins/froont/public/template.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
2 plugin tags: froont, design
froont/froont.php Passed 13 tests
The primary PHP file in "Froont for WordPress" version 1.0.0 is used by WordPress to initiate all plugin functionality
47 characters long description:
Publish your Froont projects as posts or pages.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected622 lines of code in 19 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 14 | 225 | 603 | 533 |
| JavaScript | 2 | 12 | 27 | 68 |
| CSS | 2 | 3 | 4 | 14 |
| Markdown | 1 | 3 | 0 | 7 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 7.25 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 41.00 |
| Average method complexity | 2.11 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 11.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 45 | |
| ▷ Static methods | 3 | 6.67% |
| ▷ Public methods | 40 | 88.89% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 11.11% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| 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
PNG files should be compressed to save space and minimize bandwidth usage
4 PNG files occupy 0.44MB with 0.12MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/banner-1544x500.png | 346.45KB | 148.09KB | ▼ 57.25% |
| assets/icon-128x128.png | 0.11KB | 0.12KB | 0.00% |
| assets/icon-256x256.png | 0.13KB | 0.14KB | 0.00% |
| assets/banner-772x250.png | 99.07KB | 43.14KB | ▼ 56.46% |