Slow FCP (first contentful paint) of 0.5s #5597
Replies: 4 comments 1 reply
-
Similarly interested here. I ran into this with an app with several routes and I thought it was all of the routes loaders running in parallel blocking but with a fresh app I see the same thing. After the first load, the site is blazing fast but that first load before anything is cached seems to start with a FCP of ~0.5s and once I add some other code to the root loader it starts to range from 0.6s to 0.9s. So far I've been testing on Vercel and will test elsewhere but is there some best practices for improving FCP of an index/root page at least? |
Beta Was this translation helpful? Give feedback.
-
+1 also interested in that. I followed the official Remix tutorial and ran lighthouse after the last step. FCP was ~2s for mobile, 0.5s for desktop |
Beta Was this translation helpful? Give feedback.
-
Any news on this? Can't sleep well without reaching the 100 performance points on lighthouse 🤡 |
Beta Was this translation helpful? Give feedback.
-
Same here: ~65 performance on lighthouse. A simple website 2-3 links 2 toggles. |
Beta Was this translation helpful? Give feedback.
-
I just bootstrapped an empty remix project (without any template) & used the App server. Built in production mode & served locally from my (very fast) PC, lighthouse reports a FCP of 0.5s. Next.js reaches 0.2s even in dev mode. Is this normal? Can I somehow improve that?
Beta Was this translation helpful? Give feedback.
All reactions