Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼1.51ms] Passed 4 tests
This is a short check of server-side resources used by WP Landing Page
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.04 | 34.89 ▼5.41 |
| Dashboard /wp-admin | 3.34 ▲0.04 | 47.27 ▼0.36 |
| Posts /wp-admin/edit.php | 3.39 ▲0.04 | 49.76 ▲3.43 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 91.10 ▼0.65 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.04 | 34.18 ▲0.38 |
| Access /wp-admin/edit.php?post_type=wplp_landingpage&page=access | 3.24 | 30.61 |
| All Landing Pages /wp-admin/edit.php?post_type=wplp_landingpage | 3.31 | 33.46 |
| Add New /wp-admin/post-new.php?post_type=wplp_landingpage | 3.30 | 37.65 |
Server storage [IO: ▲2.62MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 306 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WP Landing Page
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,855 ▲120 | 13.80 ▼0.58 | 1.69 ▼0.40 | 39.45 ▼9.94 |
| Dashboard /wp-admin | 2,256 ▲68 | 5.96 ▼0.01 | 108.20 ▼9.19 | 40.42 ▼3.86 |
| Posts /wp-admin/edit.php | 2,144 ▲58 | 2.31 ▲0.32 | 43.17 ▲7.36 | 34.58 ▲2.20 |
| Add New Post /wp-admin/post-new.php | 1,558 ▲44 | 23.19 ▲5.76 | 577.87 ▼102.28 | 32.21 ▼12.92 |
| Media Library /wp-admin/upload.php | 1,438 ▲47 | 4.40 ▲0.20 | 95.07 ▲1.64 | 40.53 ▼0.19 |
| Access /wp-admin/edit.php?post_type=wplp_landingpage&page=access | 852 | 1.94 | 26.89 | 35.66 |
| All Landing Pages /wp-admin/edit.php?post_type=wplp_landingpage | 1,111 | 2.22 | 33.88 | 29.37 |
| Add New /wp-admin/post-new.php?post_type=wplp_landingpage | 2,452 | 3.98 | 97.68 | 77.43 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
Smoke tests 50% 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 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following items
- 3× PHP files output text when accessed directly:
- > /wp-content/plugins/wp-landing-page/lib/plupload/examples/jquery/s3.php
- > /wp-content/plugins/wp-landing-page/lib/plupload/examples/upload.php
- > /wp-content/plugins/wp-landing-page/lib/plupload/examples/dump.php
- 14× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-landing-page/wplandingpage.php on line 28
- > PHP Warning
include_once(): Failed opening 'ABSPATHwp-admin/includes/plugin.php' for inclusion (include_path='.:/usr/share/php') in wp-content/plugins/wp-landing-page/wplandingpage.php on line 28
- > PHP Fatal error
Uncaught Error: Call to undefined function get_post_meta() in wp-content/plugins/wp-landing-page/templates/base/single-landingpage.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function wplp_editable_text() in wp-content/plugins/wp-landing-page/templates/free1/index.php:6
- > PHP Warning
include_once(ABSPATHwp-admin/includes/plugin.php): failed to open stream: No such file or directory in wp-content/plugins/wp-landing-page/wplandingpage.php on line 28
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-landing-page/includes/custom-post-type.php:48
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-landing-page/includes/access.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-landing-page/includes/colors-and-css.php:87
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-landing-page/includes/default-templates.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-landing-page/includes/default-templates.php:11
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
These attributes need to be fixed:
- Screenshots: Add a description for screenshot #4 in wp-landing-page/assets to your readme.txt
- Tags: Please reduce the number of tags, currently 30 tag instead of maximum 10
wp-landing-page/wplandingpage.php 77% from 13 tests
This is the main PHP file of "WP Landing Page" version 0.9.3, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wp-landing-page.php" instead of "wplandingpage.php")
- 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
- Domain Path: The domain path is invalid: folder "/languages" does not exist
Code Analysis 5% from 3 tests
File types 0% from 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Please fix the following items
- For security reasons, never distribute binary or executable files with your plugin
- .xap - Silverlight Application Package in Microsoft Silverlight
- ☣ wp-content/plugins/wp-landing-page/lib/plupload/js/Moxie.xap
- .xap - Silverlight Application Package in Microsoft Silverlight
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 157 | 6,952 | 7,642 | 24,827 |
| Sass | 77 | 1,243 | 1,601 | 5,752 |
| PHP | 19 | 228 | 141 | 795 |
| Markdown | 5 | 277 | 0 | 589 |
| CSS | 7 | 108 | 22 | 547 |
| HTML | 5 | 109 | 28 | 483 |
| SVG | 1 | 0 | 0 | 288 |
| JSON | 7 | 0 | 0 | 154 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.27 |
| 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 | 31 | |
| ▷ Named functions | 31 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.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.07MB with 0.02MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| lib/plupload/js/jquery.plupload.queue/img/buttons-disabled.png | 1.26KB | 1.02KB | ▼ 19.20% |
| lib/plupload/js/jquery.plupload.queue/img/transp50.png | 0.39KB | 0.11KB | ▼ 72.18% |
| lib/plupload/js/jquery.plupload.queue/img/buttons.png | 1.41KB | 1.15KB | ▼ 18.00% |
| lib/plupload/js/jquery.ui.plupload/img/plupload.png | 6.44KB | 2.99KB | ▼ 53.58% |
| images/smartphone.png | 65.45KB | 68.88KB | 0.00% |