This article provides a fix for blockers to launching on Magento Commerce (Cloud) including issues related to Fastly config, SSL certificates, 301 redirects, and static asset performance.
1. Fastly Configuration
Fastly is a Varnish-based Content Delivery Network (CDN) for serving static assets. It is required for Magento Commerce (Cloud) on Production environments, so it's important to configure Fastly and test your website (UAT) with Fastly enabled and configured — on both Staging and Production environments.
With Full Page Cache (FPC) enabled, your website performs differently; make sure you test it before going live.
The process of Fastly configuration is documented in detail in the Set up Fastly topic on DevDocs. Below are the important steps.
1a. Make sure you have the most recent version of the Fastly module installed
Make sure you have the most recent version of the Fastly module installed to get the latest features and improvements. To check if you have the latest version of Fastly review DevDocs' Upgrade the Fastly module. For more details review DevDocs' Set up Fastly.
1b. Enable and configure Fastly using the Magento Admin
For more details review DevDocs' Get your Fastly credentials.
1c. Upload Fastly VCL snippets
For more details Upload VCL to Fastly.
You can also create and add own custom VCL snippets.
1d. Configure DNS for Fastly
Read these articles for detailed steps:
Related Fastly articles on Knowledge Base
- Knowledge Base Fastly caching is not working on Cloud
- Knowledge Base Error purging Fastly cache on Cloud (The purge request was not processed successfully)
2. Valid SSL (TLS) certificate
Problem: Without a valid and working SSL certificate, you cannot test external payment methods on the Checkout page — on the Staging environment.
Recommendation: Request your shared SSL certificate for Staging or Live domain names.
Read about SSL certificates on the Knowledge Base Quick FAQ.
3. Configure and test 301 redirects
Problem: 301 redirects are not provided or poorly configured, causing your store drop in SEO rankings and search listings.
Recommendation: Carefully configure and test the 301 redirects.
In case you're migrating from an old website to a new one, the 301 redirects lead your customers from the previously indexed old pages to the proper pages on your new store, like this:
http://www.mywebsite.com/old-category-page.html -> http://www.mywebsite.com/new-seo-friendly-category-page.html
- Redirects through routes.yaml on DevDocs
- Redirects through the Project Web Interface on DevDocs
- URL Rewrites on Magento User Guide
4. Asset performance
Problem: Static assets are served slowly so your site has poor performance (long load time, multimedia content not displayed, etc). Static assets of your website are CSS resources, images, videos, attached documents and much more. The way they are organized and served is a key factor in the performance of your site.
Recommendation: To identify possible causes of poor performance consider using Magento Performance Toolkit for performance testing. You could also consider these 3rd party tools:
- Siege: HTTP load-testing and benchmarking utility; supports basic authentication, cookies, HTTP, HTTPS and FTP protocols.
- Jmeter: A reputable load-testing and performance measuring tool. Helps gauge performance for spiked traffic, e.g., for flash sales.
- New Relic: Locates processes and areas of the site causing slow performance with tracked time spent per action, like transmitting data, queries, Redis, etc.
- WebPageTest (free) and Pingdom (paid): Real-time analysis of your site pages load time with different origin locations.
- Test deployment on DevDocs