Benchmarks
Plugin footprint 83% 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 gracefully, with no errors
Server metrics [RAM: ▲0.10MB] [CPU: ▼5.90ms] Passed 4 tests
Server-side resources used by Schedule Terms
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.57 ▲0.11 | 35.07 ▼18.91 |
| Dashboard /wp-admin | 3.41 ▲0.10 | 46.30 ▼1.94 |
| Posts /wp-admin/edit.php | 3.46 ▲0.10 | 45.84 ▲0.22 |
| Add New Post /wp-admin/post-new.php | 6.00 ▲0.11 | 82.88 ▼1.77 |
| Media Library /wp-admin/upload.php | 3.33 ▲0.10 | 32.04 ▼0.98 |
Server storage [IO: ▲0.34MB] [DB: ▲0.07MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 36 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by Schedule Terms
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.80 ▲0.42 | 1.68 ▼0.28 | 38.01 ▼6.55 |
| Dashboard /wp-admin | 2,200 ▲18 | 5.78 ▲0.89 | 101.25 ▼17.34 | 40.12 ▼8.25 |
| Posts /wp-admin/edit.php | 2,092 ▼0 | 2.01 ▼0.04 | 38.60 ▲1.55 | 33.26 ▼1.49 |
| Add New Post /wp-admin/post-new.php | 1,537 ▲3 | 18.37 ▼4.75 | 703.51 ▲24.08 | 57.69 ▲1.45 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.19 ▼0.10 | 97.01 ▼1.97 | 43.04 ▼3.26 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though everything seems fine, this is not 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
Almost there! Just fix the following items
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'HAMWORKS\\WP\\Schedule_Terms\\Term\\UI' not found in wp-content/plugins/schedule-terms/includes/Term_UI.php:15
- > PHP Fatal error
Uncaught Error: Call to undefined function HAMWORKS\\WP\\Schedule_Terms\\add_action() in wp-content/plugins/schedule-terms/includes/Assets.php:19
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
2 plugin tags: schedule, term
schedule-terms/schedule-terms.php 92% from 13 tests
"Schedule Terms" version 1.2.4's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Domain Path: The domain path points to a folder that does not exist ("/languages")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
There were no executable files found in this plugin1,473 lines of code in 31 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 21 | 306 | 845 | 1,097 |
| TypeScript | 3 | 24 | 14 | 279 |
| JSON | 2 | 0 | 0 | 38 |
| Bourne Shell | 2 | 8 | 0 | 32 |
| XML | 1 | 4 | 2 | 25 |
| JavaScript | 2 | 0 | 0 | 2 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.41 |
| Average class complexity | 12.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 47.00 |
| Average method complexity | 2.59 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 4 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 12 | |
| ▷ Abstract classes | 1 | 8.33% |
| ▷ Concrete classes | 11 | 91.67% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 87 | |
| ▷ Static methods | 18 | 20.69% |
| ▷ Public methods | 74 | 85.06% |
| ▷ Protected methods | 6 | 6.90% |
| ▷ Private methods | 7 | 8.05% |
| Functions | 5 | |
| ▷ Named functions | 1 | 20.00% |
| ▷ Anonymous functions | 4 | 80.00% |
| Constants | 3 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 3 | 100.00% |
| ▷ Public constants | 3 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
3 PNG files occupy 0.26MB with 0.19MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| .wordpress-org/screenshot-3.png | 78.50KB | 22.41KB | ▼ 71.45% |
| .wordpress-org/screenshot-2.png | 70.65KB | 21.19KB | ▼ 70.01% |
| .wordpress-org/screenshot-1.png | 120.56KB | 30.11KB | ▼ 75.02% |