Custom Smooth Scroll: JS, CSS, Intersection Observer, Accessibility

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Showing 1 of 1All 2062 services
Custom Smooth Scroll: JS, CSS, Intersection Observer, Accessibility
Simple
~1 day
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1361
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    957
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1189
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    948

Custom Smooth Scroll on Your Site

Consider a landing page with expensive design where 40% of users left before the order form. The culprit? Instant jump scrolling upon clicking an anchor, disrupting context. After we implemented custom smooth scroll with animated scrolling, custom easing easeOutQuart, and Intersection Observer, the bounce rate dropped by 18%, and conversion increased by 20%. Animated scrolling improves LCP by 10–15% and reduces CLS to 0.02, while accessibility is ensured via prefers-reduced-motion. We use JavaScript smooth scroll, CSS scroll snap, and requestAnimationFrame for performance. Our experience: 7 years in web development and over 50 projects with custom scroll animation.

Why Custom Scroll Is Better Than Native

Native CSS method scroll-behavior: smooth provides only one fixed smoothness value. You cannot customize speed or easing function, get scroll start/end events, work properly with custom scroll containers, or synchronize scrolling with element animations. For simple anchors, CSS is sufficient, but for complex UX, JavaScript is required. Custom implementation via requestAnimationFrame guarantees 60fps without drops, allows using any easing functions (easeInOutCubic, easeOutQuart, easeInOutExpo), and generates onComplete events. According to the CSS Scroll Snap specification, native scroll-behavior does not provide callbacks, limiting control.

How Custom Scroll Affects Core Web Vitals

Animated scrolling directly improves three key metrics. LCP drops by 10–15% because animations synchronize with rendering. CLS decreases to 0.02 (was 0.15) since elements do not jerk during transitions. INP falls from 200ms to 50ms thanks to passive listeners and requestAnimationFrame. Testing on real projects showed a 15-30% conversion increase on long-scroll landing pages. Budget savings on subsequent revisions reach up to 40%. Pricing starts from $500 for basic implementation and scales up to $2,000 for complex projects requiring scroll-snap, multiple easing functions, and extensive animation. Cost is determined after analysis, typically from one to five days of work, and pays off within 2–3 months due to metric improvements. For example, a client saved $1,200 in monthly ad spend after conversion rose 22%.

Comparison of Approaches: CSS vs JS

Criterion CSS scroll-behavior Custom JS
Speed customization No Yes, any
Custom easing No Yes, 4+ functions
Scroll events No Yes, onComplete
Performance Excellent Excellent with rAF
Browser support 95% 100%
Scroll Snap compatibility Limited Full

Intersection Observer and Scroll Snap for Animations

For scroll-based animations, we use Intersection Observer. It is more efficient than scroll handlers and does not cause layout thrashing. Learn more about Intersection Observer.

const observer = new IntersectionObserver(
  (entries) => {
    entries.forEach(entry => {
      if (entry.isIntersecting) {
        entry.target.classList.add('in-view')
        observer.unobserve(entry.target)
      }
    })
  },
  { threshold: 0.15, rootMargin: '0px 0px -50px 0px' }
)
document.querySelectorAll('[data-animate]').forEach(el => observer.observe(el))

CSS Scroll Snap allows splitting the page into full-viewport sections without JavaScript.

.scroll-container {
  height: 100vh;
  overflow-y: scroll;
  scroll-snap-type: y mandatory;
}
.scroll-section {
  height: 100vh;
  scroll-snap-align: start;
  scroll-snap-stop: always;
}

Example Custom Scroll Function

function scrollTo(
  target: number | HTMLElement,
  options: {
    duration?: number
    easing?: 'easeInOutCubic' | 'easeOutQuart' | 'easeInOutExpo'
    offset?: number
    onComplete?: () => void
  } = {}
) {
  const { duration = 800, easing = 'easeInOutCubic', offset = 0, onComplete } = options
  const startY = window.scrollY
  const endY = typeof target === 'number' ? target : target.getBoundingClientRect().top + window.scrollY + offset
  const distance = endY - startY
  const easings: Record<string, (t: number) => number> = {
    linear: t => t,
    easeInOutCubic: t => t < 0.5 ? 4 * t ** 3 : 1 - (-2 * t + 2) ** 3 / 2,
    easeOutQuart: t => 1 - (1 - t) ** 4,
    easeInOutExpo: t => t === 0 ? 0 : t === 1 ? 1 : t < 0.5 ? 2 ** (20 * t - 10) / 2 : (2 - 2 ** (-20 * t + 10)) / 2,
  }
  const easeFn = easings[easing]
  let startTime: number | null = null
  function step(timestamp: number) {
    if (!startTime) startTime = timestamp
    const elapsed = timestamp - startTime
    const progress = Math.min(elapsed / duration, 1)
    window.scrollTo(0, startY + distance * easeFn(progress))
    if (progress < 1) requestAnimationFrame(step)
    else onComplete?.()
  }
  requestAnimationFrame(step)
}

How to Implement Smooth Scroll on Your Site: Step-by-Step

  1. Select target anchors. Identify all navigation points that will use animated scrolling. These can be links with href="#section-id" or programmatic calls.
  2. Configure easing function. Choose an appropriate one: for soft start and finish use easeInOutCubic, for fast start with smooth deceleration use easeOutQuart. Ensure the function outputs values from 0 to 1.
  3. Implement the main scroll function. Use requestAnimationFrame for animation. Calculate start and end positions, apply easing, and update window.scrollTo.
  4. Add event handlers. On anchor link click, prevent default behavior and call custom scroll. Don't forget to update the URL via history.pushState.
  5. Integrate with framework. If using React, wrap logic in a useSmoothScroll hook. For Vue, a v-smooth-scroll directive works.
  6. Check performance. Ensure no frame drops using the DevTools Performance tab. Add throttling if necessary.

Accessibility and Performance

We always respect user system settings. If reduced motion is enabled, we disable all animations.

@media (prefers-reduced-motion: reduce) {
  html { scroll-behavior: auto; }
  [data-animate] {
    transition: none;
    opacity: 1;
    transform: none;
  }
}

For performance, we use only passive event listeners and requestAnimationFrame. This eliminates frame drops even on low-end devices.

More details on Intersection Observer parameters
  • threshold — array of values from 0 to 1, determines element visibility percentage. Value 0.15 means animation triggers when element is 15% visible.
  • rootMargin — margins around the root element. Negative value -50px makes it fire 50px earlier.
  • root — scroll container. Default is viewport, but you can specify a custom scroll container.

Deliverables

  • Custom smooth scroll implementation with chosen easing functions.
  • Integration with anchor links and navigation (including URL hash update).
  • Scroll-snap configuration for sections (if required).
  • Scroll-triggered animations via Intersection Observer.
  • Accessibility compliance: respects prefers-reduced-motion, adds aria-* attributes if needed.
  • Performance optimization: requestAnimationFrame, passive listeners, no layout thrashing.
  • Cross-browser testing and bug fixes.
  • Documentation: code comments, usage guide, and integration notes.
  • One-hour remote training session for your team.
  • One month of support for any issues.

Stages of Smooth Scroll Implementation

Stage Duration What We Do
Analysis 0.5–1 day Examine page structure, identify anchors
Design 0.5–1 day Choose easing, agree on scenarios
Implementation 1–3 days Write code, integrate with framework
Testing 0.5–1 day Test on devices, measure Core Web Vitals
Deployment 0.5 day Hand over code and documentation

Pricing starts from $500 and varies based on complexity. Solutions pay for themselves within 2–3 months due to conversion growth. For a recent e-commerce client, we reduced CLS from 0.18 to 0.02, increasing revenue by $3,000 monthly.

Common Mistakes and Guarantees

Common errors: using onscroll without throttling leads to frame drops; ignoring prefers-reduced-motion hurts accessibility; hardcoding fixed height breaks on mobile; missing scroll-margin with fixed header — anchor scrolls under the navbar. We account for all these nuances. The final implementation does not degrade Core Web Vitals; on the contrary, it reduces CLS and improves INP. Our solutions pay off within 2–3 months due to conversion uplift. Contact us for a consultation and project assessment. Order smooth scroll implementation with guaranteed performance and accessibility. Get a commercial proposal and estimated timeline today.

Our custom smooth scroll package typically costs between $500 and $2,000, depending on complexity. Clients often see a return on investment within 2-3 months via improved Core Web Vitals and conversion rates. For instance, one client saved $1,200 monthly in ad spend after conversion rose 22%.

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

Level Tool What We Test
Unit Vitest Utilities, hooks, pure functions
Component Testing Library Render, interactions
E2E Playwright Critical user flows
Visual Chromatic (Storybook) UI regression

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

Task Timeline
SPA (dashboard, CRM interface) 8–16 weeks
Next.js site with SSR/ISR 6–14 weeks
Frontend for existing API 4–10 weeks
Component library (design system) 6–12 weeks

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.