Disable Link prefetch for profile and post pages

Summary

  • Add prefetch={false} to Link components that navigate to profile and post pages
  • Prevents excessive API calls caused by Next.js viewport-triggered prefetching

Problem

Next.js <Link> components with default prefetch={true} trigger SSR of target pages when links enter the viewport. This causes massive API call amplification:

Prefetch Target API Calls per Target Total for 20 Posts
Profile pages (/@author) 4 calls 80 calls
Post pages (/category/@author/permlink) 3-5 calls 60-100 calls
TOTAL 140-180 API calls

One user viewing one page = 140-180 API requests to Hive blockchain nodes and third-party services.

Solution

Add prefetch={false} to all profile and post links in post list components.

SEO Impact

None. Search engine crawlers don't execute client-side JavaScript prefetching - they follow <a href> links directly. The links remain fully crawlable.

UX Impact

Minimal. Users will see standard loading state (~200-500ms) when clicking profile/post links instead of instant navigation. This is standard web behavior.

Files Changed

  • apps/blog/features/list-of-posts/post-list-item.tsx
  • apps/blog/features/list-of-posts/summary.tsx
  • apps/blog/features/post-rendering/user-info.tsx
  • apps/blog/features/suggestions-posts/card.tsx

Test plan

  • Verify profile links still work
  • Verify post links still work
  • Monitor API call volume reduction in production

Merge request reports

Loading