Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.18MB] [CPU: ▼2.10ms] Passed 4 tests
Analyzing server-side resources used by Supertext Translation and Proofreading
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 37.41 ▲1.16 |
| Dashboard /wp-admin | 3.54 ▲0.23 | 47.26 ▼1.38 |
| Posts /wp-admin/edit.php | 3.71 ▲0.35 | 52.38 ▲1.72 |
| Add New Post /wp-admin/post-new.php | 6.12 ▲0.23 | 88.35 ▼6.04 |
| Media Library /wp-admin/upload.php | 3.47 ▲0.24 | 37.71 ▼2.15 |
| Supertext /wp-admin/options-general.php?page=supertext-settings | 3.49 | 35.24 |
Server storage [IO: ▲1.45MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 138 new files
Database: no new tables, 9 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-posts |
| polylang_supertext_version |
| widget_theysaidso_widget |
| widget_recent-comments |
| polylang_supertext_settings |
| can_compress_scripts |
| polylang_supertext_environment_adjusted |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Supertext Translation and Proofreading
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,794 ▲47 | 14.67 ▲0.39 | 1.60 ▼0.06 | 36.02 ▼0.01 |
| Dashboard /wp-admin | 2,199 ▲18 | 5.61 ▼0.10 | 93.41 ▼16.29 | 41.51 ▼0.68 |
| Posts /wp-admin/edit.php | 2,178 ▲78 | 2.24 ▲0.30 | 40.17 ▼0.70 | 36.49 ▼1.40 |
| Add New Post /wp-admin/post-new.php | 1,529 ▲3 | 23.31 ▲0.29 | 638.17 ▼30.72 | 55.24 ▲0.16 |
| Media Library /wp-admin/upload.php | 1,457 ▲57 | 4.26 ▲0.09 | 99.24 ▼15.80 | 42.22 ▼8.01 |
| Supertext /wp-admin/options-general.php?page=supertext-settings | 1,146 | 2.34 | 40.26 | 29.97 |
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 detected upon uninstall: 8 options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- polylang_supertext_environment_adjusted
- polylang_supertext_version
- db_upgraded
- 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
Even though everything seems fine, this is not an exhaustive test
SRP 50% 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
- 45× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Supertext\\TextAccessors\\PostTextAccessor' not found in wp-content/plugins/polylang-supertext/src/Supertext/TextAccessors/DiviBuilderTextAccessor.php:10
- > PHP Fatal error
Uncaught Error: Class 'Supertext\\TextAccessors\\PostTextAccessor' not found in wp-content/plugins/polylang-supertext/src/Supertext/TextAccessors/VisualComposerTextAccessor.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/polylang-supertext/views/backend/settings-elementor.php:20
- > PHP Fatal error
Uncaught Error: Interface 'Supertext\\TextAccessors\\ITextAccessor' not found in wp-content/plugins/polylang-supertext/src/Supertext/TextAccessors/CustomFieldsTextAccessor.php:14
- > PHP Fatal error
Uncaught Error: Call to a member function getSettingOption() on null in wp-content/plugins/polylang-supertext/views/backend/settings-languages.php:7
- > PHP Fatal error
Uncaught Error: Interface 'Supertext\\Api\\IMultilang' not found in wp-content/plugins/polylang-supertext/src/Supertext/Api/PolylangApiWrapper.php:9
- > PHP Warning
Invalid argument supplied for foreach() in wp-content/plugins/polylang-supertext/views/backend/settings-custom-fields.php on line 13
- > PHP Notice
Undefined variable: library in wp-content/plugins/polylang-supertext/views/backend/settings-users.php on line 5
- > PHP Fatal error
Uncaught Error: Call to a member function getSettingOption() on null in wp-content/plugins/polylang-supertext/views/backend/settings-users.php:5
- > PHP Notice
Undefined variable: library in wp-content/plugins/polylang-supertext/views/backend/settings-api.php on line 6
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 90% 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
Please fix the following attributes:
- Screenshots: Please describe screenshot #7 in polylang-supertext/assets to your readme.txt
polylang-supertext/plugin.php 85% from 13 tests
The primary PHP file in "Supertext Translation and Proofreading" version 4.22 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("polylang-supertext.php" instead of "plugin.php")
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
Everything looks great! No dangerous files found in this plugin21,003 lines of code in 99 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 9 | 418 | 2,576 | 7,296 |
| PO File | 18 | 2,400 | 2,659 | 5,298 |
| PHP | 60 | 1,193 | 1,739 | 5,081 |
| CSS | 8 | 72 | 56 | 2,674 |
| Sass | 2 | 90 | 1 | 562 |
| Markdown | 1 | 28 | 0 | 61 |
| JSON | 1 | 0 | 0 | 31 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.33 |
| Average class complexity | 12.30 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 59.00 |
| Average method complexity | 2.52 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 22.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 7 | |
| Interfaces | 6 | |
| Traits | 0 | |
| Classes | 41 | |
| ▷ Abstract classes | 3 | 7.32% |
| ▷ Concrete classes | 38 | 92.68% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 372 | |
| ▷ Static methods | 18 | 4.84% |
| ▷ Public methods | 266 | 71.51% |
| ▷ Protected methods | 7 | 1.88% |
| ▷ Private methods | 99 | 26.61% |
| Functions | 6 | |
| ▷ Named functions | 3 | 50.00% |
| ▷ Anonymous functions | 3 | 50.00% |
| Constants | 67 | |
| ▷ Global constants | 5 | 7.46% |
| ▷ Class constants | 62 | 92.54% |
| ▷ Public constants | 62 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
8 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| resources/images/delete.png | 0.82KB | 0.86KB | 0.00% |
| resources/scripts/jstree/themes/default/40px.png | 1.84KB | 1.84KB | 0.00% |
| resources/images/logo_supertext.png | 0.62KB | 0.44KB | ▼ 27.78% |
| resources/images/arrow-right.png | 1.27KB | 0.25KB | ▼ 80.43% |
| resources/images/icon-st.png | 0.86KB | 0.69KB | ▼ 20.23% |