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 gracefully, with no errors
Server metrics [RAM: ▲0.12MB] [CPU: ▼4.91ms] Passed 4 tests
Analyzing server-side resources used by Title to Terms Ultimate
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.59 ▲0.13 | 40.23 ▲4.00 |
| Dashboard /wp-admin | 3.43 ▲0.09 | 49.32 ▼7.64 |
| Posts /wp-admin/edit.php | 3.55 ▲0.19 | 51.34 ▲4.08 |
| Add New Post /wp-admin/post-new.php | 6.01 ▲0.13 | 82.24 ▼16.84 |
| Media Library /wp-admin/upload.php | 3.36 ▲0.13 | 35.33 ▲0.84 |
Server storage [IO: ▲0.29MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 22 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Title to Terms Ultimate
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,803 ▲42 | 14.35 ▼0.20 | 1.80 ▲0.28 | 43.87 ▲1.16 |
| Dashboard /wp-admin | 2,194 ▲17 | 5.56 ▼0.07 | 87.69 ▼0.38 | 40.12 ▼3.71 |
| Posts /wp-admin/edit.php | 2,102 ▲2 | 1.96 ▼0.04 | 34.39 ▼3.20 | 36.62 ▲0.05 |
| Add New Post /wp-admin/post-new.php | 1,528 ▲2 | 22.91 ▼0.25 | 700.49 ▲73.43 | 55.16 ▲7.38 |
| Media Library /wp-admin/upload.php | 1,399 ▼4 | 4.18 ▼0.17 | 96.01 ▼3.35 | 43.05 ▼0.12 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Good news, no errors were detected
SRP 0% 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 fix the following
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/title-to-tags/tests/bootstrap.php
- 3× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function Title_To_Terms\\plugin_dir_path() in wp-content/plugins/title-to-tags/title-to-terms.php:28
- > PHP Fatal error
Uncaught Error: Class 'WP_UnitTestCase' not found in wp-content/plugins/title-to-tags/tests/test-sample.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/title-to-tags/Library/fragments/update.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
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
4 plugin tags: tags, taxonomy, categories, automation
title-to-tags/title-to-terms.php 92% from 13 tests
"Title to Terms Ultimate" version 4.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("title-to-tags.php" instead of "title-to-terms.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected685 lines of code in 15 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 5 | 54 | 255 | 315 |
| Bourne Shell | 1 | 21 | 11 | 123 |
| Markdown | 3 | 38 | 0 | 109 |
| XML | 4 | 9 | 17 | 67 |
| YAML | 1 | 7 | 0 | 60 |
| CSS | 1 | 1 | 0 | 11 |
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.30 |
| Average class complexity | 18.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 35.00 |
| Average method complexity | 2.10 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 31 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 28 | 90.32% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 3 | 9.68% |
| 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
PNG files should be compressed to save space and minimize bandwidth usage
2 PNG files occupy 0.22MB with 0.15MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 134.73KB | 41.90KB | ▼ 68.90% |
| screenshot-2.png | 94.39KB | 30.93KB | ▼ 67.23% |