Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.05MB] [CPU: ▼2.30ms] Passed 4 tests
This is a short check of server-side resources used by Order Notification for Telegram
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.52 ▲0.05 | 44.91 ▼7.71 |
Dashboard /wp-admin | 3.35 ▲0.04 | 57.17 ▲4.83 |
Posts /wp-admin/edit.php | 3.46 ▲0.10 | 53.00 ▲2.91 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 98.86 ▲0.27 |
Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 37.52 ▼4.65 |
Server storage [IO: ▲0.15MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 21 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Order Notification for Telegram
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,793 ▲7 | 14.73 ▲0.35 | 1.70 ▼0.77 | 43.86 ▼3.82 |
Dashboard /wp-admin | 2,202 ▲25 | 5.62 ▼0.05 | 88.54 ▲0.41 | 40.88 ▲2.93 |
Posts /wp-admin/edit.php | 2,104 ▲7 | 2.01 ▲0.06 | 35.39 ▲1.10 | 36.09 ▼0.85 |
Add New Post /wp-admin/post-new.php | 1,530 ▲2 | 23.70 ▲0.35 | 696.54 ▲24.61 | 60.05 ▲7.38 |
Media Library /wp-admin/upload.php | 1,398 ▲1 | 4.22 ▲0.04 | 101.48 ▼16.57 | 46.04 ▼1.01 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
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
Everything seems fine, however this is by no means an exhaustive test
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
Please take a closer look at the following
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'WC_Settings_Page' not found in wp-content/plugins/order-notification-for-telegram/Classes/SettingPage.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/order-notification-for-telegram/inc/admin_ajax.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that require attention:
- Screenshots: Add a description for screenshot #2 in order-notification-for-telegram/assets to your readme.txt
order-notification-for-telegram/index.php 77% from 13 tests
The main file in "Order Notification for Telegram" v. 1.0.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Requires at least: Required version must be the same as the one declared in readme.txt ("5.0" instead of "3.2")
- Main file name: The principal plugin file should be the same as the plugin slug ("order-notification-for-telegram.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected716 lines of code in 13 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 7 | 42 | 49 | 369 |
SVG | 1 | 0 | 1 | 185 |
PO File | 1 | 22 | 22 | 84 |
JavaScript | 1 | 0 | 0 | 37 |
Markdown | 1 | 13 | 0 | 29 |
Sass | 1 | 0 | 0 | 11 |
CSS | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.13 |
Average class complexity | 4.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 8.00 |
Average method complexity | 1.36 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 5.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 4 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 4 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 26 | |
▷ Static methods | 1 | 3.85% |
▷ Public methods | 24 | 92.31% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 2 | 7.69% |
Functions | 4 | |
▷ Named functions | 2 | 50.00% |
▷ Anonymous functions | 2 | 50.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.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
2 PNG files occupy 0.08MB with 0.04MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-2.png | 33.38KB | 18.37KB | ▼ 44.99% |
screenshot-1.png | 49.94KB | 20.30KB | ▼ 59.36% |