Improving Core Web Vitals: Tips for Faster Mobile Performance | Reploverse

Improving Core Web Vitals: Tips for Faster Mobile Performance

Hey, need help with core web vitals. My client is failing INP in core web vitals and from my audit, it looks like the Replo tabs and sliders are responding very slowly on mobile. Any tips on how to make it fast?

4 comments

Steve S.
·
·
Oh this is interesting. We very rarely (read never) deal with INP (had to look it up) so this is new. For the thread INP is Interaction to Next Paint: https://www.debugbear.com/docs/metrics/interaction-to-next-paint No immediate ways to make this faster to my knowledge. Do you mind sharing a bit more context here? I think a handful of questions I'd have are:
Can you link us to the live page or a preview page you're using to test INP?
How are you actually testing INP (so we can develop a baseline here)?
Is this INP having a big effect on your Core Web Vitals? Is there some CWV dashboard you can share to help us look at this more?
Maria
·
·
You can have a look at this page I'm testing: https://advtennis.pro Only INP fails on mobile. The rest of the Core web vitals pass. I'm not too obsessed with these metrics and I know these tend to draw people towards a rabbit hole of optimizations that often don't have any significant advantage on conversions and sales. However, if you browse this page on mobile and interact with the tabbed widgets on this page, you'll notice the slowness. The tabs take 1+ second to respond. Plus, if you add a product to cart, it takes around 2 seconds to open the mini cart
Steve S.
·
·
Hmmm really? When I interact with both of the "See our players" sections (the only ones with tabs blocks in them), these respond pretty quick for me. It's not lightning fast but well within the realm of what I'd expect from an ecommerce website. Are you able to send a video of the slow interaction speed? I'm on a semi-new iPhone 15 Plus, are you using an older device by chance? As for the 2 seconds for the mini-cart, I also experience it within ~1 second which is reasonable. One thing you could do is add in a Loading State to the buttons to give the user some indication that their click worked. Finally, likely you've seen this but some good tips in our Page Speed doc
Maria
·
·
hm, it could be a device issue then. here is the core web vitals report. i'll advise my client to ignore it for now