Resolver for pre-fetching data in Angular - Performance & Optimization

Performance: Resolver for pre-fetching data

MEDIUM IMPACT

This affects the page load speed by delaying route activation until data is ready, improving perceived load but potentially increasing initial wait time.

Pre-fetching data before route activation to avoid loading spinners inside components

Angular

export const dataResolver = () => {
  const dataService = inject(DataService);
  const route = inject(ActivatedRouteSnapshot);
  return dataService.getData(route.params['id']);
};

const routes = [
  {
    path: 'item/:id',
    component: ItemComponent,
    resolve: { itemData: dataResolver }
  }
];

Data is fetched before route activation, so component renders with data immediately, reducing layout shifts and improving LCP.

📈 Performance GainSingle render with data present, reducing reflows and improving perceived load speed.

Pre-fetching data before route activation to avoid loading spinners inside components

Angular

this.route.params.subscribe(params => {
  this.dataService.getData(params['id']).subscribe(data => {
    this.data = data;
  });
});

Data loads inside the component after route activation, causing delayed content rendering and possible layout shifts.

📉 Performance CostTriggers multiple reflows as content updates after initial paint, increasing LCP and CLS.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Data fetched inside component after route loads	Multiple DOM updates as data arrives	Multiple reflows triggered	Multiple paints increasing load time	[X] Bad
Data fetched in resolver before route activation	Single DOM update with data ready	Single reflow on initial render	Single paint with stable layout	[OK] Good

Rendering Pipeline

The resolver fetches data before Angular activates the route, so the browser paints the component with data already present, avoiding multiple layout recalculations.

→JavaScript Execution

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Execution waiting for data fetch delays initial paint.

Core Web Vital Affected

LCP

This affects the page load speed by delaying route activation until data is ready, improving perceived load but potentially increasing initial wait time.

Optimization Tips

1Use resolvers to fetch data before route activation to improve LCP.

2Avoid fetching data inside components to reduce layout shifts and reflows.

3Keep resolver data fetching fast and lightweight to minimize initial load delay.

Performance Quiz - 3 Questions

How does using a resolver for data fetching affect Largest Contentful Paint (LCP)?

A It has no effect on LCP.

B It improves LCP by ensuring data is ready before rendering.

C It worsens LCP by delaying route activation unnecessarily.

D It causes layout shifts after initial paint.

DevTools: Performance

How to check: Record a performance profile while navigating to the route. Look for scripting time and paint events related to data fetching and rendering.

What to look for: Check if the main content paints once with data or if multiple paints and layout shifts occur after initial load.

Practice

1. What is the main purpose of a Resolver in Angular routing?

easy

A. To handle user authentication during navigation

B. To fetch data before the route loads so the page shows complete information

C. To define the layout of the page components

D. To manage CSS styles for routed components

Solution

1. Step 1: Understand Resolver role

   Resolvers are designed to fetch data before a route activates, ensuring the page has all needed data upfront.

2. Step 2: Compare options

   Only To fetch data before the route loads so the page shows complete information describes this pre-fetching behavior. Other options describe unrelated tasks.

3. Final Answer:

   To fetch data before the route loads so the page shows complete information -> Option B

4. Quick Check:

   Resolver purpose = pre-fetch data [OK]

Hint: Resolvers fetch data before route loads to avoid empty pages [OK]

Common Mistakes:

• Confusing resolvers with guards for authentication
• Thinking resolvers manage styles or layouts
• Assuming resolvers run after the component loads

2. Which syntax correctly defines a Resolver service in Angular?

easy

A. export class DataResolver implements Resolve { resolve(): Data { return this.service.getData(); } }

B. export class DataResolver { fetch(route: ActivatedRouteSnapshot): Data { return this.service.getData(); } }

C. export class DataResolver implements Resolve<Data> { resolve(route: ActivatedRouteSnapshot): Observable<Data> { return this.service.getData(); } }

D. export class DataResolver implements Resolve<Data> { getData(route: ActivatedRouteSnapshot): Data { return this.service.getData(); } }

Solution

1. Step 1: Check Resolver interface implementation

   The Resolver must implement Resolve<T> and define a resolve method with route parameter returning Observable or Promise.

2. Step 2: Validate method signature

   export class DataResolver implements Resolve<Data> { resolve(route: ActivatedRouteSnapshot): Observable<Data> { return this.service.getData(); } } correctly implements Resolve<Data> with resolve(route: ActivatedRouteSnapshot): Observable<Data>. Others miss interface, method name, or return type.

3. Final Answer:

   export class DataResolver implements Resolve<Data> { resolve(route: ActivatedRouteSnapshot): Observable<Data> { return this.service.getData(); } } -> Option C

4. Quick Check:

   Resolver syntax = implements Resolve<T> + resolve() [OK]

Hint: Resolver must implement Resolve<T> and have resolve(route) method [OK]

Common Mistakes:

• Missing the Resolve interface implementation
• Using wrong method name instead of resolve
• Returning data directly instead of Observable or Promise

3. Given this resolver code snippet, what will be the resolved data type when navigating to the route?

export class UserResolver implements Resolve<User> {
  constructor(private userService: UserService) {}
  resolve(route: ActivatedRouteSnapshot): Observable<User> {
    const id = route.paramMap.get('id')!;
    return this.userService.getUserById(id);
  }
}

medium

A. A Promise resolving to a User ID string

B. A plain string representing the user ID

C. An array of User objects

D. A User object wrapped in an Observable

Solution

1. Step 1: Analyze resolve method return type

   The resolve method returns this.userService.getUserById(id), which returns Observable<User> as per signature.

2. Step 2: Understand data type returned

   The resolved data is a User object wrapped inside an Observable, not a string or array.

3. Final Answer:

   A User object wrapped in an Observable -> Option D

4. Quick Check:

   Resolver returns Observable<User> [OK]

Hint: Resolver returns Observable of the specified data type [OK]

Common Mistakes:

• Confusing the route param with resolved data
• Assuming it returns a Promise or plain value
• Thinking it returns an array instead of single object

4. Identify the error in this resolver code:

export class ProductResolver implements Resolve<Product> {
  constructor(private productService: ProductService) {}
  resolve(route: ActivatedRouteSnapshot): Product {
    const id = route.paramMap.get('id')!;
    this.productService.getProduct(id).subscribe(product => {
      return product;
    });
  }
}

medium

A. The resolve method returns void instead of Product or Observable<Product>

B. The subscribe method is missing a callback function

C. The constructor is missing dependency injection

D. The route parameter 'id' is not accessed correctly

Solution

1. Step 1: Check resolve method return type

   The resolve method declares it returns Product but actually returns nothing because subscribe is asynchronous and returns void.

2. Step 2: Understand correct return for resolver

   Resolvers must return Observable<Product> or Promise<Product>, not void. Using subscribe inside resolve breaks this contract.

3. Final Answer:

   The resolve method returns void instead of Product or Observable<Product> -> Option A

4. Quick Check:

   Resolvers must return Observable or Promise, not void [OK]

Hint: Never subscribe inside resolve; return Observable or Promise directly [OK]

Common Mistakes:

• Using subscribe inside resolve instead of returning Observable
• Returning wrong data type from resolve
• Ignoring asynchronous nature of data fetching

5. You want to pre-fetch user profile and user settings before loading a route. How can you combine two resolvers to achieve this in Angular?

hard

A. Use multiple resolvers in the route config with different keys, then access both in the component

B. Create one resolver that calls both services and merges data into one object

C. Call one resolver inside another resolver's resolve method

D. Use a guard to fetch data instead of resolvers

Solution

1. Step 1: Understand Angular route resolver configuration

   Angular allows multiple resolvers in route config by assigning each resolver to a unique key in the 'resolve' object.

2. Step 2: Access resolved data in component

   The component can then access both resolved data objects via ActivatedRoute's data property using the keys.

3. Step 3: Evaluate other options

   Create one resolver that calls both services and merges data into one object is possible but less modular. Call one resolver inside another resolver's resolve method is not standard practice. Use a guard to fetch data instead of resolvers uses guards, which are not for data pre-fetching.

4. Final Answer:

   Use multiple resolvers in the route config with different keys, then access both in the component -> Option A

5. Quick Check:

   Multiple resolvers = multiple keys in route config [OK]

Hint: Assign multiple resolvers with keys in route config [OK]

Common Mistakes:

• Trying to chain resolvers inside each other
• Merging data manually instead of using multiple resolvers
• Using guards instead of resolvers for data fetching