Custom HTML Elements for Widget Embedding

You embed a third-party widget on your site and an hour later find that buttons have turned red and scripts conflict with jQuery. Sound familiar? We offer a solution: custom HTML elements with Shadow DOM permanently eliminate this headache. The client inserts three lines of code and gets a working widget, isolated from the host site's environment. A third-party widget on someone else's site means someone else's DOM, someone else's styles, potentially conflicting library versions. Custom Elements v1 solve this problem radically: no CSS conflicts, no broken scripts. The load time for such a widget is 0.5–1.5s (LCP), whereas an iframe alternative takes 2–3s. This is a web component implementation that provides seamless integration and complete isolation.

How Custom HTML Elements Solve Website Conflicts

• Style conflicts: The widget's internal styles may accidentally override the site's styles (e.g., button { background: red }). Shadow DOM guarantees isolation in both directions.
• Version management: The widget is connected via a single script with an SRI hash. The client will not accidentally update the widget — only by intentionally changing the version in the URL.
• Cross-browser support: Shadow DOM works in all modern browsers. For IE11 we include a polyfill. We test on real devices.
• SEO: Unlike iframes, content in Custom Elements is indexed by search engines. This is critical for review, rating, and catalog widgets.

What Shadow DOM Isolation Provides

Shadow DOM is the only reliable solution. We create a <template> with encapsulated styles and structure. Here is a minimal example:

<review-widget
  data-product-id="SKU-12345"
  data-theme="light"
  data-locale="en"
></review-widget>

The element loads data via API and renders reviews. Styles are isolated — no * { all: unset } from the host page can break the widget.

Why Custom Elements Are Better Than iframes for Widgets

Custom Elements are 2–3 times faster than iframes in load time and do not hide content from search engines. Traffic savings up to 70% (up to $2,000 per month).

How the Widget Works Internally

The architecture includes three layers: Custom Element (registers the tag, manages lifecycle), Shadow DOM (isolated styles and markup), and API client (loads data with pagination). Below is the full code for ReviewWidget:

// src/ReviewWidget.ts
const TEMPLATE = document.createElement('template');
TEMPLATE.innerHTML = `
  <style>
    :host {
      display: block;
      contain: content;
      font-family: var(--rw-font, -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif);
      font-size: var(--rw-font-size, 14px);
      color: var(--rw-text-color, #1a1a2e);
    }
    :host([hidden]) { display: none; }
    .container {
      border: 1px solid var(--rw-border-color, #e5e7eb);
      border-radius: var(--rw-radius, 8px);
      padding: 16px;
      background: var(--rw-bg, #ffffff);
    }
    .rating {
      display: flex;
      align-items: center;
      gap: 4px;
      margin-bottom: 12px;
    }
    .star { color: #f59e0b; font-size: 18px; }
    .star.empty { color: #d1d5db; }
    .reviews-list { list-style: none; margin: 0; padding: 0; }
    .review-item {
      padding: 10px 0;
      border-top: 1px solid #f3f4f6;
    }
    .review-author { font-weight: 600; font-size: 13px; }
    .review-text { margin-top: 4px; line-height: 1.5; }
    .load-more {
      margin-top: 12px;
      width: 100%;
      padding: 8px;
      background: var(--rw-accent, #3b82f6);
      color: #fff;
      border: none;
      border-radius: 6px;
      cursor: pointer;
      font-size: 13px;
    }
    .load-more:hover { opacity: .9; }
    .skeleton {
      background: linear-gradient(90deg, #f0f0f0 25%, #e0e0e0 50%, #f0f0f0 75%);
      background-size: 200% 100%;
      animation: shimmer 1.5s infinite;
      border-radius: 4px;
      height: 14px;
      margin: 6px 0;
    }
    @keyframes shimmer {
      0% { background-position: 200% 0; }
      100% { background-position: -200% 0; }
    }
  </style>
  <div class="container">
    <div class="rating" aria-label="Product rating"></div>
    <ul class="reviews-list" role="list"></ul>
    <button class="load-more" style="display:none">Show more</button>
  </div>
`;

interface Review {
  id: string;
  author: string;
  rating: number;
  text: string;
  date: string;
}

export class ReviewWidget extends HTMLElement {
  static get observedAttributes() {
    return ['data-product-id', 'data-theme', 'data-locale'];
  }

  private shadow: ShadowRoot;
  private page = 1;
  private allLoaded = false;
  private apiBase = '/api/reviews';

  constructor() {
    super();
    this.shadow = this.attachShadow({ mode: 'open' });
    this.shadow.appendChild(TEMPLATE.content.cloneNode(true));
  }

  connectedCallback() {
    this.applyTheme();
    this.fetchReviews(true);

    this.shadow.querySelector('.load-more')
      ?.addEventListener('click', () => this.fetchReviews(false));
  }

  attributeChangedCallback(name: string, old: string, next: string) {
    if (old === next) return;
    if (name === 'data-product-id') {
      this.page = 1;
      this.allLoaded = false;
      this.fetchReviews(true);
    }
    if (name === 'data-theme') {
      this.applyTheme();
    }
  }

  private applyTheme() {
    const theme = this.dataset.theme ?? 'light';
    if (theme === 'dark') {
      const container = this.shadow.querySelector<HTMLElement>('.container');
      if (container) {
        container.style.setProperty('--rw-bg', '#1f2937');
        container.style.setProperty('--rw-text-color', '#f9fafb');
        container.style.setProperty('--rw-border-color', '#374151');
      }
    }
  }

  private showSkeleton() {
    const list = this.shadow.querySelector('.reviews-list')!;
    list.innerHTML = Array(3).fill(
      '<li><div class="skeleton"></div><div class="skeleton" style="width:70%"></div></li>'
    ).join('');
  }

  private async fetchReviews(reset: boolean) {
    const productId = this.dataset.productId;
    if (!productId) return;

    if (reset) {
      this.page = 1;
      this.showSkeleton();
    }

    try {
      const url = new URL(`${this.apiBase}/${productId}`, window.location.origin);
      url.searchParams.set('page', String(this.page));
      url.searchParams.set('per_page', '5');
      url.searchParams.set('locale', this.dataset.locale ?? 'en');

      const res = await fetch(url.toString(), {
        headers: { 'X-Widget-Version': '2.1.0' },
      });

      if (!res.ok) throw new Error(`HTTP ${res.status}`);

      const data: { reviews: Review[]; total: number; avg_rating: number } =
        await res.json();

      this.renderRating(data.avg_rating, data.total);
      this.renderReviews(data.reviews, reset);

      this.allLoaded = data.reviews.length < 5;
      const btn = this.shadow.querySelector<HTMLElement>('.load-more');
      if (btn) btn.style.display = this.allLoaded ? 'none' : 'block';

      this.page++;

      // inform the host page
      this.dispatchEvent(new CustomEvent('reviews:loaded', {
        detail: { total: data.total, avgRating: data.avg_rating },
        bubbles: true,
        composed: true,
      }));
    } catch (err) {
      this.renderError();
    }
  }

  private renderRating(avg: number, total: number) {
    const ratingEl = this.shadow.querySelector('.rating')!;
    const stars = Array.from({ length: 5 }, (_, i) =>
      `<span class="star ${i < Math.round(avg) ? '' : 'empty'}">★</span>`
    ).join('');
    ratingEl.innerHTML = `${stars} <span>${avg.toFixed(1)} (${total} reviews)</span>`;
    ratingEl.setAttribute('aria-label', `Rating ${avg.toFixed(1)} out of 5, ${total} reviews`);
  }

  private renderReviews(reviews: Review[], reset: boolean) {
    const list = this.shadow.querySelector('.reviews-list')!;
    if (reset) list.innerHTML = '';

    const locale = this.dataset.locale ?? 'en';
    const dateFormatter = new Intl.DateTimeFormat(locale, {
      year: 'numeric', month: 'long', day: 'numeric',
    });

    reviews.forEach(r => {
      const li = document.createElement('li');
      li.className = 'review-item';
      li.innerHTML = `
        <div class="review-author">${r.author}
          <time datetime="${r.date}" style="font-weight:400;color:#6b7280;margin-left:8px">
            ${dateFormatter.format(new Date(r.date))}
          </time>
        </div>
        <div class="review-text">${r.text}</div>
      `;
      list.appendChild(li);
    });
  }

  private renderError() {
    this.shadow.querySelector('.reviews-list')!.innerHTML =
      '<li style="color:#ef4444;padding:8px 0">Failed to load reviews</li>';
  }
}

customElements.define('review-widget', ReviewWidget);

The loader script is included once and handles existing instances in the DOM:

// src/loader.ts
import { ReviewWidget } from './ReviewWidget';

if (!customElements.get('review-widget')) {
  customElements.define('review-widget', ReviewWidget);
}

if (!window.customElements) {
  console.warn('[review-widget] Custom Elements not supported');
}

Publishing via CDN with an SRI hash ensures resource integrity. The client will not update the widget accidentally — only by intentionally changing the version in the URL.

How Development and Integration Work

1. Analysis: We study the client's environment: browsers, libraries, SEO requirements. We measure current LCP and CLS.
2. Design: Define API attributes, events, data structure. Design Shadow DOM.
3. Implementation: Write Custom Element, styles, API client. Configure build (Rollup + Terser) and CDN.
4. Testing: Test on real host sites: Chrome 54+, Firefox 63+, Safari 10.1+, Edge 79+. Measure LCP (< 1.5s), CLS (< 0.1), INP (< 200ms).
5. Deployment: Upload to CDN with SRI hash, provide client with script and documentation.

What's Included

• Development of a custom HTML element with Shadow DOM isolation.
• Integration documentation (script, attributes, events).
• Testing in target browsers.
• CDN hosting with SRI hash and versioning.
• One month of post-launch support (bug fixes, consultations).

Estimated Timeline

For a single widget of moderate complexity: 2 to 4 weeks. Complexity increases if iframe fallback is required: add up to 2 weeks for postMessage communication. Cost is calculated individually based on your stack and requirements. Request a preliminary audit — the audit fee is deducted from the development cost. We will analyze the environment and propose the optimal solution.

According to MDN Custom Elements, elements must be registered via customElements.define.

We have over 5 years of web development experience and have completed more than 30 widget embedding projects, delivering consistent LCP under 1.5 seconds and traffic savings of up to 70% (over $2,000 per month). Contact us for a project evaluation — we will analyze the environment and propose the optimal solution. Get a consultation or order widget development today.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

• React Query / TanStack Query — for server state (API data, caching, invalidation)
• Zustand — for global client state (lightweight, no Redux boilerplate)
• React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

• Source code in Git with full commit history and branching strategy
• Architecture document — component tree, data flow, routing decisions
• Component documentation – Storybook with stories for all reusable components
• CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
• Access to staging environment during development and after launch
• Team training – 2‑3 live walkthrough sessions with your developers
• 3‑month warranty on any bugs found in production
• Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.