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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.09MB] [CPU: ▼5.41ms] Passed 4 tests
This is a short check of server-side resources used by WP Gatsby Markdown Exporter
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.55 ▲0.09 | 39.07 ▼9.92 |
| Dashboard /wp-admin | 3.39 ▲0.09 | 58.17 ▼0.83 |
| Posts /wp-admin/edit.php | 3.51 ▲0.15 | 54.77 ▲2.08 |
| Add New Post /wp-admin/post-new.php | 5.97 ▲0.09 | 89.56 ▼10.31 |
| Media Library /wp-admin/upload.php | 3.32 ▲0.09 | 38.06 ▼0.56 |
Server storage [IO: ▲0.58MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 185 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_theysaidso_widget |
| can_compress_scripts |
Browser metrics Passed 4 tests
WP Gatsby Markdown Exporter: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,805 ▲44 | 14.61 ▲0.21 | 1.77 ▲0.00 | 43.45 ▼4.17 |
| Dashboard /wp-admin | 2,214 ▲37 | 5.56 ▼0.10 | 90.01 ▼4.87 | 37.33 ▼7.15 |
| Posts /wp-admin/edit.php | 2,116 ▲19 | 1.98 ▼0.03 | 34.36 ▼1.60 | 34.94 ▲0.23 |
| Add New Post /wp-admin/post-new.php | 1,539 ▲13 | 23.54 ▲0.63 | 692.78 ▼5.65 | 50.80 ▼13.01 |
| Media Library /wp-admin/upload.php | 1,416 ▲16 | 4.14 ▼0.23 | 96.08 ▼14.02 | 42.39 ▼2.82 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
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
Please fix the following items
- 122× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-gatsby-markdown-exporter/vendor/composer/installers/src/Composer/Installers/PhpBBInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-gatsby-markdown-exporter/vendor/composer/installers/src/Composer/Installers/SilverStripeInstaller.php:6
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-gatsby-markdown-exporter/vendor/composer/installers/src/Composer/Installers/LithiumInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-gatsby-markdown-exporter/vendor/composer/installers/src/Composer/Installers/VanillaInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-gatsby-markdown-exporter/vendor/composer/installers/src/Composer/Installers/LaravelInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-gatsby-markdown-exporter/vendor/composer/installers/src/Composer/Installers/ClanCatsFrameworkInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-gatsby-markdown-exporter/vendor/composer/installers/src/Composer/Installers/AimeosInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-gatsby-markdown-exporter/vendor/composer/installers/src/Composer/Installers/FuelphpInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-gatsby-markdown-exporter/vendor/composer/installers/src/Composer/Installers/MediaWikiInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-gatsby-markdown-exporter/vendor/composer/installers/src/Composer/Installers/CiviCrmInstaller.php:4
- > 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)
There were no browser issues found
Optimizations
Plugin configuration 93% 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
4 plugin tags: gatsby, jamstack, export, markdown
wp-gatsby-markdown-exporter/gatsby-markdown-exporter.php 85% from 13 tests
Analyzing the main PHP file in "WP Gatsby Markdown Exporter" version 0.3.3
You should first fix the following items:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wp-gatsby-markdown-exporter.php" instead of "gatsby-markdown-exporter.php")
Code Analysis 97% from 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
Success! There were no dangerous files found in this plugin7,771 lines of code in 174 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 152 | 1,484 | 2,700 | 6,395 |
| JSON | 7 | 0 | 0 | 665 |
| Markdown | 9 | 271 | 0 | 619 |
| XML | 4 | 10 | 0 | 78 |
| YAML | 2 | 0 | 6 | 14 |
PHP code 50% from 2 tests
A short review of cyclomatic complexity and code structure
It is recommended to fix the following
- Cyclomatic complexity of methods should be reduced to less than 100 (currently 112)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.52 |
| Average class complexity | 8.52 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 256.00 |
| Average method complexity | 4.15 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 112.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 11 | |
| Interfaces | 7 | |
| Traits | 0 | |
| Classes | 136 | |
| ▷ Abstract classes | 1 | 0.74% |
| ▷ Concrete classes | 135 | 99.26% |
| ▷ Final classes | 3 | 2.22% |
| Methods | 362 | |
| ▷ Static methods | 43 | 11.88% |
| ▷ Public methods | 249 | 68.78% |
| ▷ Protected methods | 46 | 12.71% |
| ▷ Private methods | 67 | 18.51% |
| Functions | 37 | |
| ▷ Named functions | 23 | 62.16% |
| ▷ Anonymous functions | 14 | 37.84% |
| Constants | 23 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 23 | 100.00% |
| ▷ Public constants | 23 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
There were not PNG files found in your plugin