3 ms·
This isn't as awesome as it sounds. When inlining everything there is no control over the prioritization of resources. Large files like images can block the ren
by megaman821 12y ago
This isn't as awesome as it sounds. When inlining everything there is no control over the prioritization of resources. Large files like images can block the rendering of your layout giving the appearance of being slow even if the overall download time is less. HTTP2 has stream prioritization to solve this problem and is much more cache friendly.
- spankalee 12y agoIf I recall, only very small images are inlined as data URLs, and other are either sprited or left alone. There's a lot of control over these optimizations.
- aliakhtar 12y ago> When inlining everything there is no control over the prioritization of resources. You can use split points to divide up your code, only the resources in a given split point are loaded. Example: If the user is viewing your 'Sign up' page, then only the resources for the 'Sign up' page will be loaded. > Large files like images can block the rendering of your layout Only small to medium files are inlined. Large files are downloaded as usual.