When’s the last time you waited more than two or three seconds for an e-commerce site to load? Current cart-to-conversion statistics reveal the sobering fact that for every second your page doesn’t load, you lose seven per cent of your conversions. In fact, subpar site performance correlates to the likelihood that 8 out of 10 consumers won’t return to your store and that 44 per cent of those with a less than stellar view of your site’s performance will forewarn friends to steer clear. Your e-commerce platform better is functional and perform to the exacting standards of today’s fast-paced market. According to the popular Magento, 250,000 e-commerce sites worldwide use either its community or enterprise editions of Magento 1.x or 2.x. It’s no secret that both have had past performance issues. But how do they compare today?
According to January 2018 BuiltWith stats, Magento’s Community Edition ranks fourth of all e-commerce platforms, while Magento Enterprise ranks eighth. The 1.x free, open-source Community Edition (CE) and the pricey Enterprise Edition (EE) remain viable, but will 1.x legacy users migrate to 2.x should 1.x reach its end of life? Support for 1.9 was officially supposed to end November 18, 2018. However, with so many e-commerce sites worldwide utilizing the platforms and extensions, the Magento company realized that migration to 2.x will take time and development for established 1.x legacy users to migrate without adversely affecting functionality and performance. According to a May 2017 statement by Magento Commerce, the company is committed “to a minimum 18-month notice before we make any changes to our support levels.”
**Important Note**
You’re not comparing apples to oranges when you’re comparing Magento 1 and 2. It’s more like visiting an auto show and finding that your favorite ride now has some exciting new upgrades and features that make it run more efficiently. Magento 1 established the framework. Magento 2 takes that framework and optimizes it to better align with current and future functional and performance needs of merchants worldwide.
Some key differences between Magento 1 (M1) and Magento 2 (M2) include:
Why are these differences important to Magento merchants and their developers? Because updating and migrating products and extensions can get tedious and expensive, especially when support is not guaranteed for 1.x. For some merchants, Magento 1 works for them and they’ll use it as long as they can. But as more merchants migrate to Magento 2, both open source and commerce platforms, these differences in functionality mean increased ROI.
But is functionality synonymous with performance? That depends on your perspective. Functionality from a developer’s point of view is different from how a user defines functionality and if that functionality translates into a sale or not. If a merchant is using a legacy version of Magento 1.x, whether it is the open source or the commerce platform, and it takes more than a few seconds for a page to load, that lack of functionality may affect your cart-to-conversion stats. Consumers want a user-friendly site that they don’t have to work too hard to get what they want. Developers look into a different kind of performance metric. They look at server response and page load times and tweak the code to make pages run faster so that merchant won’t continue to lose sales and to keep merchants higher in search rankings.
A couple of fixes that might help is to remove render-blocking JavaScript and CSS so that pages load more quickly. If anything it will make the above-the-fold view better, which is critical for your consumer, especially if purchasing from a mobile app. You can also compress the bytes flying over your server. You’ll need a Magento developer to delve into the speed issue.
While Magento 1 doesn’t have the innate bells and whistles Magento 2 has, it does perform well as a legacy platform with thousands of extensions available to bridge functionality issues. The bone of contention is how long will it be supported as Magento 2 takes root? In 2017, Magento Open Source released version 2.2.0 with numerous enhancements and functionality fixes. Developers continue to tweak the functionality and performance issues that beset both M1 and M2 early on as evident by its recent 2.2.2 releases, patches and tools.
Choosing to continue with Magento 1 or to migrate to Magento 2 depends on your vision of your e-commerce site. Choose your developer wisely, seek counsel on viable benchmarks and budgets as maintenance can be expensive, contact us to help you navigate through any muddy waters.
Mike Patel is the Founder and CEO of ioVista, a leading digital commerce agency specializing in eCommerce solutions. With a strong background in business and technology, Mike Patel has been at the forefront of driving digital transformations for businesses. He has successfully navigated the ever-changing landscape of eCommerce, helping companies leverage the power of online platforms to grow their brand, increase revenues, and optimize their digital presence. Under his leadership, ioVista has become a trusted partner with major technology companies: Adobe/Magento, Google, BigCommerce, Shopify, and Yahoo. He is dedicated to staying ahead of industry trends, adopting cutting-edge technologies, and continuously improving strategies to provide clients with a competitive edge. Mike’s commitment to excellence and client satisfaction is evident in every project ioVista undertakes.
Mike Patel
03 Jun 2025
Mike Patel
15 Apr 2025
Mike Patel
04 Feb 2025
Mike Patel
28 Jan 2025
Mike Patel
14 Oct 2024
Mike Patel
16 Jul 2024
Mike Patel
05 Sep 2023
Mike Patel
15 Dec 2022
Mike Patel
24 Nov 2022
Mike Patel
17 Nov 2022
Mike Patel
23 Aug 2022
Mike Patel
17 Aug 2022
Mike Patel
11 May 2022
Mike Patel
27 Apr 2022
Mike Patel
01 Apr 2022
Mike Patel
29 Mar 2022
Mike Patel
24 Feb 2022
Mike Patel
11 Feb 2022
Mike Patel
27 Jan 2022
Mike Patel
30 Nov 2021
Mike Patel
17 Sep 2021With 20+ years of industry experience, ioVista understands your eCommerce needs and delivers best-in-class solutions that help you gain a competitive edge.
TOP
ioVista
We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.
To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the website is accessible to all people: blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.
This website utilizes various technologies that are meant to make it as accessible as possible at all times. We utilize an accessibility interface that allows persons with specific disabilities to adjust the website’s UI (user interface) and design it to their personal needs.
Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the website’s HTML, adapts Its functionality and behavior for screen-readers used by the blind users, and for keyboard functions used by individuals with motor impairments.
If you’ve found a malfunction or have ideas for improvement, we’ll be happy to hear from you. You can reach out to the website’s operators by using the following email
Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting with screen-readers are able to read, comprehend, and enjoy the website’s functions. As soon as a user with a screen-reader enters your site, they immediately receive a prompt to enter the Screen-Reader Profile so they can browse and operate your site effectively. Here’s how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:
Screen-reader optimization: we run a background process that learns the website’s components from top to bottom, to ensure ongoing compliance even when updating the website. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.); validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process scans all the website’s images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen-reader mode on as soon as they enter the website.
These adjustments are compatible with all popular screen readers, including JAWS and NVDA.
Keyboard navigation optimization: The background process also adjusts the website’s HTML, and adds various behaviors using JavaScript code to make the website operable by the keyboard. This includes the ability to navigate the website using the Tab and Shift+Tab keys, operate dropdowns with the arrow keys, close them with Esc, trigger buttons and links using the Enter key, navigate between radio and checkbox elements using the arrow keys, and fill them in with the Spacebar or Enter key.Additionally, keyboard users will find quick-navigation and content-skip menus, available at any time by clicking Alt+1, or as the first elements of the site while navigating with the keyboard. The background process also handles triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus drift outside it.
Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers).
Despite our very best efforts to allow anybody to adjust the website to their needs. There may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating and improving its options and features, and developing and adopting new technologies. All this is meant to reach the optimal level of accessibility, following technological advancements. For any assistance, please reach out to
Get in Touch