10% tapz-in

Code Review | Tapz

WordPress plugin Tapz scored10%from 54 tests.

About plugin

  • Plugin page: tapz-in
  • Plugin version: 1.0
  • PHP version: 7.4.16
  • WordPress compatibility: 3.0-5.9.3
  • WordPress version: 6.3.1
  • First release: Dec 11, 2019
  • Latest release: May 7, 2022
  • Number of updates: 7
  • Update frequency: every 125.4 days
  • Top authors: dhirajtapz (100%)

Code review

54 tests

User reviews

1 review

Install metrics

10+ active /480 total downloads

Benchmarks

Plugin footprint 40% from 16 tests

Installer 0% from 1 test

🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The following installer errors require your attention
  • Install procedure validation failed for this plugin
    • > Deprecated in wp-content/plugins/tapz-in/tapz.php+40
    Methods with the same name as their class will not be constructors in a future version of PHP; tapzWidget has a deprecated constructor

Server metrics [RAM: ▼1.92MB] [CPU: ▼57.57ms] Passed 4 tests

A check of server-side resources used by Tapz
This plugin does not affect your website's performance
PageMemory (MB)CPU Time (ms)
Home /2.08 ▼1.394.58 ▼38.53
Dashboard /wp-admin2.10 ▼1.257.53 ▼54.49
Posts /wp-admin/edit.php2.10 ▼1.266.31 ▼40.45
Add New Post /wp-admin/post-new.php2.10 ▼3.795.90 ▼96.81
Media Library /wp-admin/upload.php2.10 ▼1.134.89 ▼28.55

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

Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 3 new files
Database: no new tables, 8 new options
New WordPress options
widget_tapzwidget
tapz
can_compress_scripts
widget_recent-comments
theysaidso_admin_options
db_upgraded
widget_theysaidso_widget
widget_recent-posts

Browser metrics Passed 4 tests

This is an overview of browser requirements for Tapz
This plugin renders optimally with no browser resource issues detected
PageNodesMemory (MB)Script (ms)Layout (ms)
Home /2,819 ▲4813.20 ▼1.242.78 ▲0.5543.60 ▲0.38
Dashboard /wp-admin2,225 ▲335.88 ▲0.98103.40 ▼12.2340.29 ▼13.52
Posts /wp-admin/edit.php2,102 ▲132.06 ▲0.0334.20 ▼1.1234.69 ▼3.62
Add New Post /wp-admin/post-new.php1,553 ▲2523.11 ▲4.82657.61 ▲44.0650.59 ▲0.07
Media Library /wp-admin/upload.php1,404 ▲164.19 ▼0.0096.44 ▼1.5643.03 ▼1.51

Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests

🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
  • The plugin did not uninstall gracefully
    • > Deprecated in wp-content/plugins/tapz-in/tapz.php+40
    Methods with the same name as their class will not be constructors in a future version of PHP; tapzWidget has a deprecated constructor
  • Zombie WordPress options were found after uninstall: 8 options
    • widget_recent-posts
    • db_upgraded
    • widget_theysaidso_widget
    • can_compress_scripts
    • widget_tapzwidget
    • theysaidso_admin_options
    • tapz
    • widget_recent-comments

Smoke tests 50% from 4 tests

Server-side errors Passed 1 test

🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test

SRP 0% from 2 tests

🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Almost there! Just fix the following items
  • 1× PHP files perform the task of outputting text when accessed with GET requests:
    • > /wp-content/plugins/tapz-in/tapz.php
  • 1× PHP files trigger errors when accessed directly with GET requests:
    • > PHP Fatal error
      Uncaught Error: Using $this when not in object context in wp-content/plugins/tapz-in/tapz_form.php:105

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, but this is not an exhaustive test

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
Attributes that require attention:
  • Tags: Please delete some tags, you are using 41 tag instead of maximum 10
You can take inspiration from this readme.txt

tapz-in/tapz.php 85% from 13 tests

The primary PHP file in "Tapz" version 1.0 is used by WordPress to initiate all plugin functionality
The following require your attention:
  • Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("tapz-in.php" instead of "tapz.php")
  • Description: Please don't use more than 140 characters for the plugin description (currently 186 characters long)

Code Analysis Passed 3 tests

File types Passed 1 test

🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected224 lines of code in 2 files:
LanguageFilesBlank linesComment linesLines of code
PHP23174224

PHP code Passed 2 tests

A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
Cyclomatic complexity
Average complexity per logical line of code0.16
Average class complexity2.50
▷ Minimum class complexity1.00
▷ Maximum class complexity4.00
Average method complexity1.23
▷ Minimum method complexity1.00
▷ Maximum method complexity3.00
Code structure
Namespaces0
Interfaces0
Traits0
Classes2
▷ Abstract classes00.00%
▷ Concrete classes2100.00%
▷ Final classes00.00%
Methods13
▷ Static methods00.00%
▷ Public methods1184.62%
▷ Protected methods00.00%
▷ Private methods215.38%
Functions1
▷ Named functions1100.00%
▷ Anonymous functions00.00%
Constants0
▷ Global constants00.00%
▷ Class constants00.00%
▷ Public constants00.00%

Plugin size Passed 2 tests

Image compression Passed 2 tests

PNG files should be compressed to save space and minimize bandwidth usage
There were not PNG files found in your plugin