![]() There are services to generate a critical path css. Since you also need to defer scripts, that means it will only finish after everything else. With a slider above the fold, that content only finishes after all scripts execute. LCP won’t happen until at least jquery and revolution slider scripts finish downloading and executing. ![]() Just using revolution slider for example, can decrease your mobile scores by 50+ points on pagespeed insights, and I can 99% guarantee, that no amount of deferring css and adding critical path css is going to fix it. If you have a high FCP, LCP or CLS… it’s most likely because of how you designed the site, not a matter of optimization. With FVM adding a preload header, followed by a render blocking css file served from a good cdn (with brotli 11 precompression for example), your styles will load without render blocking, or within a few ms. If your css is small, then there is an option to inline it as well, so there is no render blocking. The benefit of using critical path css is negligible, if you have a normal css file and your content above the fold doesn’t require javascript to render. In those cases, you could generate the critical path css, and if you were to remove all scripts and css files from the page, the content above the fold, would need to look exactly like if you never removed the css and js files… that is what critical path css is.īut critical path, varies on screen size… it’s not something you generate and reuse for all screens and sizes, or for all pages. The critical path css would be useful only, if your site has nothing made with javascript above the fold and if you had a very large css file. If you use a slider plugin that requires js to render it, the critical path will not help the FCP in any way, since it only happens after JavaScript finishes loading. It’s not only about generating and adding the critical path… it depends on what you have above the fold. ![]() I don’t think you understand what is involved on rendering the Critical path css. Nevertheless, loading css first and js later is already what FVM is doing, so there is nothing new on that post, other than the critical path css. You can reduce all metrics by having a fast time to first byte and using a fast cdn.Ī cache plugin may help, but it’s ultimately the response time of your server. FCP metrics depend on what you put above the fold, it’s not something you can optimize with PHP. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |