Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▼0.95MB] [CPU: ▼43.21ms] Passed 4 tests
Analyzing server-side resources used by GitHub-Flavored Markdown Comments
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.02 ▼0.44 | 14.58 ▼36.13 |
| Dashboard /wp-admin | 3.06 ▼0.25 | 18.32 ▼33.04 |
| Posts /wp-admin/edit.php | 3.06 ▼0.30 | 14.20 ▼34.15 |
| Add New Post /wp-admin/post-new.php | 3.06 ▼2.83 | 15.89 ▼69.53 |
| Media Library /wp-admin/upload.php | 3.06 ▼0.17 | 22.43 ▼15.01 |
Server storage [IO: ▲0.14MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 6 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for GitHub-Flavored Markdown Comments
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲65 | 13.79 ▼0.63 | 4.47 ▲2.69 | 42.73 ▼0.74 |
| Dashboard /wp-admin | 2,209 ▲18 | 4.86 ▼0.01 | 110.94 ▼5.21 | 44.37 ▼3.06 |
| Posts /wp-admin/edit.php | 2,092 ▼0 | 2.03 ▼0.02 | 37.91 ▼0.74 | 32.50 ▼2.52 |
| Add New Post /wp-admin/post-new.php | 1,533 ▼1 | 23.33 ▼0.02 | 668.73 ▼10.04 | 53.38 ▲0.52 |
| Media Library /wp-admin/upload.php | 1,385 ▼3 | 4.24 ▼0.13 | 94.59 ▼12.89 | 41.38 ▼4.39 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- Uninstall procedure had uncaught errors
- > Deprecated in wp-content/plugins/github-flavored-markdown-comments/lib/markdown.php+780
Array and string offset access syntax with curly braces is deprecated
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means 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
Please fix the following items
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/github-flavored-markdown-comments/github-flavored-markdown-comments.php:13
- > PHP Fatal error
Uncaught Error: Class 'Markdown_Parser' not found in wp-content/plugins/github-flavored-markdown-comments/lib/markdown-extra.php:7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Please fix the following attributes:
- Screenshots: Screenshot #1 (Example of pre- and post- converted text (live previews are not (yet) includeded in the plugin).) image missing
github-flavored-markdown-comments/github-flavored-markdown-comments.php Passed 13 tests
Analyzing the main PHP file in "GitHub-Flavored Markdown Comments" version 1.0
56 characters long description:
Markdown-powered WordPress comments, with a GitHub Twist
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Everything looks great! No dangerous files found in this plugin1,785 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 421 | 795 | 1,774 |
| Markdown | 1 | 9 | 0 | 11 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 38.75 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 87.00 |
| Average method complexity | 2.66 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 24.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 91 | |
| ▷ Static methods | 1 | 1.10% |
| ▷ Public methods | 90 | 98.90% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 1.10% |
| Functions | 1 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 1 | 100.00% |
| Constants | 13 | |
| ▷ Global constants | 13 | 100.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
1 PNG file occupies 0.04MB with 0.03MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 36.37KB | 9.71KB | ▼ 73.31% |