-
Notifications
You must be signed in to change notification settings - Fork 187
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
Add custom image loader for BigCommerce CDN #574
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
9 Ignored Deployments
|
9ca0de7
to
b8df75e
Compare
This makes lighthouse worse because some of the CDN optimizations aren't working correctly. Looking into that... |
b8df75e
to
996cbe4
Compare
996cbe4
to
c402bdb
Compare
c402bdb
to
777633e
Compare
777633e
to
78407f7
Compare
78407f7
to
bc63567
Compare
bc63567
to
5dc4dc9
Compare
|
5dc4dc9
to
ed97789
Compare
ed97789
to
2e544ad
Compare
6899c07
to
e211221
Compare
e211221
to
3e73d6c
Compare
4bfdfee
to
1e8963d
Compare
1e8963d
to
560b4fd
Compare
4ef72ed
to
4236558
Compare
4236558
to
f372df2
Compare
f372df2
to
03f3dc6
Compare
c6bc97c
to
9aea253
Compare
9aea253
to
3794c13
Compare
3794c13
to
d35218c
Compare
⚡️🏠 Lighthouse reportWe ran Lighthouse against the changes and produced this report. Here's the summary:
Lighthouse ran against https://catalyst-latest-nm78m4n8e-bigcommerce-platform.vercel.app/ |
Closing in favor of #701 |
What/Why?
Adds a custom image loader to use images directly from the BigCommerce CDN
This allows for more optimal image loading and is a more generic solution that should work across hosts, and prevent wasteful double-processing of images by stacking CDNs.
Testing
Ensured images are coming from BC CDN where relevant, and other URLs are not interfered with: