Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.58ms] Passed 4 tests
Analyzing server-side resources used by Substack Importer
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 38.99 ▼2.40 |
Dashboard /wp-admin | 3.31 ▲0.00 | 48.89 ▼0.53 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 45.90 ▲0.61 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 94.06 ▼7.99 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.26 ▲1.61 |
Server storage [IO: ▲0.12MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 30 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
can_compress_scripts |
db_upgraded |
widget_recent-comments |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Substack Importer
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 13.32 ▼1.19 | 1.68 ▲0.08 | 41.23 ▲3.33 |
Dashboard /wp-admin | 2,209 ▲20 | 5.90 ▲0.93 | 103.80 ▼15.74 | 37.96 ▼9.25 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.05 ▲0.03 | 37.26 ▼2.59 | 32.32 ▼3.09 |
Add New Post /wp-admin/post-new.php | 1,534 ▲14 | 23.37 ▲0.26 | 600.43 ▼38.23 | 48.23 ▼5.74 |
Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.25 ▲0.08 | 95.48 ▲0.34 | 40.95 ▲0.38 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though everything seems fine, this is not 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
Almost there! Just fix the following items
- 5× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/substack-importer/partials/container.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/substack-importer/partials/start-screen.php:2
- > PHP Notice
Undefined variable: wp_importer in wp-content/plugins/substack-importer/partials/pre-import-screen.php on line 1
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/substack-importer/partials/progress.php:1
- > PHP Fatal error
Uncaught Error: Call to a member function import_options() on null in wp-content/plugins/substack-importer/partials/pre-import-screen.php:1
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
2 plugin tags: substack, importer
substack-importer/substack-importer.php Passed 13 tests
This is the main PHP file of "Substack Importer" version 1.0.8, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
74 characters long description:
A plugin that lets you import content from Substack to your WordPress site
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
No dangerous file extensions were detected2,531 lines of code in 26 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 22 | 582 | 981 | 2,009 |
JSON | 2 | 1 | 0 | 471 |
CSS | 1 | 7 | 0 | 32 |
JavaScript | 1 | 5 | 0 | 19 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
Average class complexity | 22.50 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 86.00 |
Average method complexity | 2.85 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 31.00 |
Code structure | ||
---|---|---|
Namespaces | 4 | |
Interfaces | 1 | |
Traits | 0 | |
Classes | 11 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 11 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 137 | |
▷ Static methods | 19 | 13.87% |
▷ Public methods | 73 | 53.28% |
▷ Protected methods | 51 | 37.23% |
▷ Private methods | 13 | 9.49% |
Functions | 8 | |
▷ Named functions | 2 | 25.00% |
▷ Anonymous functions | 6 | 75.00% |
Constants | 4 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 4 | 100.00% |
▷ Public constants | 4 | 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
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/icon-256x256.png | 5.55KB | 2.07KB | ▼ 62.72% |