I been building eCommerce platform on my own and been weight in on every improvement that will be added to the system (not enough hours in a day... hehe).
I talked with multiple store owners that implemented structured content (e.g. Schema.org), but non of them had any significant improvements from those changes. Have you been A/B testing those changes? Or measuring search traffic going your way? did they bring any significant improvements in your case? Or your just blindly following best industry practices?
I also agree on importance of mobile experience, most of consumers are on mobile now. But "Responsive Design" is a mostly failed approach in my view, scaling down from desktop is harder and experience is still not on par with desktop. I usually advice on going "Mobile first" and scaling to desktop later.
Most of mobile devices nowadays are cheap android phones (150$ - 300$ range) and best optimization you can do for those is ditching react completely. I got one of those phones myself and started using on a daily basis -- and it's just hard not to get annoyed about website built with react. dev.to or sites built with gatsby are one of those rare examples that exclude from this rule.
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.
I been building eCommerce platform on my own and been weight in on every improvement that will be added to the system (not enough hours in a day... hehe).
I talked with multiple store owners that implemented structured content (e.g. Schema.org), but non of them had any significant improvements from those changes. Have you been A/B testing those changes? Or measuring search traffic going your way? did they bring any significant improvements in your case? Or your just blindly following best industry practices?
I also agree on importance of mobile experience, most of consumers are on mobile now. But "Responsive Design" is a mostly failed approach in my view, scaling down from desktop is harder and experience is still not on par with desktop. I usually advice on going "Mobile first" and scaling to desktop later.
Most of mobile devices nowadays are cheap android phones (150$ - 300$ range) and best optimization you can do for those is ditching react completely. I got one of those phones myself and started using on a daily basis -- and it's just hard not to get annoyed about website built with react. dev.to or sites built with gatsby are one of those rare examples that exclude from this rule.
Here is a fantastic talk on Mobile Web situation
vimeo.com/364402896
Thanks for an article though and for increasing bar for eCommerce! A lot of helpful advice here!
I can DM you a case study on schema.org that we did at my previous company if you follow me on DEV and if you're interested.
Looking forward to that study! just followed you back
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.