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.01MB] [CPU: ▼5.66ms] Passed 4 tests
A check of server-side resources used by WP context for GetSiteControl
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 33.32 ▼4.13 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 43.42 ▼3.50 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 49.48 ▲2.25 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 78.13 ▼17.26 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.01 | 39.75 ▲6.07 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WP context for GetSiteControl
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,810 ▲75 | 13.32 ▼1.32 | 4.35 ▲2.42 | 42.57 ▲3.25 |
| Dashboard /wp-admin | 2,206 ▲15 | 4.86 ▼1.04 | 113.66 ▲7.46 | 47.44 ▲6.60 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.01 ▲0.00 | 40.04 ▲3.96 | 36.17 ▲4.81 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼19 | 17.59 ▼5.38 | 656.89 ▼3.51 | 59.53 ▼13.76 |
| Media Library /wp-admin/upload.php | 1,385 ▼0 | 4.20 ▼0.01 | 95.53 ▲0.34 | 40.74 ▲1.00 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means 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
Almost there! Just fix the following items
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/wp-context-for-getsitecontrol/wp-getsitecontrol-tag.php
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)
No browser issues were found
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need to be fixed:
- Contributors: Plugin contributors not specified
wp-context-for-getsitecontrol/wp-getsitecontrol-tag.php 77% from 13 tests
The main file in "WP context for GetSiteControl" v. 1.0.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Domain Path: The domain path folder does not exist ("/languages")
- Main file name: Name the main plugin file the same as the plugin slug ("wp-context-for-getsitecontrol.php" instead of "wp-getsitecontrol-tag.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected80 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 26 | 16 | 58 |
| Markdown | 1 | 10 | 0 | 22 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.76 |
| 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 | 1 | |
| ▷ Named functions | 1 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG images were found in this plugin