Wordpress LScache Plugin: First Contentful Paint (3G) suddenly high
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hello. I suddenly started to get alot of mobile issue warnings from Google Search Console, that i had Content Wider the screen , Elements too close together etc and i didnt notice anything even with testing with three multiple phones. I ran some PageSpeed Insights and Lighthouse tests and noticed Google sees my page very weirdly. Im having amazing PageSpeed scores 100 desktop & +90 on mobile, but im always failing the Core Web Vital Assesments because my First Contentful Paint (3G) is 5000-6000ms It wasnt like that before, i had no problems. I was wondering im getting those errors because Google has no time to wait my site to load and just marks it not mobile friendly. Is there anything to do with litespeed i could do to reduce First Contentful Paint (3G) Google says i should Eliminate render blocking resources /css/ffa7cd08afced98db45897db82041249.css?ver=26045 and /js/jquery/jquery.min.js?ver=3.6.0 also reduce unused css /litespeed/css/ffa7cd08afced98db45897db82041249.css?ver=26045 I have been investigating the issue and saw that, when loading the page on mobile, the main menu or something acts weirdly. Ive had problems before with mobile menus, could this be the reason? Video in link https://drive.google.com/file/d/1ItMOqYNLuOIy40P-wc7VdreiWiP9_GZ-/view Also i made and EMPTY test page and still First Contentful paint over 4000ms. There is picture from GTMterix waterfall report https://ibb.co/DtjJC8G I added this code and yeah the first contentful paint problem went away but now my mobile menu is not working so the problem is something related to that? `add_filter( script_loader_tag, add_async_to_script, 10, 3 ) function add_async_to_script( $tag, $handle, $src ) //You can use this to make all async $tag = str_replace( src, async src, $tag ) ` Removed that and added this and the problem is fixed but could this cause some problems in site? dont async JQ , many js relies on it , it will break something
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference