Magento Webshop Tutorial: going live – moving or migrating your Magento webshop to a live server. On this page we provide our customers the Ultimate Magento Go Live procedure. More information about going live with your Magento on Hypernode technology can be found in the Hypernode support documentation.

Delete unused Magento extensions/modules

Remove all that is not essential.

  1. Question the use of every extension > Needed at all? Needed now? Maybe later? Delete ALL unused extensions/modules (don’t just disable, because that won’t prevent execution of the code). Most Magento sites have 5-10 extra modules. More than 30 extra modules will most likely slow your site down tremendously.
  2. Throttle Search Engines!
    • Throttle Google through Google Webmasters.
    • Add a robots.txt that limits Google and other search engines and bots from indexing.
    • Prevent duplicate content with canonical URL (This saves CPU):
      • 1. Allow:
      • 2. Disallow:
      • 3. Disallow:
      • 4. Disallow:
  3. Try to add nofollow links for URLs that are not relevant to Search Engines: Yoast is a likely module.
  4. Create a sitemap to help bots crawl the right pages.
  5. Verify that your site works independently from external calls: do not connect to Facebook, Twitter or other external sites. Do not connect to an inventory system realtime with every pageview, but do it asynchronously in the background (using cron). Network calls add lots lag. What happens if the other site is down? Your site is slowed down for 5 seconds on each page load and the server grinds to a halt.
  6. Check all modules that are installed. If remote resources are needed. Cache them on disk and download them through either the admin panel or the shell server.

Optimize your Magento shop before going live

Make sure everything works perfect.

  1. Eliminate all use of flock(). Imagine a bottle, look at it’s neck, this is flock(). Decentralize if possible.
  2. Run test through PageSpeed. Optimize!
  3. Run test through YSlow. Optimize!
  4. Make sure 404’s are not handled by Magento.
  5. Optimize images, simplify CSS, javascript.
  6. Leverage browser caching through caching optimization. See YSlow to see what the browser still downloads. Remove ETags, add Expire headers. This clears webserver slots for other customers.
  7. Minimize or eliminate Ioncube loading, see Byte Blog.

Make sure Magento is as light and fast as possible before going live

Setting speed options makes Magento 5-10 times faster and lighter.

  1. Enable all the cache options in Magento.
  2. Clear /var/cache
  3. Make sure all cache goes to MySQL, not to disk (check var/ dirs).
  4. Eliminate disk i/o alltogether through Full Page Caching. Use a Full Page Cache (FPC) mechanism (Magento Enterprise, Nitrogento).
  5. Test working of Full Page Cache and prime FPC.
  6. If you run on a dedicated server that features the APC cache, please make sure you enable and double check APC.
  7. Please test the working of APC just before going live. Often, last minute changes require you to disable APC. In the heat of the moment, developers forget to turn it back on.
  8. Prime APC before launching.
  9. Use JPG’s in stead of PNG’s for products images. They’re smaller and generating takes less time (Thus: CPU & Diskpower).

Test the Magento functionality and performance extensively

Extensive testing ensures success, so make sure you test your shop thoroughly by taking the following steps:

  1. Communicate with Byte on how and when to run benchmarks (!).
  2. Pre-generate image families. Are all images pre-generated?
  3. Test performance/usage per hit/visit. Get BPU below 0.20 per visitor.
  4. Run benchmark on many different pages (generate list of all URLs, randomize, put in siege). Not only on 5-20 pages. Good benchmark service is: Browsermob.
  5. Run benchmarks WHILE doing import/tests/administrative tasks, to simulate real life situation.
  6. Doublecheck whether or not the back-end capacity is sufficient to support all orders in peak situations (For instance during the ‘sales’ period), be it SAP, MSSQL or another system.

The day your Magento shop goes live

If you’ve tested your shop and are satisfied with everything, you can go live:

  1. Communicate well: write a clear and simple plan for going live. Communicate the plan with both customer and Byte. Choose fixed dates for testing and going live. Let your implementation partner appoint a technical contact (this should not be a programmer, but should be knowledgable). Coordinate a technical contact at Byte as well. Check your plan with your Byte contact.
  2. Choose your Go-Live time well. Choose a relatively dull moment (monday). This leaves you some time to iron out the most critical bugs with relatively few users on the server. Then launch the campaign and bask in the attention while solving the last few bugs.
  3. Domain name / DNS > make sure DNS is at Byte. This helps us to scale your application. If we do not manage the DNS, we cannot relocate your application. In times of need, Byte cannot help when things go wrong if you manage your own DNS.
  4. Disk usage must be monitored (#GB, logs, caching). Make sure you have enough diskspace in your hosting plan. Make sure you check DB space and webspace.
  5. Never combine the Go-Live with any campaigns. Do not run actions while going live. Go for a week in “first launch” and time campains for the next week, when the dust settles.
  6. Go live with a reduced amount of products and functions (beta period).
  7. Scaling down is easier that to scale up: start up with more nodes! Set up with a dedicated database cluster.
  8. Prepare a backup plan and have a “Please come back and leave your mail address here”-page ready.
  9. Prepare a communication strategy with Byte (who is the principal technical contact at implementation party, who is the technical contact at Byte?).

Keep it clean – Prepare all Magento maintenance tasks

Make sure your Magento shop stays clean and fast by preparing the following:

  1. Periodically clean your Magento installation: add the standard cronjobs on the shellserver
  2. Clean reports
  3. Reindex when business is slow (02:00 for example)
  4. Clean the databases
  5. Remove logs from disk, database
  6. Check the var/ dirs, they tend to clog up