I am not with the eCommerce agency anymore, so I can't get you a more detailed answer for the schema. As I remember, it made some difference when implemented because the content became more prominent on Google search results. Of course, other SEO optimizations like keywords and proper site structure also played the most important role, so schema was the icing on the cake, so to speak. We didn't blindly follow the industry best practices, all changes were incrementally implemented and measured separately. I wanted to mention schema.org in the article because there are devs out there who are not aware that it exists, and it can be useful to better describe the content on the page.
I agree that the "mobile-first" approach is superior to simply scaling down a desktop view. When I was working on the eCommerce sites, there were some sites that had desktop-only frontends and needed to be scaled down to mobile because it was too expensive for them to create a theme from scratch. In that section, I wanted to reiterate the importance of responsive design and its weight in decision-making.
I've been working with React for the past year or so, and I've seen sites implemented with various performance results. There are some React optimization techniques that can be applied to improve the performance, like Gatsby is optimized out of the box (uses SSR and code splitting).
Hopefully, I've made things more clear. Let me know if you have any more questions. Glad you found the article helpful.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hello Stanislav and thanks for your input.
I am not with the eCommerce agency anymore, so I can't get you a more detailed answer for the schema. As I remember, it made some difference when implemented because the content became more prominent on Google search results. Of course, other SEO optimizations like keywords and proper site structure also played the most important role, so schema was the icing on the cake, so to speak. We didn't blindly follow the industry best practices, all changes were incrementally implemented and measured separately. I wanted to mention schema.org in the article because there are devs out there who are not aware that it exists, and it can be useful to better describe the content on the page.
I agree that the "mobile-first" approach is superior to simply scaling down a desktop view. When I was working on the eCommerce sites, there were some sites that had desktop-only frontends and needed to be scaled down to mobile because it was too expensive for them to create a theme from scratch. In that section, I wanted to reiterate the importance of responsive design and its weight in decision-making.
I've been working with React for the past year or so, and I've seen sites implemented with various performance results. There are some React optimization techniques that can be applied to improve the performance, like Gatsby is optimized out of the box (uses SSR and code splitting).
Hopefully, I've made things more clear. Let me know if you have any more questions. Glad you found the article helpful.