During several years we have been studying and implementing various approaches to improve a speed of store server and frontend.
For an online store, the most important aspect is the operation speed. And here, it is important not only how fast a server returns a page to a client (TTFB), but also, how quickly the client can download this page and all related resources (files js, css, images, fonts).
The speed of operation is one of the most significant factors which affects the SERP ranking in search engines (Google, Bing etc). The faster a server generates the page and a client downloads it, the higher your store is in the search results at all the other things being equal.
When a customer knows what he needs to buy, his first action is to find the product through a quick search. The presence of a quick drop-down menu with the found goods (auto-complete) allows him to find the right product quickly without leaving the search line. The customer has only to complement the search query with the necessary criteria and then he will see the result.
Customers expect that search results will be shown instantly (they know experience of Google or Amazon search). But technically it is very hard to achieve such level of speed in Magento store. Every request to Magento needs to initiate magento core, which speed of initialization limits the speed of our search.
To solve this problem and to greatly speed up Magento search, we have created and added a new feature to our search extensions. We named it the Fast Mode.
Unlike in Magento 1, cron performs critically important tasks in Magento 2. In the native installation there are 26 modules that use cron for 53 different jobs. You can get acquainted with the full list of modules below on the text.
Practically, all reindex processes work in cron process. Newsletters, product alerts, page cache etc
Moreover, most of the third-party extensions use cron and some extensions simply do not run if the cron is not configured or operates in the wrong way.
We suppose, no one needs a proof that communication with customers is decidedly important and that a quick response to a users’ questions strongly affects the conversion rate in any store. At present, it is not enough just to tell everything on the site pages - many of potential customers prefer to ask than to look for the necessary information on the store pages.
Since the first days of mirasvit.com (since 2012), we have been actively used Zopim chat (now it is named Zendesk Chat). About a third part of our customers ask questions before placing their orders and as much ask after the purchase is completed.
404 errors occurs in all online stores. And it’s OK. New pages are added, old pages are removed. However, things go bad when the number of 404 errors becomes very high.
First of all, although 404 errors do not directly impact a store ranking on SERP, they consume already limited crawl budget Crawl Budget. Thus, they bring you unnecessary losses.
Secondly, the only fact of 404 errors presence negatively influences customers’ impression.
Imagine the situation: any user visits your store and gets a page with 404 error. He/she does not obtain the required content and, consequently, starts hesitating. In most of cases, he/she does not keep searching for the information on your store but rather prefers not to make any purchase.
We strive to convey the most detailed information on the product pages and manuals, but some questions are still open and arise quite often. Let's consider the most typical Reward Points + Referral program questions related to the extension operation:
Q: Suppose we created an earning rule for a product sharing rule on social networks. Is there any way to set any time interval between valid clicks (e.g. for share or like), so that preventing fraudulent actions?
A: Yes, we envisioned this alternative and added the possibility to limit the points maximum number earned per day for unique loyalty programs. In every rule, there is the "Actions" section where you can set the limit for earned points.
From time to time we receive complains from our customers for the slow speed of their Magento 2 stores. They ask us to help them to solve the speed problem. In this article, we tried to collect our experience and share a few hacks regarding fixing Magento store cache system.
It’s a very rare occasion that a store is slow because of a weak server. In most cases speed issues are related to a poor quality of some extensions or custom code inside your store. So to solve the problem and fix it, you need to spot the root causes. Let’s start with some basic info on the cache workflow and it will greatly help us later.
Sphinx Search Ultimate and Elastic Search Ultimate have very similar functionality. The main and the only difference between Sphinx Search Ultimate and Elastic Search Ultimate is the usage of different search engines: Sphinx engine and Elasticsearch engine.
We have a few questions to you: How often do you update your store? How often do you install a new extension on it? How often do you change settings configurations or make changes to the theme?
Today, we are here to reveal some things about Magento 2 Page Cache performance. The aspects we are about to describe below may be well-known to you, however, it is useful to remind about them time after time.