Based on my testing of Figma Sites, I found that its support for SEO tags like H1-H6 and P is still limited. While users can assign these attributes, the code generated treats them as plain "Text" elements. Moreover, I noticed an issue with duplicate H1-H6 tags, appearing up to three times. This seems to be caused by the system counting tags separately for desktop, tablet, and mobile views. Disabling tags on tablet and mobile helps maintain the correct structure. In terms of Page Speed, Figma Sites performs well for simple websites. However, for more complex projects, performance can significantly decline, requiring additional tuning. Despite its WYSIWYG (What You See Is What You Get) interface—similar to Webflow—it lacks the ability to instantly convert drag-and-drop elements into a fully functional website. Users must have a solid understanding of CSS and positioning to achieve effective designs. One notable limitation is that Figma Sites currently does not allow setting custom classes for Div elements, which restricts design flexibility. I hope to see this feature in future updates. Lastly, the issue of bandwidth usage remains an important factor. For enterprise users, optimizing bandwidth through a CDN (Content Delivery Network) is crucial to maintain speed and stability. As for Webflow, I don't see it being significantly impacted. In fact, we might soon witness Webflow expanding its capabilities to support serious eCommerce without requiring third-party scripts, external packages, or complex CMS setups. Additionally, the pricing for CMS and bandwidth may become more competitive in the future.
