/handbook/react-best-practices/data-loading/
What We Do
Digital Platform MigrationsKey SolutionsManaged ServicesStaffing SolutionsIndustriesProducts
Discovery
Strategic consultancy & project roadmap
Growth Services
On demand development & consultation
Site Maintenance
Annual maintenance. Done for you
QE Services
Testing across SDLC for assured quality
Hosting Migration
Move to a performant hosting with zero downtime
WooCommerce
Enterprise commerce delivered without lock-in
AI
Unlock real use cases and integrations
All Services
A suite of services for any need
Technology STACK
eCommerce
Scale your e-commerce with WooCommerce, integrations, and custom extensions for growth.
EasyEngine
Server management tool that makes using WordPress on Nginx easy.
Web Auditor
Performance Audit & Insights for your Website.
rtMedia
A complete media management plugin for WordPress.
Resources
About Us
CLEAR
Resources React project best practices Data loading
Topics
On this page
- React project best practices
- Project structure
- State management
- Component architecture
- Styling
- Hooks
- Performance optimization
- Commit messages
- Code quality
- Data loading
- Testing
- Dependency management
- Accessibility
- React frameworks
- Documentation
- Deployment and monitoring
- React skeleton
- Appendices
The problem with naive data fetching
1. Race condition
2. No loading state
3. No error handling
4. Fetch request is never aborted
5. No caching
6. Network waterfall
The TanStack Query solution
1. Race condition
2. Loading state
3. Error management
4. Request abortion
5. Caching and deduplication
Key takeaways
Last updated on Apr 2, 2026
Data loading
Fetching data in React seems simple at first, but doing it right is crucial for performance, scalability, and user experience. A naive approach with useEffect often leads to issues like race conditions, missing loading/error states, unnecessary network requests, and poor caching
The problem with naive data fetching
If you want to fetch data from an useEffect manually, your code might look like this:
import { useState, useEffect } from 'react';
import { fetchBio } from './api.js';
export default function Page() {
const [person, setPerson] = useState('Alice');
const [bio, setBio] = useState(null);
useEffect(() => {
setBio(null);
fetchBios(person).then(()=>{
setBio(result);
});
}, [person]);
…
}
The example shown has the following problems:
1. Race condition
- If
personchanges quickly, old requests may overwrite newer ones. - If an instance of this component is rendered multiple times, the response may come out of order, and the latest data will not be shown. One solution is to add a cleanup function with an ignore flag.
2. No loading state
- Users see a blank screen until data arrives.
- Ideally, the UI should show a loading indicator or stale data to the user for better UX.
3. No error handling
- Failures crash silently.
- Any fetch request can fail, sometimes for known reasons. These errors should be caught, and the UI should respond.
4. Fetch request is never aborted
- Even if this component is unmounted, the fetch request will go through and use resources.
- This causes wasted network and memory when unmounted.
5. No caching
Every re-render triggers another request. Responses to a data fetch request should be cached. Caching provides the following improvement opportunities:
- Showing cached data immediately displays relevant information. The stale data can be updated later. This is better than showing a loading UI.
- Fewer requests to the server. If responses to fetch requests are keyed, there will be only one request for all components fetching the same data.
6. Network waterfall
- Multiple components may re-fetch the same data unnecessarily.
- If the pattern shown in the example is followed in other components in an app tree, this may produce a waterfall effect while rendering.
This can be addressed by creating a custom hook around fetchBios; however, this is a well-explored problem, and multiple libraries have attempted to solve it.
The TanStack Query solution
We recommend using @tanstack/query. TanStack Query provides out-of-the-box solutions to all the above problems. It manages caching, deduplication, retries, error states, and request cancellation automatically.
1. Race condition
TanStack Query is aware of the query’s state. When you trigger a new fetch for a given queryKey, it knows that any in-flight requests for that same key are now outdated. It will simply ignore the results from all except the most recently initiated request. You don’t have to write any extra code.
2. Loading state
useQuery provides flags like isLoading and isFetching to distinguish between initial load and background refetches
isLoading: trueonly on the initial fetch when there is no cached data.isFetching: truewhenever any request is in-flight for that query, including background refetches.
This enables both full-page loaders and subtle refresh indicators.
function UserProfile() {
const { isLoading, isFetching, data } = useQuery({
queryKey: ['userProfile'],
queryFn: () => fetch('/api/user').then(res => res.json()),
});
// Shows a full-page loader on the first load
if (isLoading) {
return <div>Loading your profile...</div>;
}
return (
<div>
<h1>{data.name}</h1>
{/* Shows a subtle indicator during background refetches */}
{isFetching && <span>(Updating...)</span>}
<p>{data.bio}</p>
</div>
);
}
3. Error management
The useQuery hook automatically catches any errors thrown by your queryFn. It provides an isError boolean flag and an error object containing the error details. It also has a built-in, configurable retry mechanism.
import { useQuery } from '@tanstack/react-query';
function Post({ postId }) {
const { data, isError, error, isLoading } = useQuery({
queryKey: ['post', postId],
queryFn: async () => {
const response = await fetch(`/api/posts/${postId}`);
if (!response.ok) {
// This thrown error will be caught by TanStack Query
throw new Error('Post not found!');
}
return response.json();
},
retry: 1, // Will retry a failed request 1 time
});
if (isLoading) {
return 'Loading post...';
}
// If the fetch fails, isError becomes true and `error` is populated
if (isError) {
return <div>Error: {error.message}</div>;
}
return <div>{data.content}</div>;
}
4. Request abortion
TanStack Query passes an AbortSignal to the query function. This cancels in-flight requests automatically when the component unmounts or a query becomes outdated.
import { useQuery } from '@tanstack/react-query';
// Your fetch function should accept the signal
const fetchProjects = async ({ signal }) => {
const res = await fetch('/api/projects', { signal }); // Pass the signal here
return res.json();
};
function ProjectsList() {
// TanStack Query automatically provides the signal to the queryFn
const { data } = useQuery({
queryKey: ['projects'],
queryFn: fetchProjects,
});
/* If this component unmounts while the fetch is in progress,
* the `AbortSignal` will be triggered, and the browser will
* cancel the network request. No manual AbortController needed.
**/
return (/* ... render projects ... */);
}
5. Caching and deduplication
Caching is a core feature. It’s on by default.
- Stale-While-Revalidate: When a component mounts,
useQuerychecks the cache. If cached (stale) data for thatqueryKeyexists, it is shown immediately. Simultaneously, a background fetch is triggered to get fresh data. When the new data arrives, the UI updates seamlessly. This avoids loading spinners on subsequent views. - Request Deduplication: If multiple components on the page use the same
queryKey(e.g., [‘user‘, ‘current‘]), TanStack Query will only make one network request. All components will be subscribed to the result of that single request.
import { useQuery } from '@tanstack/react-query';
const fetchUser = async (id) => fetch(`/api/users/${id}`).then(res => res.json());
// Component 1: User's avatar in the navbar
function UserAvatar({ userId }) {
const { data } = useQuery({ queryKey: ['user', userId], queryFn: () => fetchUser(userId) });
return <img src={data?.avatarUrl} alt={data?.name} />;
}
// Component 2: User's profile on the main page
function UserProfile({ userId }) {
const { data } = useQuery({ queryKey: ['user', userId], queryFn: () => fetchUser(userId) });
return <h1>Welcome, {data?.name}</h1>;
}
// In your App:
function App() {
const userId = '123';
return (
<header><UserAvatar userId={userId} /></header>
<main><UserProfile userId={userId} /></main>
</>
);
}
// Even though `useQuery` is called twice with the same key `['user', '123']`,
// only ONE network request to `/api/users/123` will be made.
Key takeaways
- Don’t fetch with bare
useEffectit leads to bugs and inefficiency. - Use TanStack Query for caching, deduplication, retries, and abort signals.
- Provide clear loading and error states for a better user experience.
- Let queries manage stale data and background updates instead of reinventing patterns.
- Optimize network usage by deduplicating requests across components.
Credits
Sayed Taqui
Author
Sayed Taqui
Author
Seasoned React, JavaScript, and WordPress Developer. Contributed significantly to WordPress Core. Currently serving as the Lead WordPress Engineer at rtCamp. Passionate about crafting innovative so…
Imran Sayed
Author
Imran Sayed
Author
Senior Software Engineer and Full-Stack Web Developer building high-performance, user-centric web applications that drive business growth. Expertise lies in e-commerce development, custom WordPress…
Ayush Nirwal
Author
Ayush Nirwal
Author
Amoghavarsha Kudaligi
Author
Amoghavarsha Kudaligi
Author
Mayank Rana
Author
Mayank Rana
Author
Good Work. Good People.
Industry partnerships
Compliance certifications
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Company
Solutions
Subscribe to our newsletter and get a few email updates every month.
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Cookie Consent
We value your privacy
We use cookies to give you the best possible experience. By clicking “Accept,” you consent to our use of cookies to improve site functionality, analyze usage, and personalize content and communications. Your privacy matters to us, and we are committed to handling your data responsibly and transparently. Please check our Privacy Policy for more details.
Manage PreferencesDon’t AllowAllow All
Why do we use cookies?
×
By clicking "Accept" or "Decline All" at the bottom, you consent to the use of cookies and other tools as described in our Cookie Policy in accordance with your settings and accept our Terms of Service.
Toggle EssentialEssential
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
30 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
Toggle CloudFlareCloudFlare
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
Name
Description
Duration
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
Toggle CommentsComments
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Toggle GodamGodam
GoDAM" is primarily a specialized WordPress plugin and media management service designed to enhance video hosting, marketing, and asset management directly within the WordPress dashboard.
Service URL: godam.io (opens in a new window)
Name
Description
Duration
user_image
Temporarily stores the path to the user's avatar or profile picture for quick rendering in the website header.
session
user_id
Stores the numerical ID of the logged-in user to maintain session continuity and basic site operations.
session
full_name
Stores the logged-in user's display name to personalize the site interface without needing database queries.
session
system_user
First-party cookie used to store basic application state identifying the current system user role.
session
sid
A generic session ID cookie used to maintain user state and functionality as the visitor navigates through the site.
session
Toggle Google reCAPTCHAGoogle reCAPTCHA
Google reCAPTCHA helps protect websites from spam and abuse by verifying user interactions through challenges.
Name
Description
Duration
_GRECAPTCHA
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
179 days
Toggle Google Tag ManagerGoogle Tag Manager
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
cookiePreferences
Registers cookie preferences of a user
2 years
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
Toggle StatisticsStatistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Toggle Factors AIFactors AI
Factors.ai is a B2B account intelligence and marketing analytics platform that helps Go-To-Market (GTM) teams identify anonymous website visitors, track buyer journeys, and measure the ROI of marketing campaigns.
Service URL: www.factors.ai (opens in a new window)
Name
Description
Duration
_fuid
It is sent to capture session details and track user behavior across your website to provide behavioral data and intent signals.
1 Year
Toggle Google AnalyticsGoogle Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
Name
Description
Duration
FPGSID
Stores a session or user identifier to track how visitors interact with a website. This helps Google Analytics measure website performance, user engagement, and usage patterns.
Session
FPLC
Used by Google Analytics to link visitor interactions and sessions across multiple related domains.
20 hours
FPID
A server-side Google Analytics cookie used as an alternative user identifier when third-party cookies are restricted.
2 years
_ga
ID used to identify users
2 years
_ga_
ID used to identify users
2 years
Toggle Jetpack StatsJetpack Stats
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
Service URL: automattic.com (opens in a new window)
Name
Description
Duration
tk_aip
Stores a list of anonymous visitor IDs so they can be merged into one identity once a visitor is recognized.
Up to 5 years
tk_tc
Used once per page load to work out which cookie domain the Tracks library should use, then removed as soon as it's read back.
Session (deleted immediately after use)
tk_qs
Queues analytics events for Jetpack's Tracks library so none are lost if the page closes before they can be sent.
30 minutes
tk_ai
Stores a randomly-generated anonymous visitor ID so Jetpack's Tracks analytics library can link tracking events to the same visitor.
Session in wp-admin; up to 5 years on the frontend
Toggle Microsoft ClarityMicrosoft Clarity
Clarity is a web analytics service that tracks and reports website traffic.
Service URL: clarity.microsoft.com (opens in a new window)
Name
Description
Duration
CLID
Identifies the first-time Clarity saw this user on any site using Clarity.
12 months
ANONCHK
Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0.
Session
_clck
Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID.
12 months
_clsk
Connects multiple page views by a user into a single Clarity session recording.
12 months
Toggle Parse.lyParse.ly
Parse.ly is a content analytics platform that helps publishers optimize audience engagement and content performance.
Name
Description
Duration
cookies.js_dtest
This cookie determines whether the browser accepts cookies.
session
_parsely_session
JSON document storing information identifying a browsing session according to Parsely’s proprietary definition
30 minutes
_parsely_visitor
JSON document uniquely identifying a browser and counting its sessions
13 months
Toggle SalespanelSalespanel
Salespanel is a B2B marketing and sales software that identifies, tracks, and qualifies website visitors and leads in real-time using first-party data. It helps businesses monitor customer journeys, score leads based on behavior, and syncs this data with CRMs (like Pipedrive or HubSpot) to improve conversion rates.
Service URL: salespanel.io (opens in a new window)
Name
Description
Duration
track_uid
Identify and tracking a lead
12 moths
Toggle MarketingMarketing
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Toggle Bing / MicrosoftBing / Microsoft
Bing, powered by Microsoft, is a search engine providing web, image, video, and map search capabilities.
Name
Description
Duration
MR
Used to collect information for analytics purposes.
6 months
ANONCHK
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
10 minutes
SM
Used by Microsoft in synchronizing the MUID across multiple Microsoft domains to track users for advertising.
session
MUID
Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes.
1 year
Toggle DoubleClick/Google MarketingDoubleClick/Google Marketing
A comprehensive digital advertising platform for managing campaigns, optimizing performance, and analyzing audience data.
Name
Description
Duration
IDE
This cookie is used for targeting, analyzing and optimisation of ad campaigns in DoubleClick/Google Marketing Suite
2 years
ar_debug
Store and track conversions
Persistent
Toggle LinkedInLinkedIn
LinkedIn is a professional networking platform for job seekers, employers, and industry connections.
Name
Description
Duration
bscookie
Used by LinkedIn to track the use of embedded services.
1 year
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries
30 days
bcookie
Used by LinkedIn to track the use of embedded services.
1 year
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
90 days
lidc
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
1 day
UserMatchHistory
Used by LinkedIn Ads to synchronize and match user IDs across different ad networks and data providers.
30 days
Toggle LinkedIn InsightLinkedIn Insight
LinkedIn Insight is a web analytics service that tracks and reports website traffic.
Service URL: www.linkedin.com (opens in a new window)
Name
Description
Duration
li_sugr
Used to make a probabilistic match of a user's identity.
90 days
lidc
Used for routing and session management.
24 hours
Toggle LiveIntentLiveIntent
LiveIntent provides a platform for email advertising and identity-driven marketing solutions.
Name
Description
Duration
_lc2_fpi_js
Companion cookie to _lc2_fpi used by JavaScript to facilitate cross-domain ad tracking and user identification.
1 year
_lc2_fpi
First-party tracking cookie usually associated with LiveRamp to identify users across devices for targeted advertising.
1 Year
_li_ss
Sets a unique ID for the visitor, that allows third party advertisers to target the visitor with relevant advertisement. This pairing service is provided by third party advertisement hubs, which facilitates real-time bidding for advertisers.
1 month
lidid
Collects data on visitors' behaviour and interaction - This is used to make advertisement on the website more relevant. The cookie also allows the website to detect any referrals from other websites.
2 years
Toggle Cookie PolicyCookie Policy
You can find more information in our Privacy Policy.
Allow AllDecline All
Accept