Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼5.85ms] Passed 4 tests
A check of server-side resources used by Formidable PRO2PDF
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.05 | 41.17 ▼1.95 |
| Dashboard /wp-admin | 3.35 ▲0.00 | 47.89 ▼14.35 |
| Posts /wp-admin/edit.php | 3.40 ▲0.04 | 48.71 ▲5.19 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.05 | 79.27 ▼8.41 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 36.23 ▲1.30 |
Server storage [IO: ▲1.81MB] [DB: ▲0.07MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 30 new files
Database: 3 new tables, 12 new options
| New tables |
|---|
| wp_fpropdf_tmp |
| wp_fpropdf_layouts |
| wp_fpropdf_fields |
| New WordPress options |
|---|
| db_upgraded |
| fpropdf_limit_dropdowns |
| fpropdf_version |
| fpropdf_installed_version |
| widget_theysaidso_widget |
| fpropdf_enable_security |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_recent-comments |
| ... |
Browser metrics Passed 4 tests
Formidable PRO2PDF: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,807 ▲60 | 14.13 ▼0.21 | 1.71 ▼0.17 | 43.35 ▼0.89 |
| Dashboard /wp-admin | 2,195 ▲15 | 5.53 ▼0.12 | 97.97 ▲8.36 | 75.54 ▲35.51 |
| Posts /wp-admin/edit.php | 2,112 ▲15 | 1.97 ▼0.03 | 33.49 ▼3.87 | 32.34 ▼0.82 |
| Add New Post /wp-admin/post-new.php | 1,554 ▲28 | 22.97 ▼0.41 | 642.44 ▼60.82 | 61.16 ▲9.58 |
| Media Library /wp-admin/upload.php | 1,412 ▲12 | 4.27 ▲0.05 | 96.63 ▼10.61 | 68.69 ▲23.14 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- The plugin did not uninstall successfully, leaving 1 table in the database
- wp_fpropdf_tmp
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Congratulations! This plugin passed the SRP test
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 96% 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
7 plugin tags: forms, pdftk, pro2pdf, formidable, pdf...
formidablepro-2-pdf/fpropdf.php 92% from 13 tests
The main file in "Formidable PRO2PDF" v. 3.18 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("formidablepro-2-pdf.php" instead of "fpropdf.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Everything looks great! No dangerous files found in this plugin6,897 lines of code in 23 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 15 | 878 | 123 | 5,517 |
| JavaScript | 2 | 115 | 1 | 1,061 |
| CSS | 3 | 16 | 0 | 181 |
| Sass | 2 | 13 | 8 | 137 |
| JSON | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.60 |
| Average class complexity | 9.30 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 42.00 |
| Average method complexity | 6.53 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 28.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 10 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 10 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 15 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 15 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 72 | |
| ▷ Named functions | 72 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 14 | |
| ▷ Global constants | 14 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| res/blank.png | 0.14KB | 0.08KB | ▼ 43.84% |
| res/icon.png | 0.73KB | 0.65KB | ▼ 10.31% |