Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.12ms] Passed 4 tests
This is a short check of server-side resources used by mqTranslate Separate Comments
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.01 | 36.73 ▼2.14 |
Dashboard /wp-admin | 3.31 ▲0.01 | 50.39 ▲3.54 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 48.36 ▼1.85 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 94.10 ▼7.35 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 32.84 ▼1.13 |
Server storage [IO: ▲0.20MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 7 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
theysaidso_admin_options |
db_upgraded |
widget_recent-comments |
can_compress_scripts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for mqTranslate Separate Comments
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲43 | 13.21 ▼1.08 | 4.61 ▲2.61 | 41.31 ▼7.13 |
Dashboard /wp-admin | 2,206 ▲17 | 5.88 ▲0.93 | 100.63 ▼13.40 | 37.74 ▼2.44 |
Posts /wp-admin/edit.php | 2,092 ▲3 | 1.98 ▼0.03 | 40.27 ▼2.50 | 35.70 ▲1.57 |
Add New Post /wp-admin/post-new.php | 1,547 ▲13 | 18.25 ▼4.87 | 597.95 ▲2.46 | 65.99 ▲10.08 |
Media Library /wp-admin/upload.php | 1,385 ▼6 | 4.30 ▲0.11 | 94.68 ▼2.99 | 40.59 ▼1.79 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_recent-posts
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
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'WP_Comment_Query' not found in wp-content/plugins/mqtranslate-separate-comments/qtranslate-separate-comments.php:411
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser errors were detected
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Please fix the following attributes:
- Screenshots: These screenshots require images: #1 (This is the notification message when a comment's language has either not been set-up or that language is currently disabled.), #2 (Here you can see different aspects of the back-end integration.)
- Tested up to: Version format is invalid
mqtranslate-separate-comments/qtranslate-separate-comments.php 85% from 13 tests
The main file in "mqTranslate Separate Comments" v. 1.2.4 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Description: Please keep the plugin description shorter than 140 characters (currently 296 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("mqtranslate-separate-comments.php" instead of "qtranslate-separate-comments.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected423 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 82 | 144 | 384 |
PO File | 1 | 9 | 16 | 39 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.41 |
Average class complexity | 29.50 |
▷ Minimum class complexity | 25.00 |
▷ Maximum class complexity | 34.00 |
Average method complexity | 4.35 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 34.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 17 | |
▷ Static methods | 15 | 88.24% |
▷ Public methods | 15 | 88.24% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 2 | 11.76% |
Functions | 0 | |
▷ Named functions | 0 | 0.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
There are no PNG files in this plugin