Yes, I had to look into the webflow.css to see which class was using that font.
I then changed the font to another one, it solved my issue.
Weird however that lato was still accessible from the designer and was not present on the font settings of the website… if i kill a font from the settings, i would have expected it got killed and therefore not available anymore from the designer ?
I can see where the Webflow publishing engine would have to make a decision between publishing with a broken font, and embedding the font, but yeah that’s a little unexpected.