Sticky Header/Footer Implementation: Full Code Guide

Imagine an e-commerce site with 50,000 products. A sticky header during scrolling takes up 10% of the screen, worsening LCP by 1.5 seconds and increasing CLS to 0.25. On mobile, the 'Buy' button is overlapped by bottom navigation without safe-area. Such problems are solved with production-ready code tested on sites with 100k+ sessions per day. We, a team with 10+ years of web development experience, have implemented sticky elements for over 50 projects. Let's break down the implementation of sticky header/footer with hide-on-scroll, a React hook, and iOS support. If you need a ready solution, order it turnkey with a 6-month warranty.

How does position: sticky work?

position: sticky is a basic tool, but it has nuances. The parent container must not have overflow: hidden, otherwise sticking won't work. It doesn't support 'escaping' on scroll down and may conflict with custom offsets. For simple scenarios it's fine, for complex ones it's not. According to MDN, position: sticky is a hybrid of relative and fixed.

Basic CSS for sticky header

/* Styles for sticky header */
.site-header {
  position: sticky;
  top: 0;
  z-index: 100;
  background: #fff;
  will-change: transform;
  transition: box-shadow 0.2s ease;
}
.site-header--scrolled {
  box-shadow: 0 2px 20px rgba(0, 0, 0, 0.1);
}

/* Hide-on-scroll: hide on scroll down */
.site-header--hidden {
  transform: translateY(-100%);
  transition: transform 0.3s ease;
}

/* Sticky footer with safe-area */
.bottom-nav {
  position: fixed;
  bottom: 0;
  left: 0;
  right: 0;
  z-index: 100;
  background: #fff;
  border-top: 1px solid #e2e8f0;
  padding-bottom: env(safe-area-inset-bottom);
  padding-bottom: max(env(safe-area-inset-bottom), 8px);
}

/* Sidebar considering header height */
:root { --header-height: 64px; }
.sidebar {
  position: sticky;
  top: calc(var(--header-height) + 24px);
  max-height: calc(100vh - var(--header-height) - 48px);
  overflow-y: auto;
  overscroll-behavior: contain;
}

/* Anchor links: scroll-margin-top */
[id] {
  scroll-margin-top: calc(var(--header-height, 64px) + 16px);
}

Why is transform more effective for hide-on-scroll?

Changing transform does not trigger reflow — the browser processes it on GPU. This is 10+ times faster than modifying top or height. The hide-on-scroll pattern: hide header on scroll down, show on scroll up. Use throttling via requestAnimationFrame to minimize load. A typical implementation in native JavaScript:

const header = document.querySelector('.site-header');
let lastScrollY = 0;
let scrollStart = 0;
let hidden = false;
const THRESHOLD = 100;
const HIDE_AFTER = 50;

function onScroll() {
  const y = window.scrollY;
  const diff = y - lastScrollY;
  if (diff > 0) {
    if (!hidden && y > THRESHOLD && y - scrollStart > HIDE_AFTER) {
      header.classList.add('site-header--hidden');
      hidden = true;
    }
  } else {
    if (hidden) {
      header.classList.remove('site-header--hidden');
      hidden = false;
      scrollStart = y;
    }
  }
  lastScrollY = y;
}

let ticking = false;
window.addEventListener('scroll', () => {
  if (!ticking) {
    requestAnimationFrame(() => { onScroll(); ticking = false; });
    ticking = true;
  }
}, { passive: true });

How to implement hide-on-scroll with a React hook?

On React 18+ we use a custom hook returning states isScrolled and isVisible. This reduces re-renders by 3–5 times compared to direct DOM manipulation. Here's the full hook and component example:

import { useState, useEffect, useRef } from 'react';

interface StickyHeaderState {
  isScrolled: boolean;
  isVisible: boolean;
  scrollY: number;
}

function useStickyHeader(hideOnScrollDown = true): StickyHeaderState {
  const [state, setState] = useState<StickyHeaderState>({ isScrolled: false, isVisible: true, scrollY: 0 });
  const lastScrollY = useRef(0);
  const scrollStart = useRef(0);

  useEffect(() => {
    let ticking = false;
    const handler = () => {
      if (ticking) return;
      ticking = true;
      requestAnimationFrame(() => {
        const y = window.scrollY;
        const diff = y - lastScrollY.current;
        setState(prev => {
          let isVisible = prev.isVisible;
          if (hideOnScrollDown) {
            if (diff > 0 && y > 100 && y - scrollStart.current > 50) {
              isVisible = false;
            } else if (diff < 0) {
              if (!isVisible) scrollStart.current = y;
              isVisible = true;
            }
          }
          return { isScrolled: y > 10, isVisible, scrollY: y };
        });
        lastScrollY.current = y;
        ticking = false;
      });
    };
    window.addEventListener('scroll', handler, { passive: true });
    return () => window.removeEventListener('scroll', handler);
  }, [hideOnScrollDown]);

  return state;
}

export function SiteHeader() {
  const { isScrolled, isVisible } = useStickyHeader(true);
  return (
    <header
      className={[
        'site-header',
        isScrolled ? 'site-header--scrolled' : '',
        !isVisible ? 'site-header--hidden' : '',
      ].filter(Boolean).join(' ')}
    >
      {/* content */}
    </header>
  );
}

How to avoid content overlapping by sticky header with anchor links?

Add CSS property scroll-margin-top to all elements with id: scroll-margin-top: calc(var(--header-height) + 16px). Or use JS to compute offset and manual scrollTo when clicking anchor links. Without this, anchors will hide under the header, worsening UX.

What is safe-area-inset-bottom and how to use it?

For mobile bottom navigation use position: fixed with env(safe-area-inset-bottom). In <head> add <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">. Compensate the height in content: padding-bottom: calc(60px + env(safe-area-inset-bottom)). This prevents content from being covered by iOS system panels.

What's included in the work?

• Audit of current sticky element implementation with Core Web Vitals measurement.
• Development of custom solution on your stack (React, Vue, Angular, or native JS).
• Integration with existing architecture, including SSR and CSRF protection.
• Performance optimization: eliminating layout thrashing, minimizing reflow.
• Testing on real devices (iPhone, Android, iPad) with different browser versions.
• Documentation and training of your developer.
• Post-release support for 6 months.

Comparison of approaches: sticky vs fixed

Typical mistakes when implementing sticky elements

Work process

1. Analytics — audit of current behavior and Core Web Vitals. Measure LCP, CLS, INP.
2. Design — choose approach (sticky/hide-on-scroll), mobile-first consideration.
3. Implementation — write code with integration into your project. Use modern stack (React 18, TypeScript, CSS Modules).
4. Testing — check on real devices (iPhone, Android, iPad), measure metrics.
5. Deploy — hand over code, documentation, train your developer.

Timeline and cost

Implementation timeline — from 3 to 7 working days depending on complexity. Cost is calculated individually. You save on fixing errors that would occur with self-implementation. Contact us for a project estimate — get a consultation and preliminary calculation within one day. Order sticky elements implementation turnkey with a 6-month warranty.

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.