I’d like to know if anyone’s figured out how to solve performance errors from the “Lightroom” extension review (see attached images | Lighthouse 01/02).
You have the option to do a mobile and desktop review and in the desktop one the score is 90+, but somehow the mobile one appears to be terrible.
On top there are 9 untagged tags, does anyone know or got a video on how can I quickly solve these errors (see attached image | Google Tag Manager 01)
In terms of loading time penalties, Lighthouse/Pagespeed is extremely outdated; many websites from even Google self score horrible, especially on mobile.
I’d recommend using it more as a tool to check for issues like contrast mismatch and labels (for example).
@Joshua24 - Concentrate on passing Core Web Vitals as that is what matters. Lighthouse is good for drilling into things to fix and debugging. Performance tuning is nottrivial and there are things you can’t modify on Webflow sites. This forum has plenty of posts and recommendations on the subject. Just understand that everything is site specific and based on choices you make.
It is possible to do. The biggest issue would be the largest contentful. Fixing that load time for that one item will take care of enough to score where you want to. This was done on my own site on mobile setting. If you haven’t already, compress images into AVIF files or use SVG’s if possible. Every kb adds up.
You can convert into AVIF files directly inside of Webflow now (it is a recent addition). Go into your images (Assets) and click the arrow to expand
Then click on the checkmark of each image you wish to compress:
Then just click on Compress:
This will happen behind the scenes and you won’t have to take the time to swap out the image after it updates. So you can bulk update them and the entire site will be repointed to the proper image once it is compressed. Side note: If you are using any PNG’s for transparency purposes DO NOT compress them. They will lose the transparency.
As for updating the Core Web Vitals, a lot of it is tiny details of cleaning up CSS like making sure that “minify” is selected for both CSS and JavaScript in the Site Settings area when you go to Publish. Any CSS/Js that you are not using should be cleaned up inside the style selector, too. The Style Selector will only go through the CSS, you will have to go through your Animations to remove any Js that you are not actively using.
Some of it just can’t be fixed as it is part of Webflow itself. But believe me, from going through sites like this, Webflow is a lot easier on these speeds than I have seen from other Visual Builders.
Thank you so much. So the images which are high resolution are all cms and not included in the default images tab, is there also a way, so I don’t have to single swap the 36 images included in our cms?
I will eventually give you a feedback on the Large Layout Shift things in the next few days. Thanks again.
When they are in the CMS like that, there’s no quick way to do it, sadly. It’s all the long way. I’ve found Webflow is ‘faster’ to compress images, so I toss them into the Assets, open them back up in a separate browser tab and download them to desktop and then load them into the CMS. But I’ve not personally seen a faster way, I’d love to know it if someone knows it.
There is lots of high quality content on the subject and it requires a significant investment in learning. I suggest you start here → Core Web Vitals | web.dev
@Joshua24 - Core Web Vitals is the third most important thing you can do. Yes it is important but you need traffic to have field data. Lighthouse is the test tool.
The quick answer is Yes and No. Yes, because every kb saved speeds up the site. No, because it DOES run smoothly. However, if the person is actively on a mobile network and not wifi, if they have a poor connection, then those kb’s are important. It’s more of an “every eventuality” versus a “perfect situation”. When in development we look at the perfect situation. Nothing survives contact with the end user.
It’s an old adage from war. Something along the lines of “Plans never survive contact with the enemy.” Like when you foolproof something someone builds a better fool. Make it as best you can, but there will sometimes be things that the live action version will test you on that you didn’t realize was possible. I live test my site on a separate browser and on my cell when I am building. Somethings just do not look the same even if they should.
