You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run my site (using Live Content API and <SanityLive> etc) on Pagespeed Insights, I see the warning below for both desktop and mobile: errors logged to the console and attributed to next-loader:live (not sure but I assumed it was coming from the new Live Content API methods.
To Reproduce
Run pagespeed insights for my actual site and a demo site (much smaller) and navigate to the Best Practices tab.
Expected behavior
This warning was not logged prior to the Live Content API updates, and my site was able to achieve perfect 100/100s for Best Practices 💯
Which versions of Sanity are you using?
@sanity/cli (global) 3.63.0 (up to date)
@sanity/code-input 4.1.4 (up to date)
@sanity/dashboard 4.1.0 (up to date)
@sanity/eslint-config-studio 4.0.0 (up to date)
@sanity/image-url 1.1.0 (up to date)
@sanity/preview-url-secret 2.0.2 (up to date)
@sanity/vision 3.63.0 (up to date)
sanity 3.63.0 (up to date)
What operating system are you using?
macOS
Which versions of Node.js / npm are you running?
9.8.1
v18.18.2
Security issue?
Not sure if related, but also saw this warning just below the warning in question:
The text was updated successfully, but these errors were encountered:
Describe the bug
When I run my site (using Live Content API and
<SanityLive>
etc) on Pagespeed Insights, I see the warning below for both desktop and mobile: errors logged to the console and attributed tonext-loader:live
(not sure but I assumed it was coming from the new Live Content API methods.To Reproduce
Run pagespeed insights for my actual site and a demo site (much smaller) and navigate to the Best Practices tab.
Expected behavior
This warning was not logged prior to the Live Content API updates, and my site was able to achieve perfect 100/100s for Best Practices 💯
Which versions of Sanity are you using?
What operating system are you using?
macOS
Which versions of Node.js / npm are you running?
Security issue?
Not sure if related, but also saw this warning just below the warning in question:
The text was updated successfully, but these errors were encountered: