Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼1.94MB] [CPU: ▼57.46ms] Passed 4 tests
This is a short check of server-side resources used by SyntaxHighlighter - Spacegray
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.05 ▼1.41 | 4.17 ▼40.34 |
Dashboard /wp-admin | 2.07 ▼1.24 | 5.37 ▼46.20 |
Posts /wp-admin/edit.php | 2.07 ▼1.29 | 5.64 ▼48.71 |
Add New Post /wp-admin/post-new.php | 2.07 ▼3.82 | 6.14 ▼94.58 |
Media Library /wp-admin/upload.php | 2.07 ▼1.16 | 5.78 ▼34.95 |
Server storage [IO: ▲0.12MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-posts |
can_compress_scripts |
widget_recent-comments |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for SyntaxHighlighter - Spacegray
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲29 | 13.20 ▼1.19 | 1.75 ▼0.31 | 44.28 ▼0.19 |
Dashboard /wp-admin | 2,209 ▲18 | 5.86 ▲0.02 | 99.57 ▼4.15 | 39.99 ▼2.18 |
Posts /wp-admin/edit.php | 2,092 ▼0 | 1.96 ▼0.08 | 38.70 ▼3.61 | 36.35 ▼2.86 |
Add New Post /wp-admin/post-new.php | 1,521 ▲2 | 23.12 ▼0.17 | 698.14 ▲81.65 | 57.73 ▲5.54 |
Media Library /wp-admin/upload.php | 1,382 ▼6 | 4.21 ▲0.06 | 101.91 ▼4.07 | 43.78 ▼4.40 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% 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
- This plugin cannot be uninstalled
- > User notice in wp-includes/functions.php+5905
Function wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the syntaxhighlighter-theme-spacegray handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need your attention:
- Tags: You are using too many tags: 15 tag instead of maximum 10
- Contributors: The plugin contributors field is not present
syntaxhighlighter-evolved-spacegray/syntaxhighlighter-spacegray.php 92% from 13 tests
"SyntaxHighlighter - Spacegray" version 1.0.2'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 ("syntaxhighlighter-evolved-spacegray.php" instead of "syntaxhighlighter-spacegray.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
Success! There were no dangerous files found in this plugin351 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 2 | 91 | 26 | 325 |
PHP | 2 | 9 | 17 | 26 |
PHP code Passed 2 tests
This is a short overview 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.10 |
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
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.10MB with 0.06MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
ScreenShot02.png | 52.93KB | 22.25KB | ▼ 57.96% |
ScreenShot01.png | 53.32KB | 22.33KB | ▼ 58.11% |