Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.21MB] [CPU: ▼9.08ms] Passed 4 tests
This is a short check of server-side resources used by EngageBay Landing Pages - Responsive landing pages for lead generation and conversions
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.69 ▲0.22 | 37.71 ▼1.63 |
Dashboard /wp-admin | 3.52 ▲0.17 | 45.74 ▼7.60 |
Posts /wp-admin/edit.php | 3.63 ▲0.27 | 50.49 ▼4.24 |
Add New Post /wp-admin/post-new.php | 6.12 ▲0.23 | 80.04 ▼22.85 |
Media Library /wp-admin/upload.php | 3.44 ▲0.21 | 32.54 ▲1.02 |
Server storage [IO: ▲1.20MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 211 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
db_upgraded |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for EngageBay Landing Pages - Responsive landing pages for lead generation and conversions
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,181 ▲395 | 14.35 ▲0.07 | 1.63 ▼0.42 | 33.14 ▼9.77 |
Dashboard /wp-admin | 2,584 ▲404 | 5.76 ▲0.10 | 81.82 ▼4.61 | 88.00 ▲50.00 |
Posts /wp-admin/edit.php | 2,120 ▲17 | 1.99 ▼0.00 | 38.12 ▼5.39 | 34.17 ▼7.03 |
Add New Post /wp-admin/post-new.php | 1,552 ▲26 | 23.05 ▼0.75 | 711.82 ▲35.60 | 61.81 ▲1.02 |
Media Library /wp-admin/upload.php | 1,407 ▲7 | 4.21 ▼0.00 | 97.93 ▲2.72 | 64.95 ▲24.49 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- can_compress_scripts
Smoke tests 50% 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)
Even though everything seems fine, this is not an exhaustive test
SRP 0% 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
Almost there! Just fix the following items
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/engagebay-landing-page-builder/index.php
- 58× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\BadResponseException' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/guzzlehttp/guzzle/src/Exception/ClientException.php:7
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\RequestInterface' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/psr/http-message/src/ServerRequestInterface.php:43
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\RequestInterface' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/guzzlehttp/psr7/src/Request.php:12
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\BadResponseException' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/guzzlehttp/guzzle/src/Exception/ServerException.php:7
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromiseInterface' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/guzzlehttp/promises/src/RejectedPromise.php:10
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\ResponseInterface' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/guzzlehttp/psr7/src/Response.php:10
- > PHP Fatal error
Uncaught Error: Class 'League\\OAuth2\\Client\\Grant\\AbstractGrant' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/league/oauth2-client/src/Grant/RefreshToken.php:22
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/guzzlehttp/psr7/src/PumpStream.php:16
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromiseInterface' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/guzzlehttp/promises/src/FulfilledPromise.php:10
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Psr7\\Request' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/guzzlehttp/psr7/src/ServerRequest.php:25
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Please fix the following attributes:
- Tags: There are too many tags (25 tag instead of maximum 10)
engagebay-landing-page-builder/index.php 85% from 13 tests
The main file in "EngageBay Landing Pages - Responsive landing pages for lead generation and conversions" v. 1.7.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Description: Please keep the plugin description shorter than 140 characters (currently 196 characters long)
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("engagebay-landing-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
No dangerous file extensions were detected20,331 lines of code in 187 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 133 | 2,355 | 6,418 | 14,196 |
Markdown | 18 | 1,295 | 0 | 3,775 |
JSON | 12 | 1 | 0 | 981 |
CSS | 2 | 40 | 5 | 650 |
SVG | 13 | 2 | 11 | 558 |
JavaScript | 5 | 23 | 3 | 130 |
XML | 1 | 0 | 0 | 19 |
Dockerfile | 1 | 8 | 0 | 10 |
make | 1 | 4 | 0 | 9 |
Bourne Shell | 1 | 2 | 0 | 3 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.45 |
Average class complexity | 13.04 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 153.00 |
Average method complexity | 2.69 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 27.00 |
Code structure | ||
---|---|---|
Namespaces | 18 | |
Interfaces | 19 | |
Traits | 9 | |
Classes | 83 | |
▷ Abstract classes | 2 | 2.41% |
▷ Concrete classes | 81 | 97.59% |
▷ Final classes | 13 | 16.05% |
Methods | 827 | |
▷ Static methods | 127 | 15.36% |
▷ Public methods | 638 | 77.15% |
▷ Protected methods | 58 | 7.01% |
▷ Private methods | 131 | 15.84% |
Functions | 228 | |
▷ Named functions | 139 | 60.96% |
▷ Anonymous functions | 89 | 39.04% |
Constants | 105 | |
▷ Global constants | 44 | 41.90% |
▷ Class constants | 61 | 58.10% |
▷ Public constants | 61 | 100.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
8 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/edit.png | 0.42KB | 0.29KB | ▼ 31.24% |
images/preview.png | 0.84KB | 0.59KB | ▼ 29.84% |
images/icon_2.png | 1.67KB | 0.88KB | ▼ 47.05% |
images/pictures.png | 1.00KB | 0.93KB | ▼ 7.69% |
images/icon.png | 0.45KB | 0.72KB | 0.00% |