-
-
Notifications
You must be signed in to change notification settings - Fork 593
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
Preview Image does not use HTTPS #4911
Comments
@cihanandac If the page doesn't have a preview image then you shouldn't render . I hope this will help you to fix issue |
Thanks, @manoharkumarsingh. Didn't help to solve it, but I understand your point. |
@cihanandac You should always use |
Thanks for the tip @avoinea. This component is also using Image Block, thus it is utilizing |
Thank you so much again @avoinea. Looks like you are right. I don't even know how I missed this one 🤦 . |
Describe the bug
While testing the website I am working on with PageSpeed Insights, I realized that the pages that use preview images are getting this warning: "Does not use HTTPS". It is dropping the score for the 'Best Practices'. If the page doesn't have a preview image shown on it, then it does not have this issue.
Link for the webpage: https://rietveldschroderhuis.intk.com/nl/over/centraal-museum-rietveld
Link for the PageSpeed test: https://pagespeed.web.dev/analysis/https-rietveldschroderhuis-intk-com-nl-over-centraal-museum-rietveld/l1bq5otzia?form_factor=desktop
Link to repo (line 72) : https://github.com/cihanandac/new-RietveldSchroderhuisWebsite/blob/main/frontend/src/components/theme/Header/HeroSection.jsx
The preview image is called with the following code:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Doesn't have "Does not use HTTPS" warning and has a better score in best practices.
Screenshots
![Screenshot 2023-06-23 at 13 45 19](https://private-user-images.githubusercontent.com/67173940/248259119-563d97ad-b4f5-41b3-b418-39805efee8e7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE2NDEwNTUsIm5iZiI6MTcyMTY0MDc1NSwicGF0aCI6Ii82NzE3Mzk0MC8yNDgyNTkxMTktNTYzZDk3YWQtYjRmNS00MWIzLWI0MTgtMzk4MDVlZmVlOGU3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzIyVDA5MzIzNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc4MjE2MTkyZjE5MDcxYzk5OWNmNDc4NTZjNmYzYzBlOTdkYjY5MjgzY2JjYWFlYjkzYTI3OGQ2MzhlNjM2NDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.aAbgUk6FdvUfIgZqgvdMx_AWa3EaLJu2oLgF6gGPqrY)
Software (please complete the following information):
The text was updated successfully, but these errors were encountered: