Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.37ms] Passed 4 tests
Server-side resources used by mnTextSelector
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 38.47 ▼4.89 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 44.54 ▼2.98 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 45.62 ▼0.09 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 84.33 ▼1.51 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.18 ▲1.55 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
| widget_recent-posts |
| db_upgraded |
Browser metrics Passed 4 tests
mnTextSelector: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,906 ▲149 | 13.60 ▼0.69 | 8.43 ▲6.33 | 42.43 ▼9.17 |
| Dashboard /wp-admin | 2,206 ▲21 | 5.87 ▲0.01 | 106.46 ▼8.41 | 38.25 ▼9.82 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.02 ▼0.04 | 35.46 ▲1.45 | 34.06 ▼3.09 |
| Add New Post /wp-admin/post-new.php | 1,538 ▲24 | 23.51 ▲6.05 | 677.24 ▼4.57 | 54.66 ▲2.56 |
| Media Library /wp-admin/upload.php | 1,391 ▲3 | 4.26 ▲0.04 | 102.77 ▲2.57 | 40.79 ▼2.34 |
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
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
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 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/mntextselector/plugin.mntextselector.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
5 plugin tags: highlighted text, text functions, jquery plugins, jquery, javascript
mntextselector/plugin.mntextselector.php 92% from 13 tests
The principal PHP file in "mnTextSelector" v. 1.2 is loaded by WordPress automatically on each request
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("mntextselector.php" instead of "plugin.mntextselector.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Good job! No executable or dangerous file extensions detected183 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 2 | 13 | 13 | 144 |
| PHP | 1 | 12 | 14 | 39 |
PHP code Passed 2 tests
Analyzing 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.07 |
| Average class complexity | 2.00 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 2.00 |
| Average method complexity | 1.14 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 2.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 7 | |
| ▷ Static methods | 7 | 100.00% |
| ▷ Public methods | 7 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
There were not PNG files found in your plugin