Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.28MB] [CPU: ▼2.94ms] Passed 4 tests
Server-side resources used by WP Glossary
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.76 ▲0.30 | 42.43 ▲2.41 |
| Dashboard /wp-admin | 3.58 ▲0.28 | 50.09 ▼4.71 |
| Posts /wp-admin/edit.php | 3.70 ▲0.34 | 51.07 ▼2.78 |
| Add New Post /wp-admin/post-new.php | 6.16 ▲0.28 | 92.82 ▼2.13 |
| Media Library /wp-admin/upload.php | 3.51 ▲0.28 | 37.77 ▼2.15 |
| Glossary Groups /wp-admin/edit-tags.php?taxonomy=wpglossarygroup&post_type=glossary | 3.50 | 39.52 |
| Glossary Options /wp-admin/edit.php?post_type=glossary&page=glossary-options | 3.47 | 44.30 |
| Add New Term /wp-admin/post-new.php?post_type=glossary | 3.66 | 46.25 |
| Glossary Terms /wp-admin/edit.php?post_type=glossary | 3.42 | 34.22 |
Server storage [IO: ▲1.27MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 47 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| db_upgraded |
| wpg_vesion_check |
| widget_wpg-random-term |
| widget_recent-posts |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WP Glossary
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,875 ▲114 | 13.14 ▼1.21 | 5.41 ▲3.61 | 44.26 ▲1.11 |
| Dashboard /wp-admin | 2,243 ▲63 | 5.64 ▼0.02 | 84.87 ▼3.01 | 39.29 ▼0.31 |
| Posts /wp-admin/edit.php | 2,154 ▲54 | 2.19 ▲0.20 | 35.38 ▼4.91 | 33.84 ▼3.99 |
| Add New Post /wp-admin/post-new.php | 1,562 ▲36 | 23.02 ▼0.21 | 650.48 ▼24.93 | 54.98 ▼0.22 |
| Media Library /wp-admin/upload.php | 1,451 ▲51 | 4.31 ▲0.20 | 97.61 ▼20.62 | 41.52 ▼8.16 |
| Glossary Groups /wp-admin/edit-tags.php?taxonomy=wpglossarygroup&post_type=glossary | 1,300 | 2.20 | 28.32 | 30.10 |
| Glossary Options /wp-admin/edit.php?post_type=glossary&page=glossary-options | 1,068 | 1.98 | 28.66 | 28.46 |
| Add New Term /wp-admin/post-new.php?post_type=glossary | 2,428 | 7.88 | 170.93 | 61.81 |
| Glossary Terms /wp-admin/edit.php?post_type=glossary | 1,159 | 2.18 | 30.63 | 29.74 |
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
You still need to fix the following
- Zombie WordPress options were found after uninstall: 8 options
- widget_theysaidso_widget
- wpg_vesion_check
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- widget_wpg-random-term
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Almost there, just fix the following server-side errors
- > GET request to /wp-admin/post-new.php?post_type=glossary
- > Notice in wp-content/plugins/wp-glossary/class/wpg-post-types.class.php+53
Undefined variable: title
- > GET request to /wp-admin/post-new.php?post_type=glossary
- > Notice in wp-content/plugins/wp-glossary/class/wpg-post-types.class.php+54
Undefined variable: link
- > GET request to /wp-admin/edit.php?post_type=glossary
- > Notice in wp-content/plugins/wp-glossary/class/wpg.class.php+134
Trying to access array offset on value of type bool
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please fix the following
- 8× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'WPG' not found in wp-content/plugins/wp-glossary/class/wpg-taxonomies.class.php:5
- > PHP Fatal error
Uncaught Error: Class 'WPG' not found in wp-content/plugins/wp-glossary/class/wpg-shortcode-glossary-atoz.class.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-glossary/ajax.php:2
- > PHP Fatal error
Uncaught Error: Class 'WPG' not found in wp-content/plugins/wp-glossary/class/wpg-post-types.class.php:5
- > PHP Fatal error
Uncaught Error: Class 'WPG' not found in wp-content/plugins/wp-glossary/class/wpg-shortcode-glossary.class.php:2
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/wp-glossary/class/wpg-widget-random-term.class.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-glossary/ajax.php:2
- > PHP Fatal error
Uncaught Error: Class 'WPG' not found in wp-content/plugins/wp-glossary/class/wpg-shortcode-glossary-list.class.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 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
Attributes that require attention:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Example frontend hover tooltip), #2 (Adding glossary term to page content using shortcode), #3 (Editing a glossary term itself), #4 (jQuery based Glossary term A to Z), #5 (Default Glossary term archive), #6 (Glossary term list front end (full)), #7 (Backend adding term list with shortcode)
wp-glossary/wp-glossary.php Passed 13 tests
The primary PHP file in "WP Glossary" version 3.1.2 is used by WordPress to initiate all plugin functionality
59 characters long description:
Build a glossary of terms and link your post content to it.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
No dangerous file extensions were detected5,918 lines of code in 32 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 11 | 826 | 791 | 3,502 |
| PHP | 11 | 155 | 104 | 986 |
| PO File | 5 | 455 | 496 | 940 |
| CSS | 4 | 124 | 91 | 468 |
| JSON | 1 | 0 | 0 | 22 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| Average class complexity | 18.50 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 33.00 |
| Average method complexity | 3.86 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 28.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 49 | |
| ▷ Static methods | 4 | 8.16% |
| ▷ Public methods | 46 | 93.88% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 3 | 6.12% |
| Functions | 3 | |
| ▷ Named functions | 3 | 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 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
7 PNG files occupy 0.91MB with 0.48MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-4.png | 4.72KB | 3.06KB | ▼ 35.09% |
| screenshot-6.png | 30.04KB | 17.10KB | ▼ 43.09% |
| screenshot-5.png | 630.22KB | 186.82KB | ▼ 70.36% |
| screenshot-3.png | 119.95KB | 47.42KB | ▼ 60.46% |
| screenshot-7.png | 45.40KB | 20.30KB | ▼ 55.28% |