Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▼1.88MB] [CPU: ▼185.76ms] Passed 4 tests
Analyzing server-side resources used by Post to Flarum
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 1.75 ▼0.97 | 5.41 ▼17.02 |
Dashboard /wp-admin | 1.77 ▼1.28 | 6.24 ▼36.60 |
Posts /wp-admin/edit.php | 1.77 ▼1.34 | 5.58 ▼34.61 |
Add New Post /wp-admin/post-new.php | 1.77 ▼3.66 | 5.48 ▼647.00 |
Media Library /wp-admin/upload.php | 1.77 ▼1.23 | 5.76 ▼24.84 |
Post to Flarum /wp-admin/tools.php?page=postToFlarum | 1.77 | 4.63 |
Server storage [IO: ▲0.14MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 33 new files
Database: 2 new tables, 1 new option
New tables |
---|
wp_posttoflarum_posts |
wp_posttoflarum |
New WordPress options |
---|
_posttoflarum_db_version |
Browser metrics Passed 4 tests
A check of browser resources used by Post to Flarum
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,690 ▲94 | 15.99 ▲0.36 | 9.60 ▼1.17 | 50.85 ▲4.19 |
Dashboard /wp-admin | 2,974 ▲43 | 5.90 ▼0.05 | 137.06 ▼11.28 | 109.25 ▼2.94 |
Posts /wp-admin/edit.php | 2,746 ▲7 | 2.72 ▲0.01 | 74.87 ▲8.81 | 98.58 ▲7.90 |
Add New Post /wp-admin/post-new.php | 1,688 ▲188 | 18.54 ▼0.31 | 363.99 ▼25.45 | 115.87 ▲4.30 |
Media Library /wp-admin/upload.php | 1,814 ▲4 | 5.04 ▲0.01 | 153.24 ▲3.58 | 117.68 ▲4.00 |
Post to Flarum /wp-admin/tools.php?page=postToFlarum | 1,192 | 2.10 | 61.42 | 78.92 |
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
These items require your attention
- This plugin did not uninstall without warnings or errors
- > User notice in wp-includes/functions.php+5663
wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the postToFlarum_css handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Please fix the following server-side errors
- > GET request to /wp-admin/tools.php?page=postToFlarum
- > User notice in wp-includes/functions.php+5663
wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the postToFlarum_css handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/tools.php?page=postToFlarum
- > User notice in wp-includes/functions.php+5663
add_submenu_page was called incorrectly. The seventh parameter passed to add_submenu_page() should be an integer representing menu position. Please see Debugging in WordPress for more information. (This message was added in version 5.3.0.)
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 20× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'League\\HTMLToMarkdown\\Converter\\ConverterInterface' not found in wp-content/plugins/post-to-flarum/htmltomarkdown/Converter/EmphasisConverter.php:9
- > PHP Fatal error
Uncaught Error: Interface 'League\\HTMLToMarkdown\\Converter\\ConverterInterface' not found in wp-content/plugins/post-to-flarum/htmltomarkdown/Converter/DefaultConverter.php:9
- > PHP Fatal error
Uncaught Error: Interface 'League\\HTMLToMarkdown\\Converter\\ConverterInterface' not found in wp-content/plugins/post-to-flarum/htmltomarkdown/Converter/ListBlockConverter.php:7
- > PHP Fatal error
Uncaught Error: Interface 'League\\HTMLToMarkdown\\Converter\\ConverterInterface' not found in wp-content/plugins/post-to-flarum/htmltomarkdown/Converter/BlockquoteConverter.php:7
- > PHP Fatal error
Uncaught Error: Interface 'League\\HTMLToMarkdown\\Converter\\ConverterInterface' not found in wp-content/plugins/post-to-flarum/htmltomarkdown/Converter/LinkConverter.php:7
- > PHP Fatal error
Uncaught Error: Interface 'League\\HTMLToMarkdown\\Converter\\ConverterInterface' not found in wp-content/plugins/post-to-flarum/htmltomarkdown/Converter/HardBreakConverter.php:9
- > PHP Fatal error
Uncaught Error: Interface 'League\\HTMLToMarkdown\\Converter\\ConverterInterface' not found in wp-content/plugins/post-to-flarum/htmltomarkdown/Converter/CodeConverter.php:7
- > PHP Fatal error
Uncaught Error: Class 'Markdownify\\Converter' not found in wp-content/plugins/post-to-flarum/htmltomarkdown/ConverterExtra.php:5
- > PHP Fatal error
Uncaught Error: Interface 'League\\HTMLToMarkdown\\Converter\\ConverterInterface' not found in wp-content/plugins/post-to-flarum/htmltomarkdown/Converter/ImageConverter.php:7
- > PHP Fatal error
Uncaught Error: Interface 'League\\HTMLToMarkdown\\Converter\\ConverterInterface' not found in wp-content/plugins/post-to-flarum/htmltomarkdown/Converter/ParagraphConverter.php:7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Please fix the following attributes:
- Screenshots: A description for screenshot #1 is required in post-to-flarum/assets to your readme.txt
post-to-flarum/postToFlarum.php 92% from 13 tests
"Post to Flarum" version 0.3.4's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("post-to-flarum.php" instead of "postToFlarum.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
Success! There were no dangerous files found in this plugin2,995 lines of code in 32 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 29 | 613 | 1,407 | 2,956 |
Markdown | 2 | 17 | 0 | 36 |
CSS | 1 | 0 | 0 | 3 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.40 |
Average class complexity | 15.07 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 153.00 |
Average method complexity | 3.37 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 34.00 |
Code structure | ||
---|---|---|
Namespaces | 3 | |
Interfaces | 4 | |
Traits | 0 | |
Classes | 24 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 24 | 100.00% |
▷ Final classes | 1 | 4.17% |
Methods | 184 | |
▷ Static methods | 1 | 0.54% |
▷ Public methods | 98 | 53.26% |
▷ Protected methods | 73 | 39.67% |
▷ Private methods | 13 | 7.07% |
Functions | 19 | |
▷ Named functions | 19 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 8 | |
▷ Global constants | 2 | 25.00% |
▷ Class constants | 6 | 75.00% |
▷ Public constants | 6 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
PNG images were not found in this plugin