perf: Code-split slug-specific sections from ExpertisePageClient#110
Merged
vibemarketerpromax merged 1 commit intomainfrom Feb 20, 2026
Merged
perf: Code-split slug-specific sections from ExpertisePageClient#110vibemarketerpromax merged 1 commit intomainfrom
vibemarketerpromax merged 1 commit intomainfrom
Conversation
Extract ~1,860 lines of inline slug-specific JSX from ExpertisePageClient.tsx into 6 dynamically-imported data-driven components under slug-sections/: - WhySection.tsx: "Why Teams Choose X" (prometheus/istio/thanos) - DecisionFramework.tsx: Decision frameworks (prometheus/istio/thanos) - TechDecisionTable.tsx: "Is X Right?" tables (nodejs/react/python/angular/flutter/react-native) - FrameworkComparison.tsx: "X vs Y" comparisons (react/python/flutter/react-native) - CustomStackTable.tsx: Stack tables for all 9 slugs - DotnetSections.tsx: Specialized services + industries (dotnet) Also converts 14 below-fold shared components (CapabilitiesGrid, WhyProcedure, TechStack, FAQSection, etc.) to next/dynamic imports. This reduces the initial JS bundle for each expertise page since only the matching slug's chunk downloads, and below-fold component hydration is deferred. Target: TBT < 200ms (from 480ms).
Deploying website with
|
| Latest commit: |
09c7b8c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f70cc9a8.website-yiq.pages.dev |
| Branch Preview URL: | https://perf-reduce-tbt-expertise-pa.website-yiq.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ExpertisePageClient.tsxinto 6 dynamically-imported data-driven components underslug-sections/CapabilitiesGrid,WhyProcedure,TechStack,FAQSection, etc.) tonext/dynamicimportsExpertisePageClient.tsxfrom 2,573 lines to 757 linesNew slug-section components
WhySectionDecisionFrameworkTechDecisionTableFrameworkComparisonCustomStackTableDotnetSectionsPerformance impact
Each expertise page now only downloads its matching slug's chunk instead of all slug-specific code. Below-fold component hydration is deferred via dynamic imports. Target: TBT < 200ms (from 480ms), LCP < 2.5s.
Test plan
/technologies/reactrenders all sections correctly (capabilities, stack table, "Is React Right?", "React vs" comparison, FAQ, etc.)/services/prometheus-monitoringrenders WhySection + DecisionFramework + custom stack table/services/istio-consultingand/services/thanos-long-term-storagesimilarly/technologies/dotnetrenders specialized services + industries sections/technologies/react— target Performance 90+