Skip to main content
Zetun Web

The Zetun Standard

Included in every service scope.

The shared foundation for Presence, Voice, and Partner.

Every published Zetun Web presence includes the same high-quality foundation. The Zetun Standard combines visible quality, technical care, and a clear frame for operation and ongoing care.

Presence, Voice, and Partner differ in how much responsibility Zetun Web takes on. The shared technical and visual quality remains part of The Zetun Standard in every service scope.

Quality frame in the launch check

Performance

97+

Accessibility in Lighthouse

100/100

SEO

100/100

Best Practices

100/100

These values are Lighthouse target values in the launch check. The 97+ for performance marks the quality frame; technically, Zetun Web will inshallah aim for 100/100 there as well when content, media scope, external embeds, and special requirements allow it.

Shared foundation

What every published presence includes

The Zetun Standard bundles the shared foundation of every published production presence in Presence, Voice, and Partner.

  • Dedicated codebase & custom build

    Every presence is built individually with its own codebase, clear page logic, and a structured technical foundation.

  • Performance & delivery

    Static output, responsive image variants, targeted loading priority, compact production files, local fonts, optimized SVGs, prepared compression, and cache rules are shaped for short loading times and robust delivery.

  • Visual material & starter visual areas

    Existing practice images receive technical preparation. Suitable open image areas receive symbolic, illustrative, or abstract visual material so the presence can be reviewed concretely from the start.

  • SEO foundations & previews

    Page titles, descriptions, canonicals, sitemap, Open Graph, dedicated preview graphics, and structured data give every page clear technical signals.

  • Usability & accessibility review

    Semantic structure, skip link to content, keyboard operation, visible focus handling, reduced motion, meaningful image descriptions, and browser-supported checks for pages and relevant interaction states belong to the foundation.

  • Quality assurance & launch check

    Lighthouse targets, responsive review, metadata, links, central user paths, and browser-supported checks form concrete review points in the launch check.

  • Privacy-conscious foundation

    Local fonts, own static resources, and deliberately chosen embeds strengthen control and technical explainability.

  • Hosting, security & care

    HTTPS, automatic certificate renewal, security headers, hosting, maintenance, monitoring, and defect resolution belong to the agreed operation frame.

  • Legal page templates

    Zetun Web prepares legal notice, privacy policy, and, where intended, an accessibility page with suitable templates and project-specific technical details. Legal review and final approval remain with the practice or an appointed legal advisor.

  • Content, responsibility & handover

    The practice remains the publisher of its content. The published production state and content stay clearly attributable for an orderly handover.

Details

The Zetun Standard in detail

Concrete parts, organized by area.

  1. 01

    Visual material for open areas

    The visual starting state receives suitable image areas so design, structure, and visual effect can be reviewed early.

    Own practice images can be integrated when they fit the presence and rights and approvals are clarified.

    For suitable open image areas, Zetun Web creates symbolic, illustrative, or abstract visual material. This creates a visual frame that fits the design and can be reviewed concretely.

    Practice rooms, team photos, or professional motifs with real relevance come from practice images or correctly licensed material. That strengthens trust, orientation, and a clear basis for publication.

    • Visual starting state
    • Symbolic and illustrative image worlds
    • Practice photos when rights are clarified
    • Subsequent technical image preparation
  2. 02

    One motif becomes a delivery set

    One motif is turned into suitable files for different devices, screen sizes, and browsers.

    Zetun Web creates several image sizes and provides modern formats: AVIF for very efficient delivery with high visual quality; WebP complements delivery with broad browser coverage.

    Image dimensions, aspect ratio, and responsive variants are prepared. A smartphone receives a suitable smaller file, while large screens can use a larger display.

    The browser chooses the file according to device, screen size, pixel density, and format support.

    This technical image process applies to selected visual material: existing practice images, correctly licensed motifs, and suitable starter visuals.

    • Several sizes per motif
    • AVIF and WebP
    • Image dimensions and display prepared
    • Prepared for phone, tablet, and desktop
  3. 03

    Professional link impression

    Shared links will inshallah carry the professional impression of the practice further.

    For the homepage, service page, or article, Zetun Web sets title, description, and preview image to match the respective page.

    This keeps content clear outside the website: in messenger links, social previews, and other shared surfaces.

    The basis is a dedicated codebase, structured page data, and a systematic production process. From the available page data, each published page receives its own preview graphic with suitable naming, page title, and description.

    Local fonts and brand elements visibly connect the preview with the practice presence.

    • Dedicated preview per published page
    • Title and description per page
    • Suitable image for shared links
    • Recognizable link impression
  4. 04

    Static delivery, cache & HTTPS

    The presence is prepared for efficient delivery because finished files are already available.

    Static HTML output, prepared images, fonts, CSS, scripts, and SVGs form the technical foundation for fast and robust delivery.

    Versioned build files use targeted cache rules. Page content and non-versioned files remain separate and can be updated deliberately.

    HTTPS delivery with automatic certificate renewal belongs to the agreed operation frame.

    • Static HTML output
    • Cache rules for assets
    • Updatable HTML pages
    • HTTPS with automatic certificate renewal

Further parts by area

Further details are grouped by topic and can be opened when needed.

Visible start & visual effect Loading priority, local fonts, and optimized SVGs.
  1. 05

    Targeted loading priority

    Important content appears early and shapes the first impression.

    The first visible area receives special attention. Hero images load early and with high priority; images lower down follow according to the page structure.

    Important font files receive early priority. Further resources stay aligned with their actual use.

    JavaScript has clear tasks for real interaction. Additional browser code loads where a function needs it, while static content is available directly.

    • Hero images prioritized early
    • Lower images loaded appropriately
    • Important fonts preloaded
    • JavaScript loaded deliberately
  2. 06

    Local fonts and suitable fallbacks

    Typography remains controlled inside the website.

    Font files live locally in the website structure. The browser loads typography directly from the presence.

    A locally embedded and metrically matched fallback font supports early text rendering and keeps the display closer to the final typography while the primary font loads.

    • Local font files
    • Directly from the website structure
    • Metrically matched fallback
    • Controlled typography
  3. 07

    Optimized SVGs

    Icons and graphic details support orientation, operation, and the premium impression.

    Zetun Web uses clear, consistent interface icons where they support navigation, orientation, or operation.

    SVGs, icons, and graphic elements receive technical optimization before they are integrated into the finished presence.

    The optimization reduces file size and preserves the technical structure relevant for rendering and reuse.

    Small graphic details stay precise, cacheable, and efficient to deliver.

    • Consistent icons for suitable interface elements
    • Technically optimized SVGs
    • Icons and graphics prepared
    • Cacheable assets
SEO, structure & page signals Metadata, sitemap, and structured data give every page clear technical signals.
  1. 08

    SEO foundations per page

    Findability starts with clear page signals.

    Every published page receives a title, description, canonical, and technical metadata that match the respective content.

    The sitemap brings together public URLs, available language versions, and change information. robots.txt adds technical orientation for search engines.

    SEO foundations create a reliable technical basis. Visibility also depends on content, demand, competition, location, trust, and ongoing signals.

    • Title and description per page
    • Canonical and language signals
    • Sitemap and robots.txt
    • Technical orientation for search engines
  2. 09

    Structured data

    Important content receives machine-readable classification.

    Structured data describes the role a page fulfils: website, organization, navigation path, article, FAQ, practitioner profile, or service page.

    The information comes from the same structured page data as content, metadata, and preview graphics. Visible page and technical classification remain closely connected.

    JSON-LD provides this classification in a format that search engines and other technical systems can evaluate.

    • Website and organization data
    • Breadcrumbs for detail pages
    • Articles, FAQs, practitioner profiles, and services
    • JSON-LD from structured page data
Delivery & production files Compact files, prepared compression, and efficient delivery.
  1. 10

    Compact production files

    The finished presence remains efficient to deliver because production files are prepared deliberately.

    HTML, CSS, and JavaScript receive a compact production output before publication.

    CSS follows the design actually used. Scripts stay focused on real interaction and the respective page areas.

    Design, interaction, and technical preparation work together efficiently before the files are made available.

    • HTML, CSS, and JavaScript prepared compactly
    • CSS matching the used design
    • Scripts for real interaction
    • Prepared for efficient delivery
  2. 11

    Pre-compressed files

    Files are already available in suitable compression variants so delivery can work efficiently from the first request.

    HTML, CSS, JavaScript, SVGs, and other suitable public files are available in several common compression formats.

    During delivery, the fitting variant is available: modern browsers receive especially efficient compression; proven formats support broad compatibility.

    Compression exists before the page request. Delivery can therefore access prepared files directly.

    • Brotli, gzip, and zstd prepared
    • Compression before page request
    • Suitable variant per browser
    • Efficient delivery of static files
Usability & quality assurance Accessibility review, keyboard operation, focus handling, and guided error paths.
  1. 12

    Browser-supported accessibility review

    Usability and accessibility review belong to the technical quality of a published presence.

    Zetun Web builds pages with semantic structure, clear heading order, skip link to content, keyboard operation, visible focus handling, and reduced motion.

    Own axe-core-supported checks provide technical findings in the built state of the website. The presence runs as a browser preview; pages, viewports, and relevant interaction states receive targeted review.

    Zetun Web reviews initial page states, opened interactions, keyboard activation with Enter and Space, Escape behavior, focus return, tab order, internal links, and same-page anchors.

    The findings serve as a correction basis in the launch check. Technical points found receive targeted review and correction in the project.

    Image descriptions and alt texts are created deliberately in the content and quality process. Their review depends on image purpose, page context, and understandability.

    • Browser-supported checks
    • Review of several viewports and interaction states
    • Keyboard operation, skip link, and focus handling
    • Links, anchors, and meaningful image descriptions
  2. 13

    Dedicated 404 error page

    Outdated or mistyped URLs remain part of a guided presence.

    When an address is not found, a designed error page appears in the style of the website.

    Clear paths guide visitors onward to the homepage, services, contact, or other central areas.

    The page remains brand-consistent, quickly reachable, and technically classified as an error page.

    • Designed 404 page
    • Clear paths into the website
    • Matching the presence
    • Technically correct error status

Care

Operation & Care

The Zetun Standard also includes the post-launch frame: hosting, monitoring, maintenance, technical care, defect resolution, and adjustment allowance belong to the agreed operation frame.

  • Hosting & technical operation

    During active care, the presence runs on Zetun Web infrastructure. Delivery, server environment, and technical baseline care come from one side.

  • Monitoring & maintenance

    Monitoring, operational checks, security updates, and maintenance of technical dependencies keep the technical state in view.

  • Defect resolution

    If an agreed part of the presence does not work as built, correction during active care belongs to the agreed operation frame.

  • Adjustment allowance

    We will inshallah classify new wishes clearly. Depending on the service scope, yearly adjustments are included; larger changes receive a concrete scope in advance.

Next

From standard to the right scope

The Zetun Standard is the shared foundation. The next pages classify scope and technical implementation.

The right scope starts with your practice.

The first step is about goals, existing content, useful contact paths, and the responsibility Zetun Web should take on for your presence.