Website profiles · Technology insights · Alternatives

tassos.gr

We build advanced Joomla extensions to help your business grow

No paid content found
Visit website
Profile views 18 Outbound visits 6 Normal
Tassos Marinos Full homepage screenshot

At a glance

Category
Design & Creativity
Language
English
Paid-content signal
No paid content foundObserved
Registered
Unknown
Hosting
CloudflareInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is Tassos Marinos?

Tassos Marinos is a Joomla extension developer and web design/development company. Its site presents a suite of commercial Joomla add-ons that extend core Joomla functionality, particularly around forms, popups, structured data, and custom fields. The company says it has offered these products since 2014 and reports over 2.4 million downloads across seven products.

Its main extensions, based on the site’s own descriptions, are:

  • Convert Forms — a contact form builder for contact, payment, registration, and calculator forms.
  • EngageBox — a popup builder for smart popups, sticky bars, fullscreen messages, and floating buttons.
  • Google Structured Data — a schema/structured data tool aimed at rich results and Joomla SEO.
  • Advanced Custom Fields — a collection of custom fields to add information to articles and pages.
  • Smile Pack, Code Snippets, and MailChimp Auto-Subscribe — additional tools listed in the product lineup.

The site also promotes a single bundle plan that gives access to all current extensions plus future ones, and it points to documentation, a blog, services, and programs for translators and nonprofits.

A practical next step: if you run a Joomla site and need one of these specific capabilities, compare the individual extension pages against your actual use case. For example, a membership site that needs registration and payment forms would look at Convert Forms, while a content site focused on search visibility would look at Google Structured Data. If you expect to need more than one tool, the bundle is the more efficient route to evaluate.

Which Tassos Marinos extension should I choose for building a contact form on my Joomla site?

Choose Convert Forms. It is the extension Tassos Marinos positions specifically as its Joomla form builder, and the one built for contact forms, payment forms, registration forms and calculator forms.

Why it fits a contact form project

  • A dedicated form builder rather than a general-purpose add-on, so form creation is the core workflow.
  • The product page lists contact forms first among its use cases, alongside payment, registration and calculator forms.
  • It is one of the developer's flagship products, with a large review base and a high JED ranking shown on the homepage.

When another extension makes more sense

Goal Better fit
Collect form submissions Convert Forms
Turn visitors into subscribers with popups, sticky bars or floating buttons EngageBox
Add rich results and structured data for SEO Google Structured Data
Add extra fields and display more information on articles and pages Advanced Custom Fields

EngageBox and MailChimp Auto-Subscribe can complement a contact form if your goal is list growth rather than enquiries, but neither replaces a form builder.

Next step

Check Convert Forms' own documentation for field types, spam protection and submission handling, then confirm it matches your Joomla version. If you expect to need popups or custom fields later, the developer's bundle gives access to all extensions under one plan, which can be cheaper than buying separately. Compare that against buying only Convert Forms if your needs are narrow.

For background on Joomla itself, see Joomla.

How does the Tassos Marinos bundle plan compare to buying individual Joomla extensions?

The bundle is a single subscription that unlocks every current extension in the Tassos Marinos catalogue plus future releases, whereas buying individually means paying per extension and only receiving updates for the ones you own. For anyone who needs two or more of these tools on the same site, the bundle is usually the simpler and cheaper route; for a site that needs exactly one, a single-extension licence is the more proportionate choice.

What each option actually covers

Bundle plan (one price, full access)

  • All extensions listed on the site: Convert Forms, EngageBox, Google Structured Data, Advanced Custom Fields, Code Snippets, Smile Pack and MailChimp Auto-Subscribe.
  • Any new extension released while your subscription is active.
  • One renewal cycle and one place to manage downloads, rather than separate licence keys per product.

Individual extensions

  • You pay only for the tool you need, e.g. Convert Forms for contact, payment, registration and calculator forms, or EngageBox for popups, sticky bars and floating buttons.
  • Updates and support apply to that product alone.
  • Adding a second or third extension later means a second or third purchase.

How to decide

Your situation Sensible choice
One clear need, e.g. only forms Individual extension
Two or more needs on one site Bundle
Agency or multi-site work with varying requirements Bundle
Wanting new tools as they are released Bundle
Testing one feature before committing Individual extension first

A concrete example

A small business building a Joomla site typically wants a contact form, a newsletter signup popup and structured data for search results. That is three separate products — Convert Forms, EngageBox and Google Structured Data. Bought individually, that is three purchases to track and renew; under the bundle it is one. A blogger who only wants richer search listings can reasonably start with Google Structured Data alone and ignore the rest.

Practical checks before you choose

  • Count how many of the seven products you would genuinely install, not just find appealing.
  • Check whether you run more than one Joomla site, since bundle value scales with site count.
  • Confirm what happens to your sites if you stop renewing — extensions generally keep working but lose updates and support, which matters most for anything handling payments or personal data.
  • Look at the extensions' ratings and JED positions on the site as a rough signal of maturity, but treat marketing rankings as marketing.

Next step: list the extensions you would use in the next twelve months, then compare that list against the current bundle price on Tassos Marinos. If the list has two or more entries, the bundle is the decision to make.

How do I use Google Structured Data to improve my Joomla site's SEO with rich results?

Google Structured Data is a Joomla extension for adding schema markup to your pages so search engines can display rich results — review stars, FAQ accordions, breadcrumbs, product prices and similar enhancements in search listings. Instead of hand-editing JSON-LD into template overrides, you choose a content type, fill in the relevant fields and the extension outputs the structured data for that page.

Tassos Marinos lists it as its SEO-focused product within a suite of Joomla extensions, alongside Convert Forms, EngageBox and Advanced Custom Fields.

A practical workflow

  1. Pick the page type that matches the content. A product page, a how-to article, an FAQ page and a local business homepage each map to different schema types. Marking up a blog post as a Product will not earn you the result you want.
  2. Fill in fields that are actually visible on the page. Review ratings, prices, author names and dates should match what a visitor sees. Mismatches are the most common reason markup gets ignored.
  3. Test before you rely on it. Run a representative URL through Google's Rich Results Test and the Schema Markup Validator. Fix errors, then check Search Console's enhancement reports after Google recrawls.
  4. Apply markup site-wide where it is uniform — organisation details, breadcrumbs, site search — and per-article where it is specific, such as FAQs or reviews.

What it realistically changes

Goal Realistic outcome
Star ratings in search listings Possible, but only if you collect genuine reviews and your page displays them
FAQ or HowTo rich results Eligibility, not a guarantee — Google shows these selectively
Better rankings Structured data is not a direct ranking factor; gains come from higher click-through and clearer entity understanding
Cleaner markup maintenance The main practical win — no template hacks, easier to update when content changes

Who benefits most

Site owners running Joomla who publish reviewable or listable content: product catalogues, service pages, recipe or tutorial sites, event listings, and organisations wanting consistent business information across pages. If your site is a small brochure with no reviewable content, the payoff is limited to breadcrumbs and organisation data.

A sensible first step: choose your three highest-traffic page types, add markup for one of them, and compare click-through rate in Search Console over the following month before rolling it out further. For Joomla users weighing alternatives, the Joomla Extensions Directory is the standard place to compare schema and SEO extensions, and Google's own Search Central documentation defines which rich result types currently exist — check that list before building markup for a type Google has retired.

Can I create popups and sticky bars for my Joomla site without coding using EngageBox?

Yes. EngageBox is presented as a Joomla popup builder aimed at creating popups, sticky bars, fullscreen messages and floating buttons without writing code. The page describes it as the "#1 Joomla Popup Builder Extension," with a 5.0 rating from 576 reviews and a #6 listing on JED, so it is a mature, widely used option rather than a niche add-on.

What you can build without coding

  • Popups — modal or overlay messages for announcements, offers, or subscription prompts.
  • Sticky bars — persistent bars that stay visible as visitors scroll, useful for promotions or cookie-style notices.
  • Fullscreen messages — takeover-style content for major announcements.
  • Floating buttons — always-accessible buttons for contact, chat, or calls to action.

How the no-code workflow typically looks

  1. Install the extension on your Joomla site.
  2. Choose a popup or bar type from the built-in options.
  3. Design the content and appearance using the visual builder.
  4. Set display rules — which pages, devices, or visitor behaviour trigger it.
  5. Publish and adjust based on results.

Practical considerations

  • Overuse is the main risk. Multiple popups and sticky bars on the same page can frustrate visitors and hurt engagement. Start with one goal per page.
  • Mobile behaviour matters. Fullscreen messages and floating buttons can crowd small screens, so test on phones before publishing.
  • Timing and targeting decide success. A popup that fires immediately often performs worse than one triggered by exit intent or scroll depth.

A sensible next step

If you also need forms, the same developer offers Convert Forms, and the site sells a bundle giving access to all extensions plus future ones. For a site that only needs popups, evaluate EngageBox on its own; for a site needing forms, popups and structured data together, the bundle may be more economical. Check the official documentation and demo before committing, and confirm current pricing and licence terms on the site itself.

Related tools from other vendors worth comparing include Joomla for core extension listings and Regular Labs for Joomla add-ons.

How do I set up the MailChimp Auto-Subscribe extension to grow my Joomla email list?

Set up MailChimp Auto-Subscribe by connecting your MailChimp account, mapping the fields you already collect in Joomla to your MailChimp audience, and then choosing where the subscription happens: during registration, at checkout, or inside a form. The goal is to add subscribers without adding a second, disconnected signup step.

A practical setup sequence

  1. Connect the account. In the extension's settings, add your MailChimp API key and select the target audience and any groups or tags you use.
  2. Map the fields. Match Joomla user fields (name, email, and any custom fields) to MailChimp merge fields. Unmapped fields simply won't be sent.
  3. Choose the trigger. Decide whether people are subscribed when they create an account, when they submit a form, or when they explicitly tick a consent box.
  4. Decide double opt-in vs. single opt-in. Double opt-in sends a confirmation email and produces a cleaner, more engaged list; single opt-in grows the list faster but risks more bounces and complaints.
  5. Test with a real address. Register a test account or submit a test form, then confirm the contact appears in MailChimp with the right tags and fields.
  6. Check consent wording. The checkbox label and privacy notice should state clearly what someone is signing up for.

Where it fits in a Joomla stack

Tool Role in list growth
MailChimp Auto-Subscribe Sends Joomla user and form data into MailChimp audiences
Convert Forms Builds the contact, registration or payment forms that feed subscriptions
EngageBox Popups, sticky bars and floating buttons that prompt signups
Advanced Custom Fields Adds the extra profile data you may want to map across

These are the extensions described on Tassos Marinos, where the bundle is positioned as one plan covering all current and future extensions. That matters if you expect to combine forms, popups and subscription logic rather than run one tool alone.

A concrete scenario

A membership site wants new registrants added to a "New Members" audience segment. You map the Joomla email and name fields, set the trigger to account creation, apply a "member" tag, and enable double opt-in. New registrants get a confirmation email; those who confirm land in the tagged segment and can receive a welcome sequence. Visitors who only use a popup signup form go into a separate "Newsletter" segment, so the two groups can be messaged differently.

Decision criteria

  • If you need signups from many different forms and pages, prioritise flexible field mapping over a single built-in signup module.
  • If list quality matters more than list size, enable double opt-in.
  • If you already run Convert Forms and EngageBox, check whether subscription can be triggered from those existing touchpoints before adding another plugin.
  • If you sell access or memberships, confirm how unsubscribes and deleted accounts are handled so your Joomla users and MailChimp contacts stay in sync.

Next step: open the extension's documentation page from the site's Resources menu and follow the version-specific setup steps, since field mapping screens and trigger options differ between releases.

Related questions

More questions →
What Are Form Tools and How Are They Used?

A form tool is software that lets you create, publish, and manage online forms without writing code. You drag fields onto a page, set rules for how the form behaves, and share a link or embed it in a website. When someone submits the form, the tool stores the responses and can route them to an email inbox, a spreadsheet, a database, or another app. That is the whole idea: replace paper forms and ad-hoc email threads with a structured, trackable digital version.

The sections below explain the main types of forms, the features that matter, where form tools get used, and how to pick one.

What a form tool actually does

At minimum, a form tool handles four jobs:

  1. Building — assembling fields (text, email, dropdown, file upload, date, rating, signature) into a layout.
  2. Publishing — generating a shareable link, an embeddable snippet, or a standalone page.
  3. Collecting — receiving submissions and validating them (required fields, correct email format, file size limits).
  4. Handling — storing responses, notifying someone, and passing data onward.

Anything beyond that — payments, e-signatures, workflow automation — is an add-on, not the core function.

The main types of forms people build

Form type Typical purpose Common fields
Contact Let visitors reach a person or team Name, email, message, topic dropdown
Intake / registration Collect details before an appointment, event, or onboarding Full name, contact info, date of birth, preferences, consent checkbox
Survey / feedback Measure opinions or satisfaction Rating scales, multiple choice, open text
Order / request Capture a specific transaction or service request Item selection, quantity, delivery details, notes
Application Evaluate candidates or applicants Background questions, file upload, long-form answers

Most tools handle all five. The differences show up in how much logic, storage, and integration each type demands.

Features worth understanding

Drag-and-drop builder

The standard interface. You pick field types from a sidebar and arrange them visually. No HTML or CSS required, though many tools let you add custom code if you want it.

Conditional logic

This is what separates a basic form from a useful one. Conditional logic shows or hides fields based on earlier answers. Example: if a respondent selects "I have a pet," the form reveals a field for the pet's name. If they select "No," that field never appears. This keeps forms short for most people while still collecting detail from those who need it.

Validation and required fields

Validation prevents bad data. An email field rejects "abc," a number field rejects letters, and a required field blocks submission until it is filled. Good tools validate as the user types, not just on submit.

Submission handling

Where do answers go? Options typically include:

  • Email notification to one or more addresses.
  • Spreadsheet export (CSV, or a live connection to Google Sheets or Excel).
  • Built-in dashboard with search, filtering, and export.
  • Webhook or API to push data into another system.

If you need responses in a CRM, a project board, or a database, check that the tool supports that destination before committing.

File uploads and payments

File upload fields let respondents attach documents or images, usually with a size cap. Payment fields connect to a payment processor so the form can collect a fee at submission. These are common in registration and order forms.

Spam protection

Public forms attract bots. Look for CAPTCHA, honeypot fields (hidden fields bots fill in but humans do not), or rate limiting.

Where form tools get used

  • Healthcare and veterinary clinics — new patient intake, appointment requests, insurance and payment information collection, post-visit feedback.
  • Education — course registration, permission slips, quiz-style assessments, parent contact updates.
  • Events — RSVPs, attendee registration, session sign-ups, dietary preferences.
  • Small business — quote requests, job applications, customer satisfaction surveys.
  • Nonprofits — volunteer sign-ups, donation pledges, grant applications.
  • Internal operations — IT support tickets, expense requests, employee onboarding checklists.

The pattern is consistent: any process that currently runs on paper, PDFs, or "just email me the details" is a candidate for a form tool.

Form tools vs. website builders

These are often confused, so it helps to separate them.

A website builder creates and hosts entire pages — navigation, content, images, blog posts, and forms. A form tool focuses only on the form and its data. Many website builders include a basic form feature, but it is usually limited: few field types, no conditional logic, weak submission management.

A dedicated form tool is the better choice when you need:

  • Complex logic or multi-page forms.
  • Reliable storage and export of responses.
  • Integrations with other software.
  • Forms that live outside your website (shared by link, embedded anywhere).

A website builder's built-in form is fine for a simple contact box on a small site.

How to choose a form tool

Work through these questions in order:

  1. What do you need to collect? List every field and whether it is required. This tells you which field types you cannot live without.
  2. Does it need logic? If answers should change what is asked next, conditional logic is mandatory.
  3. Where must the data end up? Email only, or a spreadsheet, CRM, or database? Confirm the integration exists.
  4. How many responses? Some tools cap submissions or storage on lower tiers. Check the limit against your expected volume.
  5. Who will build and maintain it? A non-technical user needs a clean drag-and-drop interface; a developer may prefer API access and custom code.
  6. What about compliance? If you collect health, financial, or personal data, check how the tool handles encryption, data retention, and regional privacy rules. This is a general consideration, not legal advice — confirm requirements for your situation.
  7. What does it cost at your scale? Pricing usually scales with features, submission volume, or number of users. Compare at the tier you would actually need, not the free plan.

A simple starting workflow

If you are building your first form, this sequence works for almost any use case:

  1. Write down the single purpose of the form in one sentence.
  2. List only the fields needed for that purpose. Cut anything "nice to have."
  3. Group related fields into sections or pages if there are more than about ten.
  4. Add conditional logic to hide irrelevant questions.
  5. Set validation on email, phone, and number fields.
  6. Decide where submissions go and test that destination.
  7. Submit the form yourself, then check the notification, the stored response, and the export.
  8. Share the link or embed it, then review responses after the first week and trim fields that nobody uses.

Bottom line

A form tool turns a question-and-answer process into a structured, trackable digital workflow. The core value is not the form itself but what happens to the data afterward — where it lands, who sees it, and how easily it can be acted on. Choose based on the fields you need, the logic required, and the destination for responses, and you will avoid most of the common mistakes.

Website Overview

Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.

Domain and Registration

Unknown

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. MX records point to the Google Workspace email service. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown. TXT records include verification markers for Google. Such markers may also remain after a service stops being used.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 90 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: HSTS, CSP, Referrer-Policy, Permissions-Policy. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

The public page identifies Joomla, Google Tag Manager, Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

The title has 74 characters and may be truncated in search results. No Open Graph metadata was detected, so social previews may depend on platform inference. JSON-LD includes Organization data, helping describe the organization as an entity. A meta description is present, with 62 characters. No Generator meta tag is publicly exposed.

Hosting and Email

DNSCloudflare
HostingCloudflare
EmailGoogle Workspace
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Location unknown Inferred 104.26.10.203

Registration details

RDAP / WHOIS

Unknown

DNS records

DNS

TypeNameValueTTLPriority
Awww.tassos.gr104.26.10.203300—
Awww.tassos.gr104.26.11.203300—
Awww.tassos.gr172.67.73.81300—
AAAAwww.tassos.gr2606:4700:20::681a:acb300—
AAAAwww.tassos.gr2606:4700:20::681a:bcb300—
AAAAwww.tassos.gr2606:4700:20::ac43:4951300—
MXtassos.graspmx.l.google.com3001
MXtassos.gralt1.aspmx.l.google.com3005
MXtassos.gralt2.aspmx.l.google.com3005
MXtassos.gralt3.aspmx.l.google.com30010
MXtassos.gralt4.aspmx.l.google.com30010
NStassos.grmatt.ns.cloudflare.com86400—
NStassos.grsara.ns.cloudflare.com86400—
TXTtassos.grahrefs-site-verification_38671ad2624687680f12883f7295101207855fa7d02c6fe1a9a5bbacb96563b6300—
TXTtassos.grgoogle-site-verification=cxgVYk234tJqgDxpj3CF3z_M1l_2-rvpMT6SfqzYg9s300—
TXTtassos.grv=spf1 include:_spf.google.com include:mailgun.org include:spf.mtasv.net ~all300—
TXTtassos.gryahoo-verification-key=OZxoUzOI5fv7h30sbuzkjg0Zjjzlp5a9fBTe7pq6IqE=300—
DMARC_dmarc.tassos.grv=DMARC1; p=none; pct=100; fo=1; ri=3600; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected],mailto:[email protected];300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjecttassos.gr
IssuerGoogle Trust Services
Valid until2026-11-23T12:40 · Remaining when checked: 52 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlno-store, no-cache, must-revalidate, post-check=0, pre-check=0
servercloudflare
x-frame-optionsSAMEORIGIN
x-content-type-optionsnosniff
set-cookieRedacted

Identified technologies

JoomlaGoogle Tag ManagerCloudflare

Pages, Search and Sharing

Meta descriptionWe build advanced Joomla extensions to help your business grow
Canonical URLhttps://www.tassos.gr
LanguageEnglish (default)
Twitter CardNot detected

Unknown

All bots 0 allowed · 16 disallowed
  • Disallow/administrator/
  • Disallow/bin/
  • Disallow/cache/
  • Disallow/cli/
  • Disallow/components/
  • Disallow/includes/
  • Disallow/installation/
  • Disallow/language/
  • Disallow/layouts/
  • Disallow/libraries/
  • Disallow/logs/
  • Disallow/modules/
  • Disallow/plugins/
  • Disallow/tmp/
  • Disallow/xmlstreams
  • Disallow/*.zip$
  • IntervalCrawl delay 10 seconds

User reviews (0)

  • No reviews yet.