Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼5.24ms] Passed 4 tests
Analyzing server-side resources used by Get in line
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 40.25 ▲0.66 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 46.37 ▼1.76 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 45.54 ▼6.00 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 84.35 ▼13.85 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 35.48 ▲1.57 |
| Get-In-Line /wp-admin/admin.php?page=get_in_line | 3.23 | 361.91 |
| Settings /wp-admin/admin.php?page=wpgil_settings | 3.18 | 29.70 |
| Records /wp-admin/admin.php?page=wpgil_records | 3.25 | 30.50 |
Server storage [IO: ▲2.41MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 34 new files
Database: no new tables, 10 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| getinline_project_widget |
| db_upgraded |
| getinline_project_language |
| widget_theysaidso_widget |
| getinline_project_key |
| widget_recent-comments |
| getinline_api |
| widget_recent-posts |
| can_compress_scripts |
Browser metrics Passed 4 tests
Get in line: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,831 ▲74 | 14.47 ▲0.04 | 1.82 ▼0.19 | 43.83 ▼2.40 |
| Dashboard /wp-admin | 2,237 ▲49 | 5.88 ▲1.00 | 102.18 ▼8.50 | 39.87 ▼1.09 |
| Posts /wp-admin/edit.php | 2,120 ▲28 | 2.06 ▼0.10 | 35.03 ▼5.90 | 34.83 ▲1.80 |
| Add New Post /wp-admin/post-new.php | 1,562 ▲38 | 23.48 ▲0.38 | 679.09 ▲66.50 | 56.75 ▲1.63 |
| Media Library /wp-admin/upload.php | 1,419 ▲37 | 4.20 ▼0.01 | 96.53 ▼3.76 | 42.24 ▼1.54 |
| Get-In-Line /wp-admin/admin.php?page=get_in_line | 687 | 1.53 | 7.42 | 14.47 |
| Settings /wp-admin/admin.php?page=wpgil_settings | 862 | 2.04 | 23.72 | 24.69 |
| Records /wp-admin/admin.php?page=wpgil_records | 1,146 | 3.79 | 57.21 | 43.39 |
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
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- db_upgraded
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
These server-side errors were triggered
- > GET request to /wp-admin/admin.php?page=wpgil_settings
- > Notice in wp-content/plugins/get-in-line/index.php+40
Undefined index: project_key
- > GET request to /wp-admin/admin.php?page=wpgil_settings
- > Notice in wp-content/plugins/get-in-line/index.php+49
Undefined index: project_widget
- > GET request to /wp-admin/admin.php?page=wpgil_settings
- > Notice in wp-content/plugins/get-in-line/index.php+58
Undefined index: language
SRP 50% from 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
Almost there! Just fix the following items
- 6× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/get-in-line/template/settings.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_remote_get() in wp-content/plugins/get-in-line/core/data.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_enqueue_style() in wp-content/plugins/get-in-line/template/records.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/get-in-line/index.php:12
- > PHP Notice
Undefined variable: message in wp-content/plugins/get-in-line/template/settings.php on line 2
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_enqueue_style() in wp-content/plugins/get-in-line/template/data.php:18
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Please fix the following user-side errors
- > GET request to /wp-admin/admin.php?page=wpgil_records
- > Javascript (severe) in unknown
/wp-admin/admin.php?page=wpgil_records - Access to XMLHttpRequest at 'https://lk.get-in-line.ru/api?do=wordpress&project=&act=orders_data' from origin '' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
- > GET request to /wp-admin/admin.php?page=wpgil_records
- > Network (severe)
https://lk.get-in-line.ru/api?do=wordpress&project=&act=orders_data - Failed to load resource: net::ERR_FAILED
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% 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
Please fix the following attributes:
- Screenshots: Please add descriptions for these screenshots #4, #5 in get-in-line/assets to your readme.txt
get-in-line/index.php 92% from 13 tests
"Get in line" 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 ("get-in-line.php" instead of "index.php")
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 detected28,282 lines of code in 18 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 5 | 2,582 | 1,889 | 23,506 |
| SVG | 1 | 0 | 0 | 2,671 |
| CSS | 6 | 206 | 94 | 1,885 |
| PHP | 6 | 50 | 15 | 220 |
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.18 |
| 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 | 9 | |
| ▷ Named functions | 9 | 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
PNG files should be compressed to save space and minimize bandwidth usage
5 compressed PNG files occupy 0.00MB
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| template/images/sort_desc_disabled.png | 0.14KB | 0.25KB | 0.00% |
| template/images/sort_asc_disabled.png | 0.14KB | 0.25KB | 0.00% |
| template/images/sort_desc.png | 0.15KB | 0.25KB | 0.00% |
| template/images/sort_both.png | 0.20KB | 0.29KB | 0.00% |
| template/images/sort_asc.png | 0.16KB | 0.25KB | 0.00% |