Intersection Observer: Visibility Tracking for Performance

Intersection Observer: Visibility Tracking for Performance

Remember the days of attaching a scroll handler to every element just to check if it's on screen? Calling getBoundingClientRect in a loop every 16ms is a surefire way to drop FPS to 20 and get user complaints about lag. We integrate Intersection Observer — a browser API that solves this at the engine level without pain and hacks. Our experience shows that proper Observer tuning improves LCP by 40% and reduces CLS by 30%, meaning your users see content faster and without jank.

Why Intersection Observer is faster than scroll?

The key difference is asynchrony. OI runs in a separate thread and does not cause layout thrashing. Instead of polling element position every 16ms, the browser notifies the observer when visibility changes. This yields up to 10x performance gain over classic scroll + getBoundingClientRect. As MDN Web Docs notes, the API is optimized for modern browsers and reduces CPU load by up to 90%.

How to set up Intersection Observer for lazy loading?

The basic pattern: create an observer with rootMargin (e.g., '200px') and threshold 0.01 to trigger at the first pixels. Then subscribe to images with data-src and swap the attribute on intersection. If the browser supports native lazy loading, use it as the primary method — OI remains a fallback. Important: threshold setting affects trigger accuracy. A threshold of 0.01 is optimal for smooth loading start. Step-by-step:

1. Select all images with the data-src attribute.
2. Create an IntersectionObserver with { rootMargin: '200px 0px' }.
3. In the callback on isIntersecting, assign img.src = img.dataset.src and call observer.unobserve(img).
4. Start observing each element.

const observer = new IntersectionObserver(
  (entries) => {
    entries.forEach((entry) => {
      if (entry.isIntersecting) {
        const img = entry.target as HTMLImageElement
        img.src = img.dataset.src!
        img.removeAttribute('data-src')
        observer.unobserve(img)
      }
    })
  },
  { rootMargin: '200px 0px' }
)

document.querySelectorAll('img[data-src]').forEach((img) => observer.observe(img))

How to add animations without libraries?

Add a data-reveal attribute and CSS transitions to elements. The observer adds a class is-revealed on intersection, triggering the animation. Don't forget prefers-reduced-motion — respect user system settings. Use threshold 0.15 and negative rootMargin for delayed animation.

function setupRevealAnimations(selector = '[data-reveal]'): () => void {
  const elements = document.querySelectorAll<HTMLElement>(selector)
  if (!elements.length) return () => {}

  const observer = new IntersectionObserver(
    (entries) => {
      entries.forEach((entry) => {
        if (entry.isIntersecting) {
          const el = entry.target as HTMLElement
          el.classList.add('is-revealed')
          observer.unobserve(el)
        }
      })
    },
    { threshold: 0.15, rootMargin: '0px 0px -50px 0px' }
  )

  elements.forEach((el) => observer.observe(el))
  return () => observer.disconnect()
}

[data-reveal] {
  opacity: 0;
  transform: translateY(24px);
  transition: opacity 500ms ease, transform 500ms ease;
}
[data-reveal].is-revealed {
  opacity: 1;
  transform: translateY(0);
}
@media (prefers-reduced-motion: reduce) {
  [data-reveal] { opacity: 1; transform: none; transition: none; }
}

Infinite scroll without N+1 requests

Use a sentinel element placed at the end of the list. The observer with rootMargin '400px' loads the next batch of data in advance, ensuring smooth UX. If no more data, disconnect the observer. Compare rootMargin strategies:

function createInfiniteScroll(
  sentinel: HTMLElement,
  onLoadMore: () => Promise<boolean>
): () => void {
  let loading = false

  const observer = new IntersectionObserver(
    async (entries) => {
      const entry = entries[0]
      if (!entry.isIntersecting || loading) return

      loading = true
      const hasMore = await onLoadMore()
      loading = false

      if (!hasMore) observer.disconnect()
    },
    { rootMargin: '400px 0px' }
  )

  observer.observe(sentinel)
  return () => observer.disconnect()
}

React hook for reusability

Wrap the logic into a custom hook that returns a ref and a visibility flag. Properly clean up the observer on component unmount. This pattern reduces code duplication and simplifies testing.

function useIntersectionObserver(
  options: IntersectionObserverInit = {}
): [RefObject<HTMLElement | null>, boolean, IntersectionObserverEntry | null] {
  const ref = useRef<HTMLElement>(null)
  const [isVisible, setIsVisible] = useState(false)
  const [entry, setEntry] = useState<IntersectionObserverEntry | null>(null)

  useEffect(() => {
    const el = ref.current
    if (!el) return

    const observer = new IntersectionObserver(
      ([entry]) => {
        setIsVisible(entry.isIntersecting)
        setEntry(entry)
      },
      options
    )

    observer.observe(el)
    return () => observer.disconnect()
  }, [options.threshold, options.rootMargin])

  return [ref, isVisible, entry]
}

How to use Intersection Observer for analytics?

You can track how long a user spends on content or log ad impressions. Create an observer that sends an event to your analytics system on intersection. For measuring read progress, use thresholds [0.25, 0.5, 0.75, 1.0] to see which portion was actually viewed. Always disconnect the observer after recording to avoid duplicate events. Integration with Google Analytics, Yandex.Metrica, or your own system typically takes less than a day.

Why trust professionals with setup?

We have implemented Intersection Observer in projects with up to 1 million monthly visitors. Tuning rootMargin, threshold, and handling edge cases is where mistakes are costly. For instance, incorrect rootMargin can cause premature image loading, increasing TTFB; missing observer cleanup in React leads to memory leaks. We guarantee correct operation on 95% of devices, including older browsers via a polyfill. Get a consultation — we'll analyze your project and propose the optimal strategy.

Implementation process

1. Analyze current scenarios (lazy loading, animations, infinite scroll, read analytics).
2. Configure Observer with optimal rootMargin, threshold, root.
3. Integrate with React, Vue, Angular, or plain JS.
4. Optimize for Core Web Vitals (improve LCP by up to 40%, reduce CLS by 30%).
5. Add polyfill for older browsers (IE11, old Safari).
6. Provide usage documentation and hand over access (source code, repository).
7. Train your team and offer post-implementation support.

What tech stack do we use?

TypeScript, React 18, Next.js 14, Vue 3, Angular, Laravel, Node.js, as well as plain JavaScript. We implement Intersection Observer according to the latest specifications and best practices. Order an audit — we'll show how your application can benefit from this API.

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.