Boost conversion rate in Magento, Shopify, WooCommerce or PrestaShop by implementing lighting fast PWA & SPA
- 50% conversion increase
- 70% average order value increase
- 100 points in PageSpeed Insights
- 0.5 second to fully load the page
How does it work?
Since you found this page, we assume that you know the advantages of PWA implementation in your store, but if you don't, go to FAQ and read about the advantages of PWA in the section below.
We offer you the service of the least invasive PWA implementation in your store.
PWA & SPA
It works in such a way that our system, by using a ready Rest API built into your store, will download and update products, categories, CMS pages, blogs, etc. In addition, we will update the stock status and product prices in real time, so that what the customer sees on the PWA side it is always up-to-date.
In order to complete purchases, the customer will be redirected to your store, where hi will complete the order, or checkout can take place on the frontend side - also through background integration via the API, depending on how you want to have the integration configured.
With this configuration, you will increase conversion rates and never again have to worry about the scalability and speed of your store. This issue will be passed on to us.
Boost your conversion rate
On Google blogs, you can get specific statistics - by how much did the conversion and user engagement improve after PWA implementation. We also encourage you to read the case studies of our clients.
Speed and SEO
Citing official Google announcements, such as "Speed is now a landing page factor in Google search and ads", we can easily see that for several years Google has been paying more and more attention to the speed and usability of websites. It clearly sets the direction store owners should take if they want to think about good organic search results and low advertising costs.
Using the PWA website gives you the feeling of using a native desktop or mobile application.
Add to home screen
Add to the mobile home screen is a function available in modern browsers that allows the user to "install" a web application - add a shortcut representing their favorite web application (or website) to the home screen, so they can access it later with a single touch.
After "Installing" Progressive Web App on the phone, the entire display area is used by the PWA. Browser UI elements such as the address bar, navigation and status bar are hidden.
PWA acts as an "overlay" on the backend of the store. PWA is not generated by the backend, it is linked to the backend via the API. This means that we are dealing with headless architecture here. Some advantages of this architecture are:
- The possibility for different project teams to work on the backend and frontend
- The fact that we do not have a tight connection between the backend and the frontend means that it is easy to "replace" individual elements of the system. E.g. changing store backend from Magneto to Shopify, keeping frontend unchanged.
- Fast design iterations
- Easily integrate with other companies that are less disruptive to growth
- Resilience to changes on the user interface side
- Simpler implementation
Blink-cart PWA advantages
Great spikes in website traffic e.g. during advertising campaigns are no longer a problem
Your server will take a breather and benefit from the new setup. Thanks to the implementation of PWA, you will significantly reduce the load on your server. The more traffic your store generates, the greater the profits resulting from the PWA implementation will be.
Single Page Application
Our PWA works on the basis of the Single Page Application architecture, which, in our opinion, should be a necessary condition for the application to be called PWA, but it is not obvious for all companies. You can find "PWA modules" that actually add a manifest to the page and little more.
The fastest and least problematic installation
Integration with your store, in the fastest variant, could be completed in one day. It is an extremely short time, since the implementation of PWA has so far involved months of work.
Lower development and maintenance costs
Until now, implementing PWA has been a very costly affair. Thanks to our specialization in Progressive Web Applications, we have developed methods that automatize processes and drastically reduce the cost of implementation.
Since more people now use phones than computers to browse the internet shops, when designing an application, we first design the perfect mobile version, which then serves to design the desktop version.
Multi Websites support
We can easily generate independent PWAs for each of your "store view". Each view can have a completely independent appearance and functionality.
Our PWA is not integrated with just one type of software. This means that for example, if you are using Magento now, and in the future you change the software to PrestaShop or Shopify, your PWA from the client's side will not change, and the changes needed on our part to switch PWA backend will not require much work.
The least intrusive integration
Our architecture assumes the least possible interference with the software of your store, in such a way that the installation and uninstallation of our PWA is possible in the shortest possible time.
In our estimation, we should receive no more access from the stores that we work with than any ordinary visitor of the store. We will not have access to orders or customer data on our side. At the same time, integration with our service will make it possible to "hide" your store instance behind our PWA. Therefore, you will increase the resistance to attacks on the frontend of the store, because it does not have to be publicly available.
Demo available in 5 minutes
A launch of a demo with your store offer is possible in 5 minutes, and you can run it yourself using the above form. On one of the ready-made templates, you can check how fast your store is running without spending money.
As we are the author of our PWA, and we do not use ready-made solutions, we are able to meet your special requests regarding the appearance of PWA and functionality.
The fastest PWA on the market
Our PWA is the fastest possible on the market. Check how it works on your phone and desktop computer.
Ready theme or custom implementation
We can run PWA based on one of our ready-made graphics, or we can implement any graphics. We can use your current store graphic or encode PWA based on the design provided by your graphic designer.
Any location of the PWA possible
We are flexible and the server your PWA will run on can be located in any country chosen by you on any continent. There is also no problem with installing CDN on request.
Incredible speed and best scores in Google PageSpeed Insights
|Magento default||Magento with Blink-cart|
|DOM content loaded||~ 1 s||0.0 s|
|Page loaded||~ 2 s||~ 0.2 s|
| Developers.google.com |
Avreage order value
... The results with React are impressive compared to our earlier Prestashop site. Our conversion rate has increased from 2,7% to 4,2%. That is more than a 55 percent increase .
Also our average value per visitor has increased - with Prestashop it was 1,86€ and after our migration to React we have seen an impressive 85% increase to 3,45€ ...
... Our strategy is highly dependant on driving organic traffic to our site. For this reason, Google is very important to us. For some time Google has been emphasizing that the speed and their usability metrics will have an ever-increasing impact on page rankings on Google search.
We have been struggling with the speed of our PrestaShop site. Either we would have to use just the barebones modules/theme or have poor performance.
Then I came across Blink-cart and their offer of turning a PrestaShop or a Magento site into a super fast React site (SPA, Single page application) was very appealing. The way it works is that the back end will use PrestaShop but the front end will use a custom, React-powered theme (using GatsbyJS framework). The data will be pulled from PrestaShop using a series of APIs and PrestaShop webservice.
After talking with their team, we started work on our project. Our shop needed some extra work since we use a few custom plugins that we absolutely needed to include, e.g. a custom reviews module and a Perfect size widget. But they were happy to work with us to design a perfect solution for us ...
Read full case story at: blog.pucilowski.eu
Frequently Asked Questions
What is Progressive Web App (PWA)
The goal of PWA is to fill the gap between websites and mobile applications. Their ultimate goal is to provide a flexible solution that will adapt to both desktop computers and mobile devices. Most of them work like a website that can be saved as a shortcut to the home screen of a smartphone or tablet and used directly from there. It looks like an application, acts like an application, ensuring a high level of user comfort. Each PWA must have several specific characteristics. Google provides three conditions that must be met to recognize a website as a PWA:
1. Loads quickly with poor internet connection
2. Runs quickly and smoothly
3. Acts similar to standard mobile applications, giving you a great user experience
These are not very precise terms. It is enough to implement the so-called manifest and SSL certificate so that our website is treated as "PWA" by mobile browsers. However, is our site really a PWA then?
Below we present a more detailed list from Google, only after meeting most of the following conditions, we can say that the website is a PWA:
1. The website should have HTTPS implemented
2. The website should be responsive on tablets and phones
3. The website should "respond" even without an internet connection
4. Implementation of the manifest
5. Fast loading of the page even with a weak connection - loading in less than 10 seconds with a 3G connection
6. The website should work on Chrome, Edge, Firefox and Safari
7. Moving between pages should be immediate
7. Each subpage should have a unique URL
8. Google should be able to index subpages
9. Metadata implementation
10. Implementation of social media metadata
10. One content should be available only under one URL (preventing duplication of the same content at different addresses)
11. Implementation of the LocalStorage, SessionStorage API
12. Proper photo loading
13. Preserving the position (scroll) of the page after we return to this page from a different page
14. After clicking on an input, the on-screen keyboard should not cover it
15. Proper page display on phones, tablets and computers.
This is only half of the guidelines, all of them with a detailed description can be found at https://developers.google.com/web/progressive-web-apps/checklist
What are benefits of PWA?
First of all speed. PWA applications load faster and work faster than traditional websites, and this increases user experience. We gain more customer returns and more conversions.
Better positions in google. For Google, it is becoming more and more important in the evaluation of the website is the speed and fulfillment of Google's requirements regarding the quality of the website, and this later translates into the ratings that the website receives from Google.
What will change after PWA implementation?
From the point of view of the store administrator, not much will change. The admin panel and all integration with external systems remain unchanged. The store functions as it did on the same server. Together with the owner of the store, we will select the appropriate time values for refreshing the store's cache.
From the point of view of the customer, the store speed and user experience will be enhanced.
What is Single Page Application (SPA)?
Single page application is a concept that allows the entire website of the store to never be completely refreshed. That is, if e.g. the customer moves between the products of the store, he only downloads information about a given product, and not the entire website, as in the case of a standard website. Due to this, we do not force the client to download over and over again sections such as the category menu, banners, website footer and others.
Why should I implement PWA?
Because you want to provide the best experience for your customers as they use your store, and thus increase your profits. It is worth bearing in mind that the PWA guidelines have become more and more important over the years for Google in the evaluation of websites.
What if my software is not supported?
Please contact us. Our company is able to undertake individual projects and integration with any EPR and e-commerce system.
Price of PWA implementation?
There are many factors, the two most important are whether we start with our ready-made graphics and modify it according to your guidelines, or whether we implement your original graphics in our system. The second important impact on the initial setup price is whether your store has a lot of modules that somehow affect the operation of the PWA - then we will have to adjust PWA to your needs.
Where PWA is located?
Because in order to ensure the best results in terms of PWA performance, quite a complicated infrastructure and server configuration are needed. We found that the easiest way would be if PWAs would run on our servers, which are optimized especially for speed. Because of this, from now on you will not have to worry about weather your store is fast in every situation because this problem has been passed on to us. The physical location of your PWA is to be determined with us, we can locate your PWA in Europe, America, in any country. We can also connect CDN networks. Your store's backend will work as usual on your server.
What technology do we use?
From the PWA side, our scripts are written in React, for SSR we use the Gatsbyjs framework, which is SEO optimized as standard. However, a lot of work has been put into it to ensure even better optimization in terms of SEO.
How long will implementation take?
The opening of the PWA demo takes 5 minutes. With ready-made graphic design and standard setup without custom modules, it takes 1 day to open a PWA. With non-standard graphics and non-standard requirements, the time takes from 2 weeks to a couple of months, depending on the complexity of the project.
Custom changes after implementation?
After we launch the store, we are most willing to make changes to it according to your guidelines. We are open to work with your graphic designer, you can also hire our graphic designers.
Is it safe?
We started from two architectural assumptions of our system to ensure the safety of the entire architecture. First, we don't want access to your store database. We only want as much API access as is absolutely necessary to create a product catalog, authenticate the customer, and nothing else. This means that even if our servers were hacked, the hacker would not get to your database because we simply do not have access to it.
Secondly, despite the fact that we use renowned data centers, and even if all our servers, backup servers were exploded at one moment, the entire architecture is so flexible that disabling our PWA and restoring the old operation of the store should take only a little while.
What's more, thanks to the fact that the frontend of your store can be turned off (except checkout in case of integration with redirection), from the moment of integration you will not be exposed to attacks on your store that use bugs in the front of your store. And these are the most common attack vectors when the store is based on open source software such as WooCommerce, Magento and PrestaShop. Internet forums are full of complaints from affected shop owners, who have not updated their shops on time. Robots that search the Internet for known vulnerabilities will not pose a threat to you anymore.
What it needs to create demo?
We need access to the Rest API of your online store. For the "read" ("GET") methods for product catalog, product categories and CMS pages, that's it.