Helly Hansen Adobe Commerce Magento PWA Studio vs. Luma performance comparison
Helly Hansen's Largest contentful paint performance.
We can see after the implementation of PWA Studio, studio performance decreased dramatically.
First of all, let’s check why not PWA Studio.
PWA Studio are heavy. Adob Commers PWA Studio is heavy slow websites. There’s no advantage for users — only for SELLERS. PWAs consume about 50MB of JS. It consumes the user’s bandwidth.
This alternative idea reminds us of the failed Google AMP propaganda. Another solution without a problem? A simple Magento Vanilla JS site is always a better strategy.
It’s touted PWA — Progressive Web Apps load instantly, respond to user clicks, and include an immersive UX. Wow! Really? Are they saying web pages don’t achieve these simple goals already?
That reported MAgento PWA Studio “optimization” is no miracle. This isn’t an improvement for the Internet! It’s average performance optimization. Ordinary, average page weight is 4 to 5 megabytes. Optimized Magento 2 and MAgento 1 web pages are much lighter — less than 1 megabyte — in the 150 to 250-kilobyte range. PWA weight is mediocre. Their main goal is converting loser and drowning apps to web pages.
Google scared site owners into thinking SEO is now dependent on being “mobile-first.” Google states responsivity (screen-size adaptation) is claimed to be the number one priority. And speed number two on the mobile-first criteria list. Do those SEO signals outweigh relevant content? Google wants to manipulate and keep us in the dark, as usual.
Google claims the big switch to mobile-first listings arrived in July 2018. But geeks employed by Google say mobile-first rankings “won’t count” for SEO. At least not until 70 percent of the Internet adopts the practice. Why? They can’t afford to tick off their big advertising income. Big account ranking-damage would be bad for Google business. So do as Google says, not as they do.
Google employees think they’ve achieved a 30-percent mobile-first adoption. Uh? That’s the same stat they brag about for SSL adoption. But other sources like BuiltWith say it’s only around 4 percent of the Internet. We suspect this propaganda is a plea for “get-on-the-bandwagon” bias.
Mobile-first ranking doesn’t matter as much as relevant content. It may never matter. Google dogma sometimes has no teeth in the real world.
Core Web Vital Adobe Commerce PWA studio performance: failed
Old Magento 2 Luma-based website performance vs PWA Studio.
Google page speed results in classical Luma frontend
Mobile Score: 18
Adobe PWA Studio performance
As we can see, Adobe Commerce PWA Studio's performance on mobile is suks, and Helly Hansen was decided by the Adobe sales liars about PWA's performance, and migration to the PWA was sold.
Magento 2 Page Speed Performance Desktop
Desktop Score: 30
PWA Studio performance
Results are pretty bad for the world brand…
Will the Hyva theme fix the magento performance issue?
For sure not! Hyva fixes just the frontend part load time however magento backend is still sucks and low performant. You can Fix MAgento 2 just by re-platforming to a new skin with fewer fonts. You can remove all extra fonts and MAgento 2 junk JS on your theme without re-platforming to a weird stack AlpineJS + Tilewind.
No matter what skin/theme you have, you need a fast backend to have a good website. The only way to improve the performance of the backend is not to use insufficient Magento 2 Backend framework and make direct communication with the database or some indexing NOSQL DB using Laravel, Python or NodeJS, GO, Rust. Magento Admin will be the same garbage but who cares if the front end is amazing fast?
However, the bigger issue of magento 2 is not performance. It is endless bugs and complexity to fix the magento 2 spaghetti code. Just MAgento Core has 6000 open bugs and issues + issues in the enterprise modules and 3-d party and 1-st part modules and integrations on top of broken core. Adobe Commerce is a nightmare of modern e-commerce software.
A demo of such MAgento NodeJs implementation you can see here:
Let's check Adobe Commerce GrapQL performance vs. NodeJS
Just a single product data fetch took 618ms. And it is just one call. Magento needs around 20 such calls to render a single PWA Studio page.
GrapQL to fetch the data:
https://www.hellyhansen.com/graphql?query=query+getProductDetailForProductPage%28%24urlKey%3AString%21%29%7Bproducts%28filter%3A%7Burl_key%3A%7Beq%3A%24urlKey%7D%7D%29%7Bitems%7Bid+uid+page_title+__typename+...ProductDetailsFragment+...ProductPerformanceFragment+...ProductInfoFragment%7D__typename%7D%7Dfragment+ProductDetailsFragment+on+ProductInterface%7B__typename+features+short_description%7Bhtml+__typename%7Dcategories%7Bid+uid+breadcrumbs%7Bcategory_id+category_name+__typename%7Duse_as_related_category+name+url_path+__typename%7Ddescription%7Bhtml+__typename%7Did+uid+meta_description+meta_keyword+name+price%7BregularPrice%7Bamount%7Bcurrency+value+__typename%7D__typename%7D__typename%7Dprice_range%7Bmaximum_price%7Bfinal_price%7Bvalue+currency+__typename%7Dregular_price%7Bvalue+currency+__typename%7Ddiscount%7Bamount_off+__typename%7D__typename%7Dminimum_price%7Bfinal_price%7Bvalue+currency+__typename%7Dregular_price%7Bvalue+currency+__typename%7Ddiscount%7Bamount_off+__typename%7D__typename%7D__typename%7Drobots_meta_tag+sku+small_image%7Burl+__typename%7Dstock_status+pdf_sheet+product_use_for%7Bcode+title+__typename%7Durl_key%7Dfragment+ProductPerformanceFragment+on+ProductInterface%7Bperformance_breathability%7Blabel+value+__typename%7Dperformance_durability%7Blabel+value+__typename%7Dperformance_insulation%7Blabel+value+__typename%7Dperformance_waterproof%7Blabel+value+__typename%7Dperformance_weight%7Blabel+value+__typename%7Dperformance_windproof%7Blabel+value+__typename%7Dproduct_workwear_features+__typename%7Dfragment+ProductInfoFragment+on+ProductInterface%7Bcare_instructions%7Bhtml+__typename%7Ddepth+fiber%7Bhtml+__typename%7Dlength+volume+water_column+weight_with_unit+width+__typename%7D&operationName=getProductDetailForProductPage&variables=%7B%22urlKey%22%3A%22jr-daybreaker-tights-41739%22%7DHow fast will Node JS (NodeJento)call for product data?
To fetch data about the product using NodeJS we need 16ms. 40 times faster than using a broken Magento 2 Framework!
You can defeatedly use AWS Lambda or other serverless services to host API code without any Adobe Commerce Cloud nonsense.
Example of the Node JS response from the slide:
And remember Adobe is still doing business with Russia and Belarus and sponsoring war in Europe! Adobe Partners and customers also is indirect sponsors of the Russian war crimes. Stop Busines with russia!
PS: Sounds like Adobe deceived their customers again. Sold PWA Studio to them and abandoned this project!
Even Adobe lovers is not satisfied with this crap.
Our previous research about Magento 2 and Adobe Commerce — Helly Hansen fiasco:
