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 gracefully, with no errors
Server metrics [RAM: ▲0.06MB] [CPU: ▼9.26ms] Passed 4 tests
This is a short check of server-side resources used by Footer Design For WPBakery Page Builder
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.53 ▲0.07 | 41.13 ▼1.53 |
| Dashboard /wp-admin | 3.37 ▲0.03 | 48.65 ▼18.65 |
| Posts /wp-admin/edit.php | 3.48 ▲0.13 | 54.85 ▲7.75 |
| Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 87.14 ▼18.55 |
| Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 38.09 ▲1.69 |
| All Footeres /wp-admin/edit.php?post_type=wpmp_footer_vc_pt | 3.33 | 39.40 |
| Add New /wp-admin/post-new.php?post_type=wpmp_footer_vc_pt | 3.40 | 46.74 |
| Settings /wp-admin/edit.php?post_type=wpmp_footer_vc_pt&page=footer_setting | 3.26 | 36.17 |
Server storage [IO: ▲0.25MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 20 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-comments |
| can_compress_scripts |
| db_upgraded |
| widget_recent-posts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by Footer Design For WPBakery Page Builder
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,914 ▲168 | 13.96 ▼0.42 | 6.13 ▲4.45 | 40.15 ▼2.56 |
| Dashboard /wp-admin | 2,233 ▲48 | 5.86 ▲0.01 | 102.28 ▼7.83 | 78.27 ▲32.34 |
| Posts /wp-admin/edit.php | 2,119 ▲30 | 1.98 ▼0.01 | 39.42 ▲1.89 | 37.81 ▲1.87 |
| Add New Post /wp-admin/post-new.php | 1,540 ▲26 | 23.28 ▲5.70 | 643.62 ▲21.67 | 192.67 ▲141.73 |
| Media Library /wp-admin/upload.php | 1,415 ▲27 | 4.26 ▲0.10 | 121.91 ▲11.66 | 80.54 ▲34.67 |
| All Footeres /wp-admin/edit.php?post_type=wpmp_footer_vc_pt | 1,092 | 1.98 | 36.74 | 30.40 |
| Add New /wp-admin/post-new.php?post_type=wpmp_footer_vc_pt | 2,175 | 7.55 | 166.82 | 122.06 |
| Settings /wp-admin/edit.php?post_type=wpmp_footer_vc_pt&page=footer_setting | 850 | 2.02 | 26.07 | 28.44 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- can_compress_scripts
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)
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_posts() in wp-content/plugins/footer-design-for-wpbakery-page-builder/includes/views/settings.views.php:6
- > PHP Warning
Use of undefined constant WPMP_FOOTER_VC_POST_TYPE - assumed 'WPMP_FOOTER_VC_POST_TYPE' (this will throw an Error in a future version of PHP) in wp-content/plugins/footer-design-for-wpbakery-page-builder/includes/views/settings.views.php on line 4
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need your attention:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (it is very easy), #2 (Great footer)
footer-design-for-wpbakery-page-builder/index.php 92% from 13 tests
The principal PHP file in "Footer Design For WPBakery Page Builder" v. 1.0 is loaded by WordPress automatically on each request
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("footer-design-for-wpbakery-page-builder.php" instead of "index.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 plugin311 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 26 | 7 | 270 |
| Sass | 2 | 0 | 0 | 20 |
| CSS | 1 | 3 | 1 | 13 |
| JavaScript | 1 | 0 | 0 | 8 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.41 |
| Average class complexity | 3.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 8.00 |
| Average method complexity | 1.50 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 4.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 16 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 16 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 6 | |
| ▷ Global constants | 6 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
5 PNG files occupy 0.21MB with 0.11MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/admin/images/icon.png | 2.91KB | 0.17KB | ▼ 94.05% |
| assets/frontend/images/placeholder.png | 9.01KB | 9.59KB | 0.00% |
| assets/frontend/images/Screenshot_2.png | 78.13KB | 34.27KB | ▼ 56.13% |
| assets/frontend/images/Screenshot_1.png | 69.12KB | 36.25KB | ▼ 47.56% |
| assets/frontend/images/Screenshot_3.png | 53.16KB | 21.58KB | ▼ 59.40% |