Optimizing Performance by Caching Critical CSS #168
Conversation
This file contains 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.
Caching CSS Based on a Data-Attribute (e.g., data-pagetype)
To enable this feature, first pass a key in the options:
cacheCriticalCSS: true.Next, add a class named page_layout_nxt to any
<div>in the HTML and provide a data attribute (e.g., data-pagetype). This data attribute can be any unique key based on a combination of page name, user logged in status, and device type (mobile/desktop).Critical CSS is then saved in the cache and returned from the cache instead of being recalculated for the same unique key. This will improve the Time to First Byte (TTFB).
Related Issue:
This pull request closes #169