Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changed Slick Carousel lazyLoad technique to Progressive. #1259

Closed
wants to merge 1 commit into from
Closed

Changed Slick Carousel lazyLoad technique to Progressive. #1259

wants to merge 1 commit into from

Conversation

Ubersmake
Copy link
Contributor

What?

Cornerstone has an issue where the first image in a carousel appears to reload on wrap. This "reload" happens despite the browser not making any new GETs.

This behavior is fixed by changing the Slick Carousel's lazy load technique from "ondemand" to "progressive". Note that this does technically make page performance worse, since progressive will attempt to load all images on the carousel at once instead of when a slide scrolls.

Tickets / Documentation

Screenshots and Reports

Reports were done on a test store. These stores are light, with very few products and zero customizations. The margin in performance should be significantly wider on a live store.

These reports were generated by Lighthouse and can be viewed in a human-readable form at https://googlechrome.github.io/lighthouse/viewer2x/.

Before: ondemand

ondemand

ondemand.txt

After: progressive

progressive

progressive.txt

@bigbot
Copy link

bigbot commented Jun 7, 2018

Autotagging @bigcommerce/storefront-team @davidchin

@Ubersmake Ubersmake closed this Jun 8, 2018
@Ubersmake Ubersmake deleted the slick-lazyload-progressive branch June 8, 2018 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants