Skeleton loader renders even when requests are not running and data is cached

Wized
1

On a product page using Wized session variables for caching, the skeleton loader is rendered even when:

  • isRequesting for all related requests is false

  • product data is already available in session variables

  • requests are conditionally skipped due to cache match

Despite guarding the skeleton with isRequesting checks and cache comparisons, the skeleton still appears on page load.

This results in the skeleton being visible even though no network request is in progress and valid cached data exists.
read only link : Wized
Path: go to any product from the home page, or go straight to /product with parameter id -3 )

2

Hello,

Thank you for sharing your project link and from the setup, all is done well. The reason why it still shows the loader is because there is some time needed to load the Wized runtime itself to also check for the variable.

By default - your page from the server is fetched with the loader UI and no product data in place since this is managed by Wized. The runtime for wized also needs some time to load, this happens after the page fetch after the runtime loads the logic to show or remove the loader is then executed. This slight time between is what makes you observe the skeleton loader

1 Like