Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼0.01MB] [CPU: ▼8.98ms] Passed 4 tests
Analyzing server-side resources used by NewPath WildApricotPress Add-on – iFrame Widget
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 37.50 ▼10.05 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 54.12 ▼10.27 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 50.83 ▲0.82 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 93.10 ▼15.61 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.18 ▲0.02 |
Server storage [IO: ▲1.35MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 20 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for NewPath WildApricotPress Add-on – iFrame Widget
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.40 ▲0.04 | 2.10 ▲0.20 | 43.58 ▲0.08 |
| Dashboard /wp-admin | 2,195 ▲18 | 5.66 ▼0.03 | 91.04 ▲1.80 | 40.96 ▲0.76 |
| Posts /wp-admin/edit.php | 2,100 ▲3 | 2.06 ▲0.05 | 39.68 ▲3.75 | 34.67 ▼1.50 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲14 | 23.14 ▼0.20 | 687.49 ▼9.12 | 54.10 ▲2.39 |
| Media Library /wp-admin/upload.php | 1,400 ▼3 | 4.32 ▲0.15 | 107.76 ▼3.01 | 46.38 ▼8.59 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
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
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/newpath-wildapricotpress-add-on-iframe-widget/wap-addon-wa-iframe.php:30
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that need to be fixed:
- Screenshots: Add an image for screenshot #1 (Inserting WildApricot Press iframe into a page)
newpath-wildapricotpress-add-on-iframe-widget/wap-addon-wa-iframe.php 85% from 13 tests
This is the main PHP file of "NewPath WildApricotPress Add-on – iFrame Widget" version 1.0.1, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
It is important to fix the following:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Main file name: It is recommended to name the main PHP file as the plugin slug ("newpath-wildapricotpress-add-on-iframe-widget.php" instead of "wap-addon-wa-iframe.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Everything looks great! No dangerous files found in this plugin39,142 lines of code in 14 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JSON | 3 | 0 | 0 | 38,113 |
| Markdown | 1 | 121 | 0 | 553 |
| JavaScript | 4 | 74 | 240 | 390 |
| PHP | 2 | 15 | 37 | 61 |
| Sass | 2 | 2 | 0 | 18 |
| CSS | 2 | 2 | 13 | 7 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.14 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 6 | |
| ▷ Named functions | 6 | 100.00% |
| ▷ Anonymous functions | 0 | 0.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
No PNG files were detected