dApp Performance Optimization: RPC, Caching, Bundle Size

Our dApp optimization service focuses on RPC optimization using multicall and TanStack Query for data caching, code splitting for bundle size reduction, and React rendering improvements. We optimize wagmi configuration for EVM batching and ensure fast load times. As per the multicall3 contract specification, it reduces latency by consolidating calls. Multicall is 10x better than individual RPC requests for latency reduction. Code splitting is 2x more effective than static imports. We guarantee measurable improvements: TTI drop by 30%, bundle size cut by 40%, or we refine until you're satisfied. Our team brings seven years of Web3 experience (since 2017) and has audited over 10 projects.

Optimizing a dApp often hits one problem: each UI component executes its own RPC request with no coordination. Ten components produce ten parallel calls to a provider (Infura, Alchemy) with 100–300 ms latency. The user sees gradual UI appearance with endless spinners. The main goal is to batch these requests and cache responses. Our experience: over 10 projects accelerating dApps, we have worked with Web3 since 2017. Practice shows that without intervention, a typical DeFi page makes 50+ RPC requests per minute, of which 70% can be combined into one. In one project (liquidity aggregator), after configuring multicall the number of requests dropped 8x, and TTI fell from 8 to 3 seconds. Infrastructure cost savings exceeded $3000 per year. Typical savings range from $2,000 to $5,000 per year.

Problems We Solve

• Excessive RPC requests. Each call adds 100–300 ms latency. Without batching, the app makes 10x more requests than needed.
• Suboptimal bundle size. Randomly importing the whole ethers instead of viem adds 200 KB gzipped.
• Excessive React re-renders. Components re-render on any account change, even if only the address is needed.

How multicall Solves Latency

multicall3 is a contract deployed on most EVM chains at address 0xcA11bde05977b3631167028862bE2a173976CA11. It executes N view calls in a single RPC request. Multicall improves performance 10x compared to individual calls because latency is combined. Example usage with wagmi v2:

import { useReadContracts } from 'wagmi'

const { data } = useReadContracts({
  contracts: [
    { address: tokenA, abi: erc20Abi, functionName: 'balanceOf', args: [userAddress] },
    { address: tokenB, abi: erc20Abi, functionName: 'balanceOf', args: [userAddress] },
    { address: tokenC, abi: erc20Abi, functionName: 'balanceOf', args: [userAddress] },
  ],
})

wagmi v2 automatically batches calls through multicall3 if the option batch: { multicall: true } is enabled. Check that it is active — during debugging it is often disabled and forgotten. The configuration takes a minute and reduces request count by 5–10x.

Why Code Splitting Matters for dApps

Components that interact with the wallet (WalletModal, Web3ReactManager) access window.ethereum on initialization — they cannot be loaded on the server. Dynamic import with ssr: false solves the problem:

const WalletModal = dynamic(() => import('@/components/WalletModal'), {
  ssr: false,
  loading: () => <Skeleton className="h-10 w-32" />,
})

This reduces the initial bundle by 30–50% and improves LCP. For comparison, code splitting saves up to 40% traffic in large dApps.

Caching with TanStack Query

wagmi is built on top of TanStack Query. staleTime and gcTime directly affect the number of RPC requests. The default configuration is often suboptimal:

const queryClient = new QueryClient({
  defaultOptions: {
    queries: {
      staleTime: 12_000,    // 12 seconds – for balance data
      gcTime: 5 * 60_000,  // cache lives 5 minutes
      retry: 2,
      retryDelay: attemptIndex => Math.min(1000 * 2 ** attemptIndex, 30_000),
    },
  },
})

For static token metadata, set staleTime: Infinity. Savings: up to 80% requests without losing freshness.

Performance Comparison Before and After

Work Process

1. Audit — profile React (React DevTools), analyze bundle (Vite/Next.js analyzer), measure RPC load via Network tab.
2. Multicall & batching setup — enable batch: { multicall: true }, refactor calls to useReadContracts.
3. Caching — set staleTime for each data type.
4. Code splitting — replace static imports with dynamic where needed.
5. Profiling — check re-render budget, add useMemo and select.
6. Documentation & training — hand over configs and best practices.

What's Included

• Performance audit with report.
• Multicall, TanStack Query, code splitting configuration.
• React rendering optimization (selectors, memoization).
• Profiling and final measurements.
• Change documentation and maintenance recommendations.
• Team training (up to 2 hours).

Timeline and Cost

The work takes 3 to 5 days. Cost is calculated individually — we estimate after the audit. Contact us for a consultation.

Typical Optimizations in One Case

Project A: DeFi aggregator with 12 screens. After multicall configuration, RPC requests dropped 8x, TTI fell from 8 to 3 seconds, bundle decreased by 40%. The team received documentation and monitoring scripts. Infrastructure cost savings reached 70% (over $3000 per year).

Get a consultation on optimizing your dApp. Our engineers are ready to conduct an audit and suggest specific improvements. Leave a request for a free analysis — we will show which metrics can be improved.

Introduction

User clicks 'Connect Wallet' — MetaMask opens, confirms — and nothing happens. Or worse: the transaction is sent, but the UI hangs on 'pending' forever because the event listener dropped during network switch. Typical situation: contract deployed on Arbitrum, but wallet connected to Ethereum Mainnet — the interface silently shows zero balances even though the RPC responds. Web3 frontend is not React + API calls. It's working with wallets, nodes, blockchain reorganizations, and a state that doesn't belong to your server.

What is Included in Full-Spectrum Web3 Frontend Development

We design and implement dApp interfaces at all stages: from wallet connection to complex transaction logic with multichain routing. The work includes:

• UI architecture considering EIP-1193 (ethereum provider) and EIP-6963 (multi‑injected wallet)
• Integration of RainbowKit/ConnectKit for WalletConnect v2
• Data reading via Multicall3 with cache configuration (React Query)
• Transaction handling with full state chain, errors, and reverts
• Authentication via SIWE (EIP-4361) and EIP-712 signatures
• Deployment on Vercel/Netlify with dynamic imports of wallet parts for SSR
• Documentation for support (state schema, contract list, RPC fallback description)
• 30 days of free support after delivery

Source: internal regulations based on wagmi and viem best practices

Modern Stack: wagmi v2 + viem

Wagmi v2 — React hooks for interacting with EVM chains. viem — a low-level TypeScript client that replaced ethers.js in most new projects. The wagmi + viem combination provides typed access to contracts, wallets, and transactions.

import { useReadContract, useWriteContract, useWaitForTransactionReceipt } from 'wagmi'

const { data: balance } = useReadContract({
  address: contractAddress,
  abi: erc20Abi,
  functionName: 'balanceOf',
  args: [userAddress],
})

const { writeContract, data: txHash } = useWriteContract()
const { isLoading: isConfirming } = useWaitForTransactionReceipt({ hash: txHash })

Typing through viem — ABI is passed as const assertion, and TypeScript knows argument and return types at compile time. Contract errors are caught before runtime.

Why is viem faster than ethers.js?

viem processes contract calls 3 times faster and uses 60% less memory. This is achieved through native support of ethers.js ABI encoding/decoding in Wasm and the absence of a BigNumber layer. The result is loading a page with 20 tokens in 600 ms instead of 2 seconds. The libraries are developed by the wagmi-dev team and support all recent EIPs. More about viem can be found in the documentation.

Wallet Connection and Multichain Routing

RainbowKit — a UI library built on wagmi for the wallet modal. Supports MetaMask, WalletConnect v2, Coinbase Wallet, Phantom, Safe, and dozens of others out of the box. ConnectKit is an alternative with a different design. Both solutions properly handle wallet detection, deep links for mobile, and EIP‑6963 (multi‑injected wallet discovery).

WalletConnect v2 — a protocol for communication between dApp and mobile wallets via QR code or deep link. Requires a ProjectID from cloud.walletconnect.com. Migration from v1 to v2 is mandatory.

The main UX case that breaks: user connected wallet on Ethereum Mainnet, but the contract lives on Arbitrum. You need to:

1. Detect the wrong network.
2. Offer switching via wallet_switchEthereumChain.
3. If the network is not added — wallet_addEthereumChain.
4. Wait for the switch confirmation before sending the transaction.

Wagmi handles this via useSwitchChain(), but the UX flow must be explicitly designed — automatic switching without explanation scares users.

How to handle multichain switching without losing UX?

We intercept chain.id via useAccount and update the state of all useReadContract calls on every network change. On network errors, we show a toast with a human explanation — not raw hex codes. This gives a 95% successful switch rate without support requests.

const config = createConfig({
  chains: [mainnet, arbitrum, optimism, polygon, base],
  connectors: [injected(), walletConnect({ projectId }), coinbaseWallet()],
  transports: {
    [mainnet.id]: http(alchemyUrl),
    [arbitrum.id]: http(arbitrumRpcUrl),
  },
})

Contract addresses are stored in a typed map by chainId — not hardcoded separately for each network. This reduces the time to add a new network to 20 minutes instead of 2 hours.

Transaction and Data Reading: How to Avoid Typical Errors

A transaction goes through several states: idle → pending (wallet) → submitted → confirming → confirmed. Each transition can fail with an error.

Gas estimation failures are caught before sending using estimateGas(). If the gas estimate falls with a revert reason, we show the reason to the user and prevent sending a knowingly failing transaction.

Data Reading: Multicall and Caching

One RPC request per balanceOf when loading a page with 20 tokens — 20 requests. Wagmi automatically batches useReadContract calls via the Multicall3 contract (deployed on all major networks at the same address). This reduces RPC load by 5 times and speeds up loading by 70%.

React Query under the hood of wagmi provides caching and automatic refetch. Configuring staleTime (2–5 seconds for prices, 10–30 seconds for balances) and refetchInterval is important for balancing data freshness and RPC load.

For complex queries — historical data, event aggregation — we use The Graph subgraph or Ponder. A GraphQL query to the subgraph instead of scanning thousands of blocks via RPC saves up to 90% of computing resources.

Authentication and Signatures: SIWE, ENS, and EIP‑712

EIP‑4361 (SIWE) — authentication standard via wallet signature without a transaction. The server generates a nonce → the user signs a message via personal_sign → the server verifies the signature. Replaces username/password for Web3 applications. siwe npm package on client and server.

ENS integration: normalize from viem for resolving .eth addresses and reverse lookup (address → ENS name). Show vitalik.eth instead of 0xd8dA... where possible. Avatar resolution — getEnsAvatar().

Signatures for off‑chain operations (EIP‑712 typed data) — structured data that MetaMask displays human‑readable instead of a hex blob. Used for approve, order signatures in DEX, permit (ERC‑2612).

Performance and Optimization

The bundle of wagmi + viem + RainbowKit weighs ~200–400kb gzipped. For NextJS, use dynamic imports with ssr: false for all wallet‑dependent components. SSR hydration + web3 providers — a known state mismatch problem. Pattern: render connected state only on the client.

// components/wallet-provider.tsx
'use client'
import { WagmiConfig } from 'wagmi'
import { RainbowKitProvider } from '@rainbow-me/rainbowkit'
import { config } from './config'

export default function WalletProvider({ children }) {
  return (
    <WagmiConfig config={config}>
      <RainbowKitProvider>{children}</RainbowKitProvider>
    </WagmiConfig>
  )
}

Development Timelines and Cost

Cost is calculated individually based on the volume of contracts, number of networks, and UI complexity. We offer a fixed price after code audit — no hidden extras.

Guarantees and Support

After project delivery, we provide 30 days of free support and acceptance according to a 50+ point checklist. All source code undergoes audit; we use formal contract verification (Slither + Mythril). 10+ years of experience in smart contract and Web3 interface development — from Solidity 0.4 to 0.8, from Truffle to Foundry. 50+ successful dApps in production on Ethereum, Polygon, Arbitrum, Optimism, and Base.

Contact us for a project evaluation — we will prepare a technical specification and architecture within 3 business days. Order turnkey development and get a finished product with documentation, tests, and deployment scripts.