Findify aims to provide the very best experience for the end user in the ecommerce segment.
In order to achieve this, Findify enables websites to show content as fast as possible which reduces waiting time for the users - even on mobile devices with bad internet connection.
Findify cannot, however, influence any of the other 3rd party apps installed on the store front. As Findify is delivering critical content to the page, it is up to the merchant to make sure that Findify scripts are loading first on their site, without being blocked by other scripts.
This metric is most sensitive on the mobile devices. Google calculates time between first asset request time and the last critical (or large) piece of content in the viewport loaded before the user interacts with the screen.
To reduce this time we have to load visible content as fast as possible and not modify content on the screen before the user touches it.
This metric is about how fast your server returns the data. Most store platforms already have CDN and Cache strategies that make your website load content fast. But the 3rd party apps are usually hosted on other domains requiring additional steps (DNS-resolve) to fetch the content.
Findify strongly recommend to add dns-prefetch tags in the HEAD section to resolve DNS lookup as fast as possible and not spend time on it when content will be required.
<link rel="preconnect" href="https://cdn.jsdelivr.net" crossorigin> <link rel="preconnect" href="https://api-v3.findify.io" crossorigin>
Following best UX practices, Google asks developers to not extend page layout before the user has interacted with it. To follow this guidance, we created a placeholder generator that allows for the creation of SVG placeholders with the same size as the real content of the search results or smart collections. The Placeholder will extend window height to the size needed for real content and reduce CLS number accordingly.
Updated 9 months ago