Mobile & desktop page speed improvement.Theme level CSS & JavaScript optimization - minify CSS, minify JS, inline CSS, inline JS.Option to compare image quality (before & after).Option to preserve photo quality (lossless).Image compression on all pages - home, collection, product, blog, & more.Latest image size & quality optimization methods from Google.Here is a comprehensive list of what you get: You need to optimize your code & a lot more for better SEO & higher conversions. How? All-in-one Page Speed Optimization AppĪ fast-loading Shopify store is not just about resizing & compressing images. Plug In Speed does exactly this, plus offers everything else you need to speed up your Shopify store and make more sales. The good news is, you can fix all these problems easily with an app that increases your store's speed on both mobile and desktop. Less traffic = fewer sales = poor revenue Higher bounce rate = less website traffic Slow loading sites lead to higher bounce rate (more people dropping off your website) IMHO these should be part of the default build process, I understand there's a reason for pushing SCSS compilation onto Shopify, but when it seriously affects the flow and speed of development, it might not be worth it.A slow-loading page or site harms your online business revenue and eventually profitability. In my own projects I'd happily fork slate-tools to deal with these things, but I don't feel I'm the only person who would want to see SCSS compilation errors or use the latest version of Sass. So even if there was a way to override just the processCss() and processThemeJs() functions locally within the theme, that would be super handy. When you're used to working with the latest version, it's really hard to revert to a 4 year old version of the same toolįrom what I've read on this repo and the Slate repo, most people are looking to do some variation of the above, but rarely want to modify anything else within Slate tools. Shopify's Sass is so old it doesn't support things like &_elem, let alone any of the other new features that have been added since 2013. I could be wrong but it doesn't seem possible to see compilation errors even within the Shopify console, which makes it really hard to pinpoint errors (which I encountered due to the next point) Receive SCSS compilation errors in real-time.For example, these are the things I want to do: I feel that most people are only going to want to change the css and js tasks. This isn't my decision, so for this project I have to stay on the safe side and use Slate as-is. They want to stay on the edge and keep Slate up to date when new features are released, but a forked slate-tools could make it harder for them to upgrade. If you don't plan on setting up CI testing in your own repo, you could have those same prepublish commands run at a different time - like hooked into your package's version scripts or part of your git commit Personally I'm fine with forking slate-tools, but I work with a lot of different teams on different projects and one of them has expressed concerns about the friction a forked version of slate-tools would add to the upgrade process. I had to manually build using npm run prepublish before pushing to That command is run automatically in our own repo with the Circle CI integration. However, being able to have more control over what Slate does at different stages of the build process is something that is being requested - so this falls under that category. So at this time, what you're proposing isn't something we'd introduce to the Slate build process. And explaining the workflow wasn't something we were going to go all in on and publicly document as "the new way themes at Shopify work". Having both files would indeed be useful to developers who could intuit why there was both a *.js and *.min.js, but it risked being confusing for anyone else. js file, then minify it in a separate process, then replace the existing min.js with this new file isn't something we wanted to introduce as a new practice in themes. Uploading both a *.js and *.min.js file in the theme assets was debated, but ultimately we decided not to do it as we weren't convinced it was a workflow to encourage. This is something we've discussed on the Themes team as well. However, in most cases, I strongly feel like the original, un-minified JavaScript file should be preserved for merchant's developers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |