Benchmarks
Plugin footprint 64% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲6.74MB] [CPU: ▲42.78ms] 25% from 4 tests
A check of server-side resources used by Glossary
Please have a look at the following items
- RAM: You should keep total memory usage under 10MB (currently 10.12MB on /wp-admin/edit.php?post_type=glossary&page=glossary)
- CPU: Total CPU usage must kept under 500.00ms (currently 2,024.97ms on /wp-admin/edit.php?post_type=glossary&page=glossary)
- Extra RAM: Extra memory usage should kept under 5MB (currently 6.74MB on /wp-admin/edit.php?post_type=glossary&page=glossary)
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 10.10 ▲6.63 | 76.76 ▲38.64 |
Dashboard /wp-admin | 10.12 ▲6.81 | 95.83 ▲42.90 |
Posts /wp-admin/edit.php | 10.12 ▲6.76 | 93.05 ▲42.04 |
Add New Post /wp-admin/post-new.php | 12.64 ▲6.75 | 132.95 ▲47.52 |
Media Library /wp-admin/upload.php | 10.12 ▲6.88 | 86.35 ▲54.81 |
Freemius Debug [v.2.6.0] /wp-admin/admin.php?page=freemius | 10.12 | 78.06 |
Settings /wp-admin/edit.php?post_type=glossary&page=glossary | 10.12 | 2,024.97 |
Server storage [IO: ▲11.92MB] [DB: ▲0.01MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 1,011 new files
Database: no new tables, 16 new options
New WordPress options |
---|
widget_glossary-latest-terms |
theysaidso_admin_options |
glossary_count_terms |
can_compress_scripts |
widget_glossary-alphabetical-index |
fs_active_plugins |
widget_recent-posts |
widget_theysaidso_widget |
glossary_count_related_terms |
db_upgraded |
... |
Browser metrics Passed 4 tests
Glossary: an overview of browser usage
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,889 ▲127 | 13.16 ▼1.24 | 4.44 ▲2.85 | 31.48 ▼7.86 |
Dashboard /wp-admin | 2,288 ▲110 | 4.86 ▼0.82 | 100.62 ▼13.91 | 41.60 ▲0.43 |
Posts /wp-admin/edit.php | 2,184 ▲84 | 2.47 ▲0.46 | 37.70 ▼2.28 | 34.15 ▼3.98 |
Add New Post /wp-admin/post-new.php | 6,292 ▲4,764 | 25.31 ▲2.06 | 940.20 ▲312.40 | 39.68 ▼11.05 |
Media Library /wp-admin/upload.php | 1,485 ▲91 | 4.42 ▲0.28 | 99.00 ▲1.60 | 44.59 ▲3.18 |
Freemius Debug [v.2.6.0] /wp-admin/admin.php?page=freemius | 1,141 | 1.99 | 35.34 | 31.02 |
Settings /wp-admin/edit.php?post_type=glossary&page=glossary | 1,059 | 2.23 | 40.54 | 61.27 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- Uninstall procedure had uncaught errors
- > Notice in wp-content/plugins/glossary-by-codeat/vendor/freemius/wordpress-sdk/includes/class-freemius.php+8546
Undefined property: stdClass::$plugins
- This plugin did not uninstall successfully, leaving 16 options in the database
- fs_debug_mode
- widget_recent-posts
- fs_active_plugins
- wrm_7f0e94d3baf140f6d309
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
- glossary-version
- widget_glossary-alphabetical-index
- theysaidso_admin_options
- ...
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following
- 5× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/glossary-by-codeat/vendor/micropackage/requirements/tests/bootstrap.php
- > /wp-content/plugins/glossary-by-codeat/glossary.php
- > /wp-content/plugins/glossary-by-codeat/vendor/wpdesk/wp-notice/vendor/wpdesk/wp-builder/tests/integration/bootstrap.php
- > /wp-content/plugins/glossary-by-codeat/vendor/wpdesk/wp-notice/tests/integration/bootstrap.php
- > /wp-content/plugins/glossary-by-codeat/vendor/wpdesk/wp-builder/tests/integration/bootstrap.php
- 347× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/glossary-by-codeat/vendor/ayecode/wp-super-duper/vendor/composer/installers/src/Composer/Installers/TaoInstaller.php:7
- > PHP Fatal error
Uncaught Error: Class 'CMB2_Type_Textarea' not found in wp-content/plugins/glossary-by-codeat/vendor/cmb2/includes/types/CMB2_Type_Textarea_Code.php:13
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/glossary-by-codeat/vendor/composer/installers/src/Composer/Installers/MayaInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'WP_UnitTestCase' not found in wp-content/plugins/glossary-by-codeat/vendor/micropackage/requirements/tests/Checker/test-ssl.php:16
- > PHP Fatal error
Uncaught Error: Class 'CMB2_Type_Counter_Base' not found in wp-content/plugins/glossary-by-codeat/vendor/cmb2/includes/types/CMB2_Type_Text.php:13
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/glossary-by-codeat/vendor/composer/installers/src/Composer/Installers/TuskInstaller.php:7
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/glossary-by-codeat/vendor/composer/installers/src/Composer/Installers/PlentymarketsInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Glossary\\Engine\\Base' not found in wp-content/plugins/glossary-by-codeat/frontend/Theme/Archive.php:19
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/glossary-by-codeat/vendor/ayecode/wp-super-duper/vendor/composer/installers/src/Composer/Installers/MediaWikiInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'WP_UnitTestCase' not found in wp-content/plugins/glossary-by-codeat/vendor/micropackage/requirements/tests/Checker/test-plugins.php:18
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
5 plugin tags: tooltip, glossary, lexicon, dictionary, vocabulary
glossary-by-codeat/glossary.php 85% from 13 tests
The main PHP file in "Glossary" ver. 2.2.10 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("glossary-by-codeat.php" instead of "glossary.php")
- Domain Path: The domain path folder does not exist ("/languages")
Code Analysis 97% from 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
Everything looks great! No dangerous files found in this plugin120,791 lines of code in 788 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 500 | 15,069 | 33,317 | 60,597 |
PO File | 122 | 14,327 | 18,516 | 32,401 |
JSON | 30 | 0 | 0 | 9,807 |
CSS | 35 | 404 | 1,217 | 5,853 |
SVG | 4 | 0 | 12 | 4,651 |
Markdown | 34 | 1,137 | 0 | 3,126 |
JavaScript | 22 | 455 | 676 | 2,149 |
Sass | 17 | 306 | 29 | 1,411 |
YAML | 12 | 74 | 31 | 440 |
XML | 11 | 46 | 38 | 236 |
Bourne Shell | 1 | 21 | 11 | 120 |
PHP code 50% from 2 tests
Analyzing cyclomatic complexity and code structure
It is recommended to fix the following
- Class cyclomatic complexity has to be reduced to less than 1000 (currently 3,096)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.52 |
Average class complexity | 17.22 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 3,096.00 |
Average method complexity | 3.61 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 94.00 |
Code structure | ||
---|---|---|
Namespaces | 32 | |
Interfaces | 26 | |
Traits | 6 | |
Classes | 487 | |
▷ Abstract classes | 22 | 4.52% |
▷ Concrete classes | 465 | 95.48% |
▷ Final classes | 2 | 0.43% |
Methods | 3,329 | |
▷ Static methods | 510 | 15.32% |
▷ Public methods | 2,632 | 79.06% |
▷ Protected methods | 216 | 6.49% |
▷ Private methods | 481 | 14.45% |
Functions | 237 | |
▷ Named functions | 193 | 81.43% |
▷ Anonymous functions | 44 | 18.57% |
Constants | 227 | |
▷ Global constants | 126 | 55.51% |
▷ Class constants | 101 | 44.49% |
▷ Public constants | 101 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
17 PNG files occupy 0.08MB with 0.02MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
vendor/cmb2/images/ui-bg_flat_0_aaaaaa_40x100.png | 0.18KB | 0.08KB | ▼ 51.67% |
vendor/cmb2/images/ui-icons_454545_256x240.png | 4.27KB | 4.11KB | ▼ 3.78% |
vendor/freemius/wordpress-sdk/assets/img/plugin-icon.png | 9.16KB | 5.26KB | ▼ 42.58% |
vendor/cmb2/images/ui-icons_2e83ff_256x240.png | 4.27KB | 4.11KB | ▼ 3.78% |
vendor/cmb2/images/ui-icons_222222_256x240.png | 4.27KB | 4.11KB | ▼ 3.78% |