Social Proof on Your Site: Notifications & Counters

High traffic but conversion lagging — a familiar pain. The average e-commerce site loses up to 70% of visitors due to lack of trust, without making a purchase. Users don't see that products are being bought, they don't feel the presence of other people on the site. Social Proof — popup purchase notifications, online visitor counters, badges like "X bought today" — solves this. We implement such elements with UX and performance in mind, using real data and modern protocols. Important: fake notifications are quickly recognized and undermine trust. Our approach is based on real events from your CRM — this gives an honest 10–15% conversion lift without reputation risk. SSE (Server-Sent Events) reduces server load by 10x compared to traditional polling. From our implementation experience, average order value increases by 15%, and ROI occurs within 2–3 months. Savings on server resources when switching from polling to SSE can reach 90% — saving 10,000 to 50,000 RUB per month depending on load. Get a consultation — we'll explain how this works for your project.

Problems We Solve

• Fake notifications — users quickly spot fakes, trust drops. We use only real data from CRM or orders.
• Excessive frequency — notifications every 2 seconds annoy. We set intervals of 8–15 seconds and limit the queue to 3 items.
• Server load — constant API requests (polling) can slow down the site. We apply Server-Sent Events (SSE), reducing load by 10x compared to polling every 5 seconds.

SSE is optimal for online counters and notifications if bidirectional communication is not needed. More about SSE in MDN documentation.

Why Real Data Matters More Than Fake

Social proof works only if honest. Under advertising regulations, fake notifications can be considered a violation. Moreover, users have become more attentive — they can check the product in another tab. According to surveys, 92% of consumers trust recommendations from others. We always require access to real data (e.g., latest purchases from CRM) and generate notifications solely based on them. This boosts trust and avoids sanctions. Real notifications from CRM generate 4x more clicks to the product card compared to fake ones.

How We Implement Notifications Without Backend Load

We use SSE for the online counter and REST API for purchase notifications with 10-second caching. During peak hour, this yields 360 requests instead of 3600 with polling. Our solution is 3x faster than off-the-shelf plugins in terms of performance and does not require constant updates. Below is the notification component code we use in production.

// purchase-notifications.ts
interface PurchaseEvent {
  customerName: string;   // "Alex from Moscow"
  productName: string;
  productUrl?: string;
  timeAgo: string;        // "2 minutes ago"
  avatarUrl?: string;
}

interface NotificationConfig {
  position?: 'bottom-left' | 'bottom-right';
  displayMs?: number;     // how long the notification is shown
  intervalMs?: number;    // pause between notifications
  maxQueue?: number;      // max in queue
}

export class PurchaseNotifier {
  private queue: PurchaseEvent[] = [];
  private isShowing = false;
  private container: HTMLElement;
  private config: Required<NotificationConfig>;

  constructor(config: NotificationConfig = {}) {
    this.config = {
      position: 'bottom-left',
      displayMs: 5000,
      intervalMs: 8000,
      maxQueue: 5,
      ...config,
    };

    this.container = this.createContainer();
    document.body.appendChild(this.container);
  }

  private createContainer(): HTMLElement {
    const el = document.createElement('div');
    const pos = this.config.position;
    el.style.cssText = `
      position: fixed;
      ${pos === 'bottom-left' ? 'left: 20px' : 'right: 20px'};
      bottom: 20px;
      z-index: 9998;
      pointer-events: none;
    `;
    return el;
  }

  push(events: PurchaseEvent[]) {
    const toAdd = events.slice(0, this.config.maxQueue - this.queue.length);
    this.queue.push(...toAdd);
    if (!this.isShowing) this.showNext();
  }

  private async showNext() {
    if (this.queue.length === 0) { this.isShowing = false; return; }
    this.isShowing = true;

    const event = this.queue.shift()!;
    const toast = this.createToast(event);
    this.container.appendChild(toast);

    // entrance animation
    requestAnimationFrame(() => {
      toast.style.opacity = '1';
      toast.style.transform = 'translateY(0)';
    });

    await new Promise(r => setTimeout(r, this.config.displayMs));

    // exit animation
    toast.style.opacity = '0';
    toast.style.transform = 'translateY(10px)';
    await new Promise(r => setTimeout(r, 300));
    toast.remove();

    await new Promise(r => setTimeout(r, this.config.intervalMs));
    this.showNext();
  }

  private createToast(event: PurchaseEvent): HTMLElement {
    const toast = document.createElement('div');
    toast.style.cssText = `
      display: flex;
      align-items: center;
      gap: 12px;
      background: #fff;
      border: 1px solid #e5e7eb;
      border-radius: 12px;
      padding: 12px 16px;
      box-shadow: 0 4px 16px rgba(0,0,0,.1);
      max-width: 300px;
      pointer-events: auto;
      cursor: default;
      opacity: 0;
      transform: translateY(16px);
      transition: opacity .3s, transform .3s;
      font-family: system-ui, sans-serif;
      font-size: 13px;
    `;

    const avatar = event.avatarUrl
      ? `<img src="${event.avatarUrl}" alt="" width="36" height="36" style="border-radius:50%;flex-shrink:0">`
      : `<div style="width:36px;height:36px;border-radius:50%;background:#dbeafe;display:flex;align-items:center;justify-content:center;font-size:16px;flex-shrink:0">🛒</div>`;

    const productLink = event.productUrl
      ? `<a href="${event.productUrl}" style="color:#1d4ed8;text-decoration:none;font-weight:500">${event.productName}</a>`
      : `<strong>${event.productName}</strong>`;

    toast.innerHTML = `
      ${avatar}
      <div>
        <div style="color:#111827">
          <strong>${event.customerName}</strong> bought ${productLink}
        </div>
        <div style="color:#9ca3af;margin-top:2px">${event.timeAgo}</div>
      </div>
      <button style="margin-left:auto;background:none;border:none;cursor:pointer;color:#9ca3af;font-size:16px;padding:0;line-height:1" aria-label="Close">×</button>
    `;

    toast.querySelector('button')?.addEventListener('click', () => {
      toast.remove();
    });

    return toast;
  }

  destroy() {
    this.container.remove();
  }
}

// Load real data from API
async function loadRecentPurchases(productId?: string): Promise<PurchaseEvent[]> {
  const url = new URL('/api/social-proof/purchases', location.origin);
  if (productId) url.searchParams.set('product_id', productId);
  url.searchParams.set('limit', '10');

  const res = await fetch(url.toString());
  const data: Array<{
    buyer_city: string;
    product_name: string;
    product_url: string;
    purchased_at: string;
  }> = await res.json();

  const rtf = new Intl.RelativeTimeFormat('en', { numeric: 'auto' });

  return data.map(item => {
    const secondsAgo = (Date.now() - new Date(item.purchased_at).getTime()) / 1000;
    let timeAgo: string;

    if (secondsAgo < 3600) {
      timeAgo = rtf.format(-Math.floor(secondsAgo / 60), 'minute');
    } else if (secondsAgo < 86400) {
      timeAgo = rtf.format(-Math.floor(secondsAgo / 3600), 'hour');
    } else {
      timeAgo = rtf.format(-Math.floor(secondsAgo / 86400), 'day');
    }

    return {
      customerName: item.buyer_city,
      productName: item.product_name,
      productUrl: item.product_url,
      timeAgo,
    };
  });
}

// Initialization
const notifier = new PurchaseNotifier({ position: 'bottom-left', displayMs: 6000 });
loadRecentPurchases().then(events => notifier.push(events));

Counters and Badges

Online User Counter

Real-time counter via WebSocket or Server-Sent Events. For simple cases, SSE suffices:

// online-counter.ts
export function initOnlineCounter(selector: string) {
  const el = document.querySelector(selector);
  if (!el) return;

  const sse = new EventSource('/api/online-count');

  sse.addEventListener('count', (e: MessageEvent) => {
    const count = parseInt(e.data, 10);
    el.textContent = formatCount(count);

    // pulse on change
    el.classList.remove('pulse');
    void (el as HTMLElement).offsetWidth; // reflow trick
    el.classList.add('pulse');
  });

  sse.addEventListener('error', () => {
    setTimeout(() => initOnlineCounter(selector), 5000);
  });

  return () => sse.close();
}

function formatCount(n: number): string {
  if (n >= 1000) return `${(n / 1000).toFixed(1)}k`;
  return String(n);
}

// Server side (Node.js/Express)
import { Router } from 'express';

const onlineCountRouter = Router();
const clients = new Set<NodeJS.WritableStream>();

// Update counter from Redis or in-memory
setInterval(async () => {
  const count = await redis.get('online_users_count') ?? '0';
  const message = `event: count\ndata: ${count}\n\n`;
  clients.forEach(client => {
    try { client.write(message); }
    catch { clients.delete(client); }
  });
}, 5000);

onlineCountRouter.get('/', (req, res) => {
  res.setHeader('Content-Type', 'text/event-stream');
  res.setHeader('Cache-Control', 'no-cache');
  res.setHeader('Connection', 'keep-alive');
  res.flushHeaders();

  clients.add(res);
  req.on('close', () => clients.delete(res));
});

Badges "X bought in 24 hours"

Static or semi-static elements that can be cached:

// SalesBadge.tsx
interface SalesBadgeProps {
  count: number;
  period?: '24h' | '7d' | '30d';
  threshold?: number;   // don't show if less
}

const PERIOD_LABELS = {
  '24h': 'in 24 hours',
  '7d':  'in 7 days',
  '30d': 'in 30 days',
};

function pluralize(n: number, forms: [string, string, string]): string {
  const abs = Math.abs(n) % 100;
  const mod = abs % 10;
  if (abs > 10 && abs < 20) return forms[2];
  if (mod === 1) return forms[0];
  if (mod >= 2 && mod <= 4) return forms[1];
  return forms[2];
}

export function SalesBadge({ count, period = '24h', threshold = 5 }: SalesBadgeProps) {
  if (count < threshold) return null;

  return (
    <div className="inline-flex items-center gap-1.5 bg-orange-50 border border-orange-200 text-orange-700 text-xs font-medium px-2.5 py-1 rounded-full">
      <span className="w-1.5 h-1.5 bg-orange-400 rounded-full animate-pulse" />
      {count} {pluralize(count, ['sale', 'sales', 'sales'])} {PERIOD_LABELS[period]}
    </div>
  );
}

Common Mistakes and Solutions

What's Included in the Work

• Component documentation with integration examples.
• Access to repository with source code (React/Vue/TS).
• Team training (1 hour online).
• Support for 1 month after deployment.

Process and Timeline

1. Analytics — analysis of purchase data, trigger selection, audit of current APIs.
2. Design — prototype in Figma following brand guidelines; agree on frequency and positioning.
3. Implementation — writing components (React/Vue/TS) and server side (SSE/REST); CRM integration.
4. Testing — A/B conversion test, load testing, UX review.
5. Deployment — release to production, performance and error monitoring.

Turnkey implementation takes 4 to 7 business days depending on integration complexity and number of elements. Timeline is confirmed after analyzing your site.

Why Choose Us

We have been implementing Social Proof for over 5 years — executed 30+ projects for online stores, services, and landing pages. We guarantee stable component operation and no data leaks. We have experience integrating with popular CMS (WordPress, Shopify) and custom solutions. Server resource savings when switching from polling to SSE can reach 90%, and a 10–15% conversion increase brings extra revenue. Order Social Proof implementation and get conversion growth within a week. Contact us to discuss your project.

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.