Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.06MB] [CPU: ▼9.30ms] Passed 4 tests
A check of server-side resources used by Landing Page Creator With Custom Posts
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.54 ▲0.08 | 37.74 ▼11.65 |
Dashboard /wp-admin | 3.38 ▲0.03 | 47.88 ▼15.28 |
Posts /wp-admin/edit.php | 3.49 ▲0.13 | 51.88 ▲3.18 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.07 | 85.63 ▼12.26 |
Media Library /wp-admin/upload.php | 3.30 ▲0.07 | 40.35 ▲1.99 |
Server storage [IO: ▲0.12MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 12 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_recent-posts |
widget_theysaidso_widget |
widget_recent-comments |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Landing Page Creator With Custom Posts
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,813 ▲67 | 13.32 ▼0.91 | 4.26 ▲2.59 | 40.84 ▲3.34 |
Dashboard /wp-admin | 2,216 ▲33 | 5.77 ▲0.86 | 98.07 ▼14.99 | 40.06 ▼5.64 |
Posts /wp-admin/edit.php | 2,104 ▲12 | 2.01 ▲0.01 | 39.39 ▲2.05 | 38.20 ▼0.32 |
Add New Post /wp-admin/post-new.php | 1,546 ▲10 | 23.49 ▲0.41 | 658.18 ▲6.29 | 54.83 ▼14.36 |
Media Library /wp-admin/upload.php | 1,404 ▲16 | 4.22 ▲0.15 | 98.20 ▼16.80 | 47.24 ▲0.47 |
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
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
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
The following issues need your attention
- 4× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/landing-page-creator-with-custom-posts/landingpage-creator-with-custom-posts.php
- > /wp-content/plugins/landing-page-creator-with-custom-posts/templates-parts/navigation.php
- > /wp-content/plugins/landing-page-creator-with-custom-posts/landingpage_lpccp_admin.php
- > /wp-content/plugins/landing-page-creator-with-custom-posts/landingpage_lpccp_template.php
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 88% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that require attention:
- Tags: Too many tags (45 tag instead of maximum 10); only the first 5 tags are used in your directory listing
- Requires php: Version not formatted correctly
landing-page-creator-with-custom-posts/landingpage-creator-with-custom-posts.php 92% from 13 tests
The principal PHP file in "Landing Page Creator With Custom Posts" v. 0.3.3 is loaded by WordPress automatically on each request
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("landing-page-creator-with-custom-posts.php" instead of "landingpage-creator-with-custom-posts.php")
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
Good job! No executable or dangerous file extensions detected2,187 lines of code in 7 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 1 | 48 | 1 | 997 |
PHP | 4 | 308 | 385 | 986 |
PO File | 1 | 88 | 105 | 198 |
JavaScript | 1 | 3 | 0 | 6 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.36 |
Average class complexity | 44.50 |
▷ Minimum class complexity | 19.00 |
▷ Maximum class complexity | 70.00 |
Average method complexity | 3.65 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 12.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 33 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 22 | 66.67% |
▷ Protected methods | 11 | 33.33% |
▷ Private methods | 0 | 0.00% |
Functions | 2 | |
▷ Named functions | 1 | 50.00% |
▷ Anonymous functions | 1 | 50.00% |
Constants | 5 | |
▷ Global constants | 5 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.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
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 |
assets/images/section-icon.png | 0.96KB | 0.13KB | ▼ 86.83% |
assets/images/landingpage-icon.png | 0.96KB | 0.13KB | ▼ 86.97% |