Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼7.88ms] Passed 4 tests
This is a short check of server-side resources used by VigLink SpotLight By ShortCode
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 41.16 ▼5.56 |
Dashboard /wp-admin | 3.32 ▼0.03 | 47.80 ▼16.03 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 51.13 ▲2.12 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 87.65 ▼10.46 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 38.16 ▲0.53 |
VigLink SpotLight /wp-admin/options-general.php?page=slb-viglink-spotlight | 3.21 | 33.54 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 3 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-comments |
widget_recent-posts |
db_upgraded |
Browser metrics Passed 4 tests
VigLink SpotLight By ShortCode: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,793 ▲7 | 14.75 ▲0.40 | 1.84 ▼0.14 | 42.74 ▼2.46 |
Dashboard /wp-admin | 2,193 ▲13 | 5.55 ▼0.10 | 85.71 ▼9.72 | 37.42 ▼2.59 |
Posts /wp-admin/edit.php | 2,104 ▲4 | 1.96 ▼0.04 | 35.77 ▼3.18 | 35.22 ▼2.05 |
Add New Post /wp-admin/post-new.php | 1,529 ▲3 | 23.00 ▲0.10 | 653.00 ▼22.45 | 52.59 ▼1.23 |
Media Library /wp-admin/upload.php | 1,404 ▲4 | 4.17 ▼0.01 | 97.78 ▼5.70 | 41.41 ▼2.86 |
VigLink SpotLight /wp-admin/options-general.php?page=slb-viglink-spotlight | 815 | 1.99 | 24.75 | 25.64 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- db_upgraded
Smoke tests 75% 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 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
Please take a closer look at the following
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/viglink-spotlight-by-shortcode/spotlight.php:27
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need your attention:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== viglink-spotlight-by-shortcode ===
) - Screenshots: Please add descriptions for these screenshots #2, #3 in viglink-spotlight-by-shortcode/assets to your readme.txt
viglink-spotlight-by-shortcode/spotlight.php 77% from 13 tests
The main PHP script in "VigLink SpotLight By ShortCode" version 1.0.a... is automatically included on every request by WordPress
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("viglink-spotlight-by-shortcode.php" instead of "spotlight.php")
- Version: Use periods and digits only for your plugin's version number (ex. "1.0.3" instead of "1.0.a...")
- Description: Keep the plugin description shorter than 140 characters (currently 230 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected53 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 14 | 9 | 53 |
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 problems
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 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 PNG file occupies 0.04MB with 0.02MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/vlsl.png | 36.87KB | 16.32KB | ▼ 55.73% |