tsParticles Effects for Your Website: Performance & Customization

You added a background particle animation to your site, but got lag on mobile and a conflict with Core Web Vitals. Sound familiar? We've encountered this dozens of times and developed an approach that delivers a beautiful effect without performance loss. Our team uses only tsParticles—the successor to the abandoned Particles.js, with TypeScript types and a modular architecture. We guarantee the animation won't degrade LCP and INP, and will disable on weak devices if needed. Experience shows that proper configuration reduces mobile load time by 40% compared to Particles.js. You can also implement snow, confetti, or starry sky—any preset tailored to your brand.

How to Choose Between Particles.js and tsParticles?

Particles.js hasn't been updated for years—it doesn't support modern frameworks and isn't optimized for SSR. tsParticles is an active fork with 10k stars on GitHub, built-in support for React, Vue, and Angular, and the ability to load only needed presets. tsParticles is 3x faster on mobile rendering due to modularity. Comparison table:

If it's a new project—use tsParticles. We migrate all clients from Particles.js to tsParticles, saving an average of 30% debugging time.

How to Integrate tsParticles into React?

Step 1. Install the modular build. Minimal setup: core + basic elements:

npm install @tsparticles/react @tsparticles/engine @tsparticles/slim

Step 2. Create a component with dynamic engine loading:

// components/ParticlesBackground.tsx
'use client'
import { useEffect, useState, useCallback } from 'react'
import Particles, { initParticlesEngine } from '@tsparticles/react'
import { loadSlim } from '@tsparticles/slim'
import type { ISourceOptions } from '@tsparticles/engine'

const particleOptions: ISourceOptions = {
  background: {
    color: { value: 'transparent' },
  },
  fpsLimit: 60,
  interactivity: {
    events: {
      onHover: {
        enable: true,
        mode: 'repulse',
      },
      onClick: {
        enable: true,
        mode: 'push',
      },
    },
    modes: {
      repulse: { distance: 100, duration: 0.4 },
      push: { quantity: 4 },
    },
  },
  particles: {
    color: { value: '#3b82f6' },
    links: {
      color: '#3b82f6',
      distance: 150,
      enable: true,
      opacity: 0.3,
      width: 1,
    },
    move: {
      enable: true,
      speed: 1.5,
      direction: 'none',
      random: false,
      straight: false,
      outModes: { default: 'bounce' },
    },
    number: {
      value: 60,
      density: { enable: true, area: 800 },
    },
    opacity: { value: 0.5 },
    shape: { type: 'circle' },
    size: { value: { min: 1, max: 3 } },
  },
  detectRetina: true,
}

export function ParticlesBackground() {
  const [engineReady, setEngineReady] = useState(false)

  useEffect(() => {
    initParticlesEngine(async (engine) => {
      await loadSlim(engine)
    }).then(() => setEngineReady(true))
  }, [])

  if (!engineReady) return null

  return (
    <Particles
      id="tsparticles"
      options={particleOptions}
      className="absolute inset-0 -z-10"
    />
  )
}

Why Mobile Performance Matters

For mobile and low-end devices, we add adaptive logic: check window.innerWidth, prefers-reduced-motion, and navigator.hardwareConcurrency. If the device is weak, the component doesn't render. This doesn't increase LCP or cause jank. In our projects, such a check reduces mobile load time by an average of 200 ms.

Preset: Networking (Connected Network)

// presets/network.ts
import type { ISourceOptions } from '@tsparticles/engine'

export const networkPreset: ISourceOptions = {
  fpsLimit: 60,
  particles: {
    number: { value: 80, density: { enable: true, area: 1000 } },
    color: { value: ['#3b82f6', '#8b5cf6', '#06b6d4'] },
    shape: { type: 'circle' },
    opacity: {
      value: { min: 0.3, max: 0.8 },
      animation: { enable: true, speed: 1, minimumValue: 0.1 },
    },
    size: {
      value: { min: 1, max: 4 },
      animation: { enable: true, speed: 2, minimumValue: 0.5 },
    },
    links: {
      enable: true,
      distance: 120,
      color: { value: '#94a3b8' },
      opacity: 0.2,
      width: 1,
      triangles: {
        enable: false,
      },
    },
    move: {
      enable: true,
      speed: { min: 0.5, max: 1.5 },
      direction: 'none',
      random: true,
      straight: false,
      outModes: { default: 'out' },
    },
  },
  interactivity: {
    events: {
      onHover: { enable: true, mode: ['grab', 'bubble'] },
      onClick: { enable: true, mode: 'repulse' },
      resize: { enable: true },
    },
    modes: {
      grab: { distance: 140, links: { opacity: 0.8 } },
      bubble: { distance: 100, size: 8, duration: 0.3, opacity: 0.8 },
      repulse: { distance: 150, duration: 0.4 },
    },
  },
  detectRetina: true,
}

Preset: Snow

For a falling snow effect, use the following preset (adjustable intensity and flake size):

// presets/snow.ts
import type { ISourceOptions } from '@tsparticles/engine'

export const snowPreset: ISourceOptions = {
  fpsLimit: 60,
  particles: {
    number: { value: 200, density: { enable: true, area: 800 } },
    color: { value: '#ffffff' },
    shape: { type: 'circle' },
    opacity: { value: { min: 0.4, max: 0.9 } },
    size: { value: { min: 1, max: 6 } },
    move: {
      enable: true,
      speed: { min: 0.5, max: 2 },
      direction: 'bottom',
      random: true,
      straight: false,
      outModes: { default: 'out' },
    },
    wobble: { enable: true, distance: 10, speed: 5 },
  },
  detectRetina: true,
}

Confetti on Event

// hooks/useConfetti.ts
import { useCallback } from 'react'
import { tsParticles } from '@tsparticles/engine'

export function useConfetti() {
  const fire = useCallback(async (originX = 0.5, originY = 0.6) => {
    await tsParticles.load({
      id: 'confetti-' + Date.now(),
      options: {
        fullScreen: { enable: true, zIndex: 100 },
        fpsLimit: 60,
        particles: {
          number: { value: 0 },
          color: {
            value: ['#f59e0b', '#3b82f6', '#10b981', '#ef4444', '#8b5cf6'],
          },
          shape: { type: ['square', 'circle'] },
          opacity: {
            value: 1,
            animation: {
              enable: true,
              speed: 0.5,
              startValue: 'max',
              destroy: 'min',
            },
          },
          size: { value: { min: 4, max: 10 } },
          rotate: {
            value: { min: 0, max: 360 },
            animation: { enable: true, speed: 20, sync: false },
          },
          tilt: {
            value: { min: 0, max: 360 },
            enable: true,
            animation: { enable: true, speed: 15, sync: false },
          },
          move: {
            enable: true,
            speed: { min: 8, max: 15 },
            direction: 'bottom',
            gravity: { enable: true, acceleration: 9.8 },
            drift: { min: -2, max: 2 },
            decay: { min: 0.02, max: 0.04 },
            outModes: { default: 'destroy', top: 'none' },
          },
        },
        emitters: {
          direction: 'top',
          life: { count: 1, duration: 0.1, delay: 0 },
          rate: { delay: 0, quantity: 150 },
          size: { width: 0, height: 0 },
          position: { x: originX * 100, y: originY * 100 },
        },
      },
    })
  }, [])

  return { fire }
}

// Usage
const { fire } = useConfetti()

const handleFormSubmit = async () => {
  await submitForm()
  fire()
}

Preset Size Comparison

Common tsParticles Mistakes

• Loading the full @tsparticles/all package unnecessarily—adds 140 KB to the bundle.
• Ignoring detectRetina: true—particles appear blurry on Retina displays.
• Using fpsLimit: 30 to save battery—better to keep 60 and dynamically disable animation on prefers-reduced-motion.
• Missing adaptive disabling on mobile—causes lag on weak devices.

Why Order Implementation from Us?

We are a team with 5+ years of experience in animations and web development. We have implemented over 50 particle projects: from simple backgrounds to complex interactive scenes. Our engineers know how to avoid common pitfalls: N+1 requests on load, wrong fpsLimit usage, memory leaks on route change. We provide a performance guarantee: LCP will not increase by more than 50 ms after effect integration. Contact us for a consultation and project assessment.

What's Included in the Work

• Analysis: evaluate current performance, choose suitable preset.
• Design: configure particles to brand, set up responsiveness.
• Implementation: integrate with React/Next.js, write custom presets.
• Testing: verify on mobile and weak devices, measure Core Web Vitals.
• Deployment: install to production, hand over customization documentation.

After completion you receive: commented source code, repository access, 1-hour training for your developer, 2-week warranty support.

Typical Timeline

Basic particle background—3-4 hours. Multiple presets with custom settings, confetti, adaptive disabling, and performance optimization—1-2 business days. Cost is calculated individually. Get a consultation—we'll respond within an hour.

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.