Optimize site performance via Lighthouse audits#812
Merged
Conversation
✅ Deploy Preview for ucmacm ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No767
marked this pull request as ready for review
July 17, 2026 12:39
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
Ensure that the site is well-optimized and performing smoothly by using Lighthouse to audit performance and components of a11y, best praactices, and SEO. Notably:
EventsCalendarcomponent has been split up to be loaded lazily instead. This aids in not putting the full paint logic in first, so it improves our FCP and LCP scores. Also, generally should make the site feel more smoother. As a bonus, this also dedupes some code as wellvendor-base-uiwas removed due to it manually chunking and causing unesscary Base UI components to be loaded. This caused unesscary code to be included. Now Rolldown will handle them based on where they are needed, which is the intended purpose. Although this will increase build times, that's fine because Rolldown has to do the calcuations anyways so it really doesn't matter.Although the lighthouse auditing tools are omitted in this PR, at some point I would like to introduce a proper lighthouse auditing system for this site, alongside with a proper CI flow to aid in scores.
As a side note, I don't know why Sonarcloud is reporting a duplication rate of 13.3% for this PR
Types of changes
What types of changes does your code introduce to the UC Merced's ACM Chapter Website?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply