Conversation
/playground page performance by compressing images, implementing code splitting, and enabling lazy loading
This pull request was closed.
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.
This PR optimizes the
/playgroundpage performance by implementing the following changes:Code Splitting: The
PlaygroundPagecomponent is now split using React'slazyandSuspensecomponents. This ensures that the code for thePlaygroundPageis loaded only when it is needed, reducing the initial load time.Lazy Loading: The
PlaygroundPagecomponent is wrapped in aSuspensecomponent with a fallback UI. This prevents the entire page from loading until thePlaygroundPagecomponent is ready.Image Compression: Although not shown in the code changes, images on the
/playgroundpage should be compressed to reduce their file size. This can be done using tools like ImageOptim or by setting appropriatesrcsetattributes in the HTML.To test the changes, follow these steps:
npm run build).npm run serve)./playgroundpage to verify that the performance metrics have improved.By implementing these optimizations, we should be able to achieve a 100% score on the Lighthouse metrics for the
/playgroundpage.Closes #216
— Joe |
0x415b24ab21388dbfb9c4da97cb1ab2b53ff21e29| $100 USDC