Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼8.10ms] Passed 4 tests
A check of server-side resources used by Fetch JFT
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 36.30 ▼5.96 |
| Dashboard /wp-admin | 3.34 ▼0.01 | 53.90 ▼11.85 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 47.18 ▼0.37 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 82.92 ▼14.21 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 36.20 ▲2.51 |
| Fetch JFT /wp-admin/options-general.php?page=jft-plugin | 3.23 | 33.80 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 10 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_recent-posts |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| db_upgraded |
Browser metrics Passed 4 tests
Fetch JFT: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,795 ▲34 | 14.28 ▼0.07 | 1.55 ▼0.10 | 39.77 ▼7.54 |
| Dashboard /wp-admin | 2,202 ▲22 | 5.54 ▼0.14 | 82.29 ▼1.41 | 38.26 ▼0.63 |
| Posts /wp-admin/edit.php | 2,104 ▲4 | 1.99 ▼0.03 | 33.96 ▼0.80 | 31.13 ▼8.96 |
| Add New Post /wp-admin/post-new.php | 1,529 ▲3 | 23.66 ▲0.63 | 677.91 ▼1.84 | 55.41 ▼4.35 |
| Media Library /wp-admin/upload.php | 1,404 ▲7 | 4.26 ▼0.01 | 95.32 ▼3.36 | 43.20 ▼2.43 |
| Fetch JFT /wp-admin/options-general.php?page=jft-plugin | 921 | 1.99 | 23.67 | 28.12 |
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
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
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
Good news, no errors were detected
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/fetch-jft/fetch-jft-plugin.php
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/fetch-jft/src/Widget.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
4 plugin tags: jft, just for today, narcotics anonymous, na
fetch-jft/fetch-jft-plugin.php 85% from 13 tests
The primary PHP file in "Fetch JFT" version 1.8.2 is used by WordPress to initiate all plugin functionality
You should first fix the following items:
- Main file name: Name the main plugin file the same as the plugin slug ("fetch-jft.php" instead of "fetch-jft-plugin.php")
- Description: Keep the plugin description shorter than 140 characters (currently 189 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
Success! There were no dangerous files found in this plugin831 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 83 | 285 | 831 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.43 |
| Average class complexity | 28.20 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 100.00 |
| Average method complexity | 3.87 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 52.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 5 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 5 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 48 | |
| ▷ Static methods | 18 | 37.50% |
| ▷ Public methods | 29 | 60.42% |
| ▷ Protected methods | 14 | 29.17% |
| ▷ Private methods | 5 | 10.42% |
| Functions | 2 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 2 | 100.00% |
| Constants | 5 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 5 | 100.00% |
| ▷ Public constants | 5 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
No PNG images were found in this plugin