perf: optimize application loading and workflows#109
Merged
Conversation
AussieScorcher
force-pushed
the
perf/optimization
branch
from
July 18, 2026 18:42
a25e08f to
b6db527
Compare
AussieScorcher
force-pushed
the
perf/optimization
branch
from
July 18, 2026 18:59
b6db527 to
26795eb
Compare
AussieScorcher
marked this pull request as ready for review
July 18, 2026 19:05
Contributor
|
Too many files changed for review. ( Bypass the limit by tagging |
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
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
Improves perceived and measured frontend performance across navigation, public pages, contribution tools, the draft generator, and staff workflows. It also adds repeatable profiling/React diagnostics and documents the product design principles guiding the interface work.
Changes Made
Additional Information
The main performance issues were whole-page Suspense transitions, repeated route loading, mirrored UI state, controlled high-frequency map state, and legacy modules that increased maintenance and bundle surface.
User impact: navigation keeps the application shell stable, loading states better match destination content, interactive workflows do less avoidable work, and administrative screens are more consistent and accessible.
Validation:
npm run lintnpm run test— 63 tests passednpm run buildbunx react-doctor@latest --verbose --scope changed— no issues foundThe production build succeeds with advisory warnings for chunks larger than 500 kB.
Author Information
Discord Username:
VATSIM CID:
Checklist: