Poor INP google metric on some components #2981
mkrystkowicz
started this conversation in
Feedback
Replies: 1 comment
-
UPDATE: It looks like the size of rendered list for example in Autocomplete component matters, with 72 elements in list I get 272ms response, for 6 elements in list it already 120ms |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey, I've got notified by google that some mobile users are struggling with poor responsiveness on slow mobiles (INP metric). Have someone met this problem as well? I've done short investigation and have assumptions that it might be caused by Popover component, the problem exist in components that use Popover component inside.
https://pagespeed.web.dev/analysis/https-nextui-org-docs-components-divider/wdoryzxc3g?form_factor=mobile
https://pagespeed.web.dev/analysis/https-nextui-org-docs-components-dropdown/p76chix62f?form_factor=mobile
https://pagespeed.web.dev/analysis/https-nextui-org-docs-components-select/rj3xu4vt5j?form_factor=mobile
https://pagespeed.web.dev/analysis/https-nextui-org-docs-components-tabs/uedr6ogoki?form_factor=mobile
Even in docs these values are huge. As I know this metric impacts SEO. My question is - are there any plans on fixing that? Is it known issue? How can we deal with that, any walk-arounds?
Beta Was this translation helpful? Give feedback.
All reactions