Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.64ms] Passed 4 tests
Analyzing server-side resources used by FullscreenWidth
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.00 | 41.27 ▼3.20 |
| Dashboard /wp-admin | 13.19 ▲0.01 | 1,865,986.33 ▲7,968.02 |
| Posts /wp-admin/edit.php | 3.40 ▲0.00 | 44.44 ▼7.77 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.00 | 97.06 ▼6.68 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.00 | 41.65 ▼0.92 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for FullscreenWidth
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,803 ▲17 | 14.25 ▲0.01 | 1.87 ▼0.02 | 41.21 ▼2.59 |
| Dashboard /wp-admin | 2,212 ▲35 | 5.65 ▼0.02 | 91.22 ▼6.79 | 40.13 ▼3.75 |
| Posts /wp-admin/edit.php | 2,114 ▲14 | 2.01 ▼0.02 | 41.33 ▲4.08 | 36.16 ▲0.91 |
| Add New Post /wp-admin/post-new.php | 1,529 ▲1 | 23.45 ▲0.70 | 667.10 ▼20.25 | 57.50 ▲0.88 |
| Media Library /wp-admin/upload.php | 1,414 ▲14 | 4.18 ▼0.01 | 99.10 ▼3.58 | 42.23 ▼7.05 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% 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
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/fullscreenwidth/fullscreen-width.php:22
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that need to be fixed:
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== fullscreenwidth ===)
fullscreenwidth/fullscreen-width.php 92% from 13 tests
"FullscreenWidth" version 1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("fullscreenwidth.php" instead of "fullscreen-width.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Good job! No executable or dangerous file extensions detected28 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 7 | 18 | 28 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.60 |
| Average class complexity | 3.00 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 3.00 |
| Average method complexity | 2.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 3.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 2 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 2 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG files were detected