88% engagebay-landing-page-builder

Code Review | EngageBay Landing Pages - Responsive landing pages for lead generation and conversions

WordPress plugin EngageBay Landing Pages - Responsive landing pages for lead generation and conversions scored 88% from 54 tests.

About plugin

  • Plugin page: engagebay-landing...
  • Plugin version: 1.7
  • PHP version: 7.4.16
  • WordPress compatibility: 3.7-5.8
  • WordPress version: 5.8.1
  • First release: Sep 3, 2018
  • Latest release: Aug 3, 2021
  • Number of updates: 18
  • Update frequency: every 59.2 days
  • Top authors: engagebay (100%)

Code review

54 tests

User reviews

2 reviews

Install metrics

200+ active / 4,406 total downloads

Benchmarks

Plugin footprint Passed 16 tests

Installer Passed 1 test

🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully

Server metrics [RAM: ▲0.20MB] [CPU: ▼142.44ms] 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
PageMemory (MB)CPU Time (ms)
Home /3.04 ▲0.2137.91 ▲3.53
Dashboard /wp-admin3.27 ▲0.2143.82 ▼6.41
Posts /wp-admin/edit.php3.38 ▲0.2744.53 ▼0.23
Add New Post /wp-admin/post-new.php5.63 ▲0.1988.87 ▼566.65
Media Library /wp-admin/upload.php3.21 ▲0.2134.22 ▲3.59

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, no new options

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
PageNodesMemory (MB)Script (ms)Layout (ms)
Home /4,182 ▲58616.45 ▲0.7913.11 ▲1.9838.82 ▼6.67
Dashboard /wp-admin3,439 ▲5056.22 ▲0.13138.63 ▼18.25149.61 ▲38.69
Posts /wp-admin/edit.php2,756 ▲172.62 ▼0.0963.52 ▼8.8196.85 ▲13.88
Add New Post /wp-admin/post-new.php1,627 ▲1221.59 ▲0.55294.14 ▼2.75102.36 ▼1.22
Media Library /wp-admin/upload.php1,764 ▼435.03 ▲0.02135.46 ▼22.88141.83 ▲27.82

Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests

🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Uninstaller ran successfully

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: Interface 'GuzzleHttp\\Promise\\PromiseInterface' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/guzzlehttp/promises/src/Promise.php:9
    • > PHP Fatal error
      Trait 'League\\OAuth2\\Client\\Tool\\RequiredParameterTrait' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/league/oauth2-client/src/Grant/AbstractGrant.php on line 31
    • > 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: Interface 'GuzzleHttp\\Promise\\TaskQueueInterface' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/guzzlehttp/promises/src/TaskQueue.php:13
    • > 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/Coroutine.php:43
    • > PHP Fatal error
      Uncaught Error: Interface 'GuzzleHttp\\Exception\\GuzzleException' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/guzzlehttp/guzzle/src/Exception/InvalidArgumentException.php:5
    • > PHP Fatal error
      Uncaught Error: Class 'GuzzleHttp\\Exception\\RequestException' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/guzzlehttp/guzzle/src/Exception/BadResponseException.php:10
    • > 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: Class 'League\\OAuth2\\Client\\Grant\\AbstractGrant' not found in wp-content/plugins/engagebay-landing-page-builder/vendor/league/oauth2-client/src/Grant/AuthorizationCode.php:22

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)
The official readme.txt might help

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 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:
LanguageFilesBlank linesComment linesLines of code
PHP1332,3556,41814,196
Markdown181,29503,775
JSON1210981
CSS2405650
SVG13211558
JavaScript5233130
XML10019
Dockerfile18010
make1409
Bourne Shell1203

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 code0.45
Average class complexity13.04
▷ Minimum class complexity1.00
▷ Maximum class complexity153.00
Average method complexity2.69
▷ Minimum method complexity1.00
▷ Maximum method complexity27.00
Code structure
Namespaces18
Interfaces19
Traits9
Classes83
▷ Abstract classes22.41%
▷ Concrete classes8197.59%
▷ Final classes1316.05%
Methods827
▷ Static methods12715.36%
▷ Public methods63877.15%
▷ Protected methods587.01%
▷ Private methods13115.84%
Functions228
▷ Named functions13960.96%
▷ Anonymous functions8939.04%
Constants105
▷ Global constants4441.90%
▷ Class constants6158.10%
▷ Public constants61100.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.00MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant
FileSize - originalSize - compressedSavings
images/icon.png0.45KB0.72KB0.00%
images/preview.png0.84KB0.59KB▼ 29.84%
images/preview-n.png2.21KB1.84KB▼ 17.02%
images/refresh-icon.png4.46KB2.66KB▼ 40.53%
images/pictures.png1.00KB0.93KB▼ 7.69%