Change Stack is Always Good

Change stack is always good for users. May most of you have changed the technology stack for improving SEO benefits, ease of use and for user experience. It is certainly difficult or even sometimes not advisable to change the tech stack. I was about to complete 4 years of WordPress website development in July 2022. I decided in mid of June 2022 to move from the stacks I was using and experimenting with.

I would surely ask anyone to change the tech stack only if you are technically sound or have fast technical support from service providers, don’t have big web search traffic to your website, or you are to believe in taking a risk for giving a makeover. For me I always believed in change 4 change, so here are the reasons I changed the stack I was using for 4 years.

  • You need to upgrade the technologies for betterment
  • change stack is always good for users if you have focused on user experience on your website
  • I have tried, experimented, failed, with many stacks, and that’s given me the option for the right decision.
  • I have good technical support from the service providers, e.g. hosting, stack tools, DNS, etc…

Change Stack is Always Good On

Here is the list of stacks I have moved to and benefited from.

  • CloudFlare APO: This is the biggest and foremost important change I made on the CDN part. I have moved from BunnyNet to CloudFlare APO.
  • Cloudflare DNS: I have realised good and fast DNS is a must for any website and hence I tried Namecheap premium DNS to DigitalOcean, Google domains and finally Cloudflare DNS. The combination of Cloudflare DNS + Cloudflare APO is the best.
  • GeneratePress: Theme is very important for any non-techies on WordPress web development. I was using the Astra theme, and I have seen Astra is one of the best out there. But if you are a big believer in simplicity like me, then I would recommend GeneratePress.
  • GenerateBlocks: I was using the Elementor page builder, and I played with it so nicely and the web pages were so nicely designed with it. For me, the load which the elementor has given to my website, the tables, database space, and database options elementor loading on any website is concerned. The block editor is a better replacement for elementor and I would surely recommend GeneratePress + GenerateBlocks combo for speed and lighter weight. 
  • Perfmatters: Here is the stack from which I started the change. I am very much fond of Perfmatters and the co-founder Brian. The first plugin you should install on any WordPress website should be Perfmatters. 
  • RunCloud: An excellent support from a managed hosting provider and ease of use is a must for anyone like me. I have switched from A2 hosting, Cloudways, to RunCloud. I have learned many things about important aspects of WordPress website optimization from Cloudways. The support they provided was outstanding, and I was friendly with Cloudways’ support team members from Pakistan. But RunCloud is the growing and affordable managed hosting I would recommend to anyone who is intermediate or technically sound with website development. 

The stacks I have discontinued using

  • Webpush for push notifications
  • Socialsnap for social sharing widgets
  • Google stories
  • Elfsight widgets
  • Affiliate memberships

What I gained after changing the stack

  • Plugin load on our e-commerce website reduced from 52 to 43 and personal blogs sites from 20 to 14.
  • The entire website size is reduced by 50%
  • Improved TTFB
  • Query requests were reduced by 40%
  • HTML caching by CloudFlare improved total load time
  • Core Web Vitals PASSED
Change stack is always good for users

The first aim of any web developer should be to serve the best user experience on their web app. If one can achieve that, then it’s peace of mind and less stress work. Your focus can be diverted to other business areas instead of worrying about the stability and performance of web apps. 

Read my previous valueable action on WhatsApp