72% insiteful

Code Review | Insiteful — Form Abandonment Tracking, Partial Entries, Save & Continue Later

WordPress plugin Insiteful — Form Abandonment Tracking, Partial Entries, Save & Continue Later scored72%from 54 tests.

About plugin

  • Plugin page: insiteful
  • Plugin version: 1.1.0
  • PHP version: 7.4.16
  • WordPress compatibility: 3.0.1-6.1
  • WordPress version: 6.3.1
  • First release: Sep 24, 2020
  • Latest release: Dec 9, 2022
  • Number of updates: 7
  • Update frequency: every 115.2 days
  • Top authors: insitefulco (100%)

Code review

54 tests

User reviews

3 reviews

Install metrics

30+ active /723 total downloads

Benchmarks

Plugin footprint 83% from 16 tests

Installer Passed 1 test

🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully

Server metrics [RAM: ▲0.06MB] [CPU: ▼11.86ms] Passed 4 tests

Analyzing server-side resources used by Insiteful — Form Abandonment Tracking, Partial Entries, Save & Continue Later
Server-side resource usage in normal parameters
PageMemory (MB)CPU Time (ms)
Home /3.50 ▲0.0422.93 ▼16.38
Dashboard /wp-admin3.36 ▲0.0639.98 ▼10.62
Posts /wp-admin/edit.php3.47 ▲0.1245.47 ▲2.06
Add New Post /wp-admin/post-new.php5.96 ▲0.0883.65 ▼15.58
Media Library /wp-admin/upload.php3.28 ▲0.0630.65 ▼4.85
Insiteful /wp-admin/options-general.php?page=insiteful3.2625.79

Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests

Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 22 new files
Database: no new tables, 6 new options
New WordPress options
widget_theysaidso_widget
db_upgraded
widget_recent-posts
can_compress_scripts
theysaidso_admin_options
widget_recent-comments

Browser metrics Passed 4 tests

Insiteful — Form Abandonment Tracking, Partial Entries, Save & Continue Later: an overview of browser usage
Normal browser usage
PageNodesMemory (MB)Script (ms)Layout (ms)
Home /2,842 ▲7113.82 ▼0.769.77 ▲7.3934.64 ▼7.86
Dashboard /wp-admin2,211 ▲234.85 ▼0.03108.63 ▼9.3542.88 ▼2.09
Posts /wp-admin/edit.php2,100 ▲112.00 ▼0.0239.46 ▲2.0835.92 ▲3.15
Add New Post /wp-admin/post-new.php1,521 ▼323.43 ▲0.04651.64 ▼33.9656.64 ▲6.63
Media Library /wp-admin/upload.php1,396 ▲144.33 ▲0.1396.92 ▼1.9741.62 ▼5.07
Insiteful /wp-admin/options-general.php?page=insiteful9352.1627.0872.61

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
It is recommended to fix the following
  • This plugin did not uninstall successfully, leaving 6 options in the database
    • can_compress_scripts
    • widget_theysaidso_widget
    • theysaidso_admin_options
    • db_upgraded
    • widget_recent-comments
    • widget_recent-posts

Smoke tests 25% from 4 tests

Server-side errors 0% from 1 test

🔹 Test weight: 20 | This is a shallow check for server-side errors
These server-side errors were triggered
    • > GET request to /wp-admin/options-general.php?page=insiteful
    • > Notice in wp-content/plugins/insiteful/admin/partials/insiteful-admin-display.php+20
    Trying to access array offset on value of type bool

SRP 0% from 2 tests

🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
  • 1× PHP files output text when accessed directly:
    • > /wp-content/plugins/insiteful/public/partials/insiteful-public-display.php
  • 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
    • > PHP Fatal error
      Uncaught Error: Call to undefined function get_option() in wp-content/plugins/insiteful/admin/partials/insiteful-admin-display.php:17

User-side errors Passed 1 test

🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side

Optimizations

Plugin configuration 90% 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
Attributes that require attention:
  • Screenshots: Please describe screenshot #3 in insiteful/assets to your readme.txt
You can take inspiration from this readme.txt

insiteful/insiteful.php 85% from 13 tests

"Insiteful — Form Abandonment Tracking, Partial Entries, Save & Continue Later" version 1.1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please make the necessary changes and fix the following:
  • Description: Keep the plugin description shorter than 140 characters (currently 245 characters long)
  • Plugin Name: Keep the plugin name shorter than 70 characters (currently 79 characters long)

Code Analysis Passed 3 tests

File types Passed 1 test

🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected265 lines of code in 16 files:
LanguageFilesBlank linesComment linesLines of code
PHP12138574259
JavaScript24546
CSS2080

PHP code Passed 2 tests

An overview of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity
Average complexity per logical line of code0.10
Average class complexity1.71
▷ Minimum class complexity1.00
▷ Maximum class complexity3.00
Average method complexity1.18
▷ Minimum method complexity1.00
▷ Maximum method complexity3.00
Code structure
Namespaces0
Interfaces0
Traits0
Classes7
▷ Abstract classes00.00%
▷ Concrete classes7100.00%
▷ Final classes00.00%
Methods28
▷ Static methods27.14%
▷ Public methods2382.14%
▷ Protected methods00.00%
▷ Private methods517.86%
Functions3
▷ Named functions3100.00%
▷ Anonymous functions00.00%
Constants1
▷ Global constants1100.00%
▷ Class constants00.00%
▷ Public constants00.00%

Plugin size Passed 2 tests

Image compression Passed 2 tests

All PNG images should be compressed to minimize bandwidth usage for end users
There were not PNG files found in your plugin