Online Invitation Knowledge
Practical online invitation knowledge guides from ThiepOnline covering WebP image compression, Zalo and Facebook Open Graph link previews, custom domains and favicons, mobile typography readability, guest RSVP spreadsheet management, and clear bilingual Vietnamese-English invitation etiquette for Vietnam event hosts.
Plenty of online invitations look sharp on a designer's laptop, then break down the moment guests tap the link inside Zalo or Messenger. An 18MB batch of raw wedding photos stalls over 4G, the chat link preview crops off half the couple's faces, thin script fonts turn unreadable on a 360px phone screen, and RSVP entries arrive without indicating which side of the family a guest belongs to. These launch-day issues rarely stem from taste; they come from skipping core technical checks before publishing.
The online invitation knowledge guides at ThiepOnline serve as a practical technical playbook for event hosts and coordinators. Every guide walks through concrete specs and repeatable fixes across image compression, Zalo and Facebook Open Graph previews, custom domains and favicons, mobile typography readability, structured RSVP list management, and clear bilingual Vietnamese-English invitation etiquette.
1. Image Compression and Mobile Load Speed Optimization
More than 85% of invitation recipients open links directly inside messaging apps on mobile data while commuting or taking a quick break. Uploading unedited studio exports (often 4MB to 12MB per file) pushes total page weight past 40MB, causing Zalo's and Facebook's in-app browsers to lag, freeze, or crash on mid-range smartphones.
The dependable workflow is to resize every photo to its actual display dimensions before uploading, convert assets to WebP (or progressive JPEG at 78%–82% quality), and strip bulky camera EXIF metadata. Always lock explicit aspect ratios on image containers so the page never jumps vertically (Cumulative Layout Shift) while a guest is reading ceremony hours or tapping the map button.
| Invitation Asset Slot | Recommended Resolution (px) | Preferred Format | Target File Weight | Common Mistake to Avoid |
|---|---|---|---|---|
| Opening Hero Image | 1200 × 1600 (vertical) or 1600 × 1067 (horizontal) | WebP (80% quality) | Under 150 KB | Uploading 6000px camera originals that leave a blank screen for 5 seconds |
| Photo Gallery (8–12 Images) | Max width 1080 – 1200 px | WebP or Progressive JPEG | 70 – 110 KB each | Embedding 25+ uncompressed photos without lazy loading |
| Open Graph Preview (Zalo/FB) | 1200 × 630 px (1.91:1 ratio) | JPEG or PNG | Under 300 KB | Placing faces or text near outer edges where Zalo crops to square |
| VietQR Code / Brand Logo | 600 × 600 px (clean white margin) | PNG or SVG (logos) | Under 60 KB | Over-compressing JPEG QR codes until banking scanners fail to read |
2. Configuring Open Graph (OG) Previews for Zalo and Facebook
A guest's first impression happens inside the chat bubble before the invitation page even loads. When a shared URL shows a blank placeholder box, a truncated headline, or default template copy, click-through rates drop and cautious recipients may mistake the link for spam.
- Design Around the Center Safe Zone: Export your Open Graph image at the standard
1200 × 630 pxcanvas, but keep faces, logos, and headline text inside the central630 × 630 pxsquare. Facebook renders the full 1.91:1 horizontal frame, whereas several Zalo mobile layouts center-crop previews into a compact square card. - Tighten Title and Description Lengths: Keep
og:titlebetween 45 and 65 characters (for example: "Minh Anh & Quoc Bao Wedding – Oct 24, 2026") andog:descriptionbetween 110 and 140 characters stating the date, city, and venue so guests absorb key details at a glance. - Clear Social Scraper Caches After Edits: If you update your cover photo or title after sending a test link, social platforms often keep serving the old cached card. For Facebook and Messenger, paste the URL into the Facebook Sharing Debugger and click "Scrape Again." For Zalo, upload the updated OG image under a fresh filename or append a short version query parameter (such as
?v=2) for your next outreach batch.
3. Custom Domains, Clean Slugs, and Favicon Setup
A readable address like minhanh-quocbao.vn or thieponline.net.vn/minh-anh-quoc-bao builds immediate trust in chat messages and prints neatly on physical keepsake cards or welcome standees. For corporate launches and conferences, attaching a company subdomain such as yep2026.company.vn or launch.brand.com signals authenticity to partners, clients, and press invitees.
When connecting a custom domain to ThiepOnline, verify three technical items at least 48 hours before your main send date:
- DNS Records and Propagation: Point the exact
CNAMErecord (for subdomains) orArecord (for root domains) at your registrar, and keep TTL at 300–600 seconds during setup so changes propagate quickly without lingering stale records. - Active SSL/HTTPS Certificate: Verify the padlock icon loads cleanly on Chrome, Safari, and Zalo's embedded browser. An unprovisioned SSL certificate triggers full-screen security warnings that cause most guests to close the page immediately.
- Favicon and Apple Touch Icon: Upload a crisp
32 × 32 pxfavicon for browser tabs and a180 × 180 pxApple Touch Icon for guests who bookmark the invitation to their iPhone home screen. Choose a simple monogram or high-contrast emblem rather than a detailed photo that blurs at tiny sizes.
4. Mobile Typography and Readability Standards
The fastest way to frustrate guests on a phone is setting body paragraphs in delicate calligraphic script or shrinking text to 12px to cram extra lines onto one screen. Remember that your audience often includes relatives over 55 checking directions outdoors in bright sunlight or inside a moving taxi.
- Enforce Clear Size Hierarchy: Set body copy to at least
15px–16pxon mobile with a comfortable line-height of1.5to1.65. Reserve decorative script fonts strictly for couple names or large section titles (28pxand up); render all dates, start times, street addresses, and phone numbers in clean Sans-serif or legible Serif typefaces. - Verify Full Vietnamese Diacritic Support: Many free display fonts lack complete Vietnamese glyph coverage, causing accented characters like ư, ơ, ệ, ộ, ũ to fall back to a mismatched system font mid-word. Always test a sample sentence containing all six Vietnamese tones and uppercase accented letters before locking your font pairing.
- Maintain Accessible Color Contrast: Avoid pale gold, pastel pink, or thin gray text over white backgrounds or bright wedding photos. Aim for at least a 4.5:1 contrast ratio; when placing white text over hero photography, apply a subtle dark gradient overlay (35%–50% opacity) behind the text block.
- Size Tap Targets for Thumbs: Every interactive button—Google Maps directions, RSVP submit, calendar save, and audio toggle—should measure at least
44pxtall with at least12pxof spacing between adjacent controls so guests never mis-tap on compact screens.
5. Structured Guest List and RSVP Data Management
Collecting RSVPs is only half the operational win; the real payoff comes when your exported spreadsheet translates cleanly into banquet tables, dietary counts, and reception check-in lists. Without upfront structure, responses turn into a tangle of informal nicknames ("Uncle Hung", "Lan from accounting") that slow down front-desk staff on event day.
Keep your guest dataset clean and actionable by following four practical habits:
- Tag Guest Groups Inside the Form: Include a required group selector or standardized tag convention (such as
Groom-Family,Bride-College,Company-Sales,VIP-Partner). Filtering your export by group gives you instant table counts for each family side or department. - Separate Adult Headcount from Children: At weddings and family milestones, knowing whether a "+2" means two adults or one adult and a toddler affects both catering portions and high-chair requests. Provide a clear adult count selector alongside an optional child-seat or dietary note box.
- Deduplicate Updated Submissions: Guests frequently submit the RSVP form a second time when their plans change from "Attending" to "Regrets" or when a partner joins late. Before locking numbers with the venue, sort your spreadsheet by newest Timestamp and retain only the latest entry per phone number or full name.
- Protect Guest Contact Privacy: Never expose guest phone numbers or email addresses inside a public guestbook widget. Display only names and congratulatory messages on the live invitation while keeping contact fields restricted to your private admin dashboard.
6. Bilingual Vietnamese–English (VI/EN) Invitation Etiquette
For intercultural weddings, overseas family networks, and international corporate gatherings in Vietnam, a well-crafted bilingual invitation makes every guest feel welcomed while clarifying local traditions. Literal word-for-word translation rarely reads naturally and often introduces avoidable date or schedule confusion.
- Eliminate Numeric Date Ambiguity: Writing
04/05/2026reads as May 4 to Vietnamese and European guests, but April 5 to American guests. On the English version, always spell out the month name (May 4, 2026or4 May 2026); on the Vietnamese version, write04 tháng 05, 2026clearly. - Contextualize Traditional Vietnamese Ceremonies: International guests may not know what distinguishes Lễ Vu Quy from Lễ Thành Hôn or why a lunar date appears alongside the Gregorian date. Pair traditional titles with concise English explanations such as "Lễ Vu Quy (Bride's Ancestral Tea Ceremony)" and "Main Wedding Reception", explicitly noting which sessions all guests are invited to attend.
- Pick the Right Language Layout: For multi-section invitations featuring a love story, detailed timeline, and travel tips, place a sticky VI / EN language switcher at the top corner so the page stays compact instead of doubling in scroll length. Use side-by-side bilingual blocks only on short one- or two-screen announcements such as reception-only cards or quick store openings.
- Include Time Zone and Ride-Hailing Friendly Addresses: Add
GMT+7 (Vietnam Time)for remote livestream links or airport transfer notes, and provide an unaccented address line alongside the Vietnamese street address so overseas visitors can copy-paste smoothly into Grab or Google Maps.
7. Mandatory Technical QA Checklist Before Mass Distribution
Before broadcasting your invitation link to hundreds of guests, run through the verification matrix below across real devices and chat apps so every module holds up under live traffic.
| QA Category | Test Device / Tool | Pass Criteria | Fix if Failed |
|---|---|---|---|
| Load Speed & Image Weight | Smartphone on 4G (incognito tab) | Hero renders under 2 seconds; smooth scroll without stutter | Re-export images to WebP under 150 KB; enable gallery lazy-load |
| Open Graph Link Preview | Zalo private chat & Facebook Debugger | Crisp 1200×630 thumbnail, faces centered, complete title | Recenter subject in 630×630 safe zone; refresh cache with ?v=2 |
| Custom Domain, SSL & Favicon | Chrome, iOS Safari, Zalo in-app browser | Valid HTTPS padlock, zero security warnings, visible tab icon | Verify CNAME/A records and wait for SSL provisioning to finish |
| Typography & Tap Targets | 360px – 390px phone viewport | Body text ≥ 15px, clean VI diacritics, buttons ≥ 44px high | Switch to full Vietnamese-safe font; raise text-background contrast |
| RSVP Flow & Map Pin | Live test submission & Maps tap | Entry saves under correct group; pin lands at venue entrance | Adjust required fields and update exact venue coordinates |
| Bilingual VI/EN Parity | Side-by-side section audit | Spelled-out English months, matching times, no untranslated labels | Standardize date formats and verify toggle switches every block |
6-Minute Pre-Launch Smoke Test Sequence
- Minute 1: Open the live URL on both an iPhone and an Android phone over 4G cellular data to verify initial hero load speed and scroll responsiveness.
- Minute 2: Paste the URL into a private Zalo chat and a Messenger thread to inspect the Open Graph image crop, title, and description snippet.
- Minute 3: Tap every interactive control in order: Google Maps directions, calendar save, background audio toggle, and the VI/EN language switcher.
- Minute 4: Submit one realistic RSVP entry containing Vietnamese diacritics and a dietary note, then confirm the record appears cleanly in your dashboard export.
- Minute 5: Scan any embedded VietQR code with a live banking app to confirm the beneficiary name and bank match your records exactly.
- Minute 6: Proofread all hotline phone numbers, parent names, hall numbers, and weekday-to-date alignment one final time before sending your first wave.
