EveryHost: Magento Dedicated Hosting UK
    Peak season 2026: Black Friday is 27 November

    The Magento Black Friday readiness checklist

    Secure, fast, and built to last

    By Simon Bumford, Founder of EveryHost••10 min read

    The date everyone plans around is the wrong one

    27 November
    Black Friday 2026
    30 October
    When most merchants freeze changes
    2 October
    Last sensible date to start a move

    Everybody counts down to Black Friday. Very few people say the deadline that actually binds. If you want to change anything structural, move host, re-platform, upgrade a major version, the work has to be finished and bedded in before your code freeze, not before the sale. For most Magento merchants that freeze lands around the end of October, and a migration done properly takes about eight weeks end to end.

    This checklist is deliberately written so it is useful wherever you are hosted. Most of it is work you or your agency can do this week without speaking to anybody. Four sections, and each one links to a longer piece with the detail.

    Secure

    Peak is when attack traffic and change freeze collide. Everything you have not patched by 30 October, you are trading through.

    • Confirm your exact Magento version and patch level. Not the major version, the -p number.
    • Apply every outstanding Adobe security patch, in order. July before August, August before September.
    • Check nothing under app/etc/ or var/ is reachable over HTTP. It should return 404, not 403.
    • Search your web root for a stray .env, .git directory or database dump. Including the backup you took during a deploy and forgot.
    • Put two-factor authentication on every admin account, and delete the accounts belonging to people who left.
    • Move the admin URL off /admin if it is still there.
    • Confirm someone is reading the security alerts, not just receiving them.
    Read the full secure guide →

    Fast

    Your homepage is not the problem. It is cached and it is the one page everybody tests. Peak breaks where cache cannot reach.

    • Load test the logged-in journey, not the homepage. Cart, checkout, and payment.
    • Check your full page cache hit rate. A low rate under load is the single most common peak failure.
    • Confirm indexers are on Update by Schedule, not Update on Save.
    • Check cron is actually running and consumers are alive, not just installed.
    • Make sure OpenSearch or Elasticsearch is healthy and correctly sized. It is the component most often left on defaults.
    • Look at your slowest real page in field data, not lab data, on mobile.
    • Know your headroom. If you do not know what your server does at four times normal traffic, you do not know if you are ready.
    Read the full fast guide →

    Built to last

    Everyone has backups. Almost nobody has tested a restore. Peak is a poor time to find out which you are.

    • Restore a backup to staging and time it. Write the number down.
    • Confirm backups are off-site, not on the same server as the store.
    • Check you can roll a deploy back, and that someone has done it before.
    • Have a working staging environment that matches production, including the extensions.
    • Set your code freeze date and tell everyone, including the agency.
    • Write down who to call at nine on a Friday night, and test that the number is answered.
    • Agree in advance what you switch off if the site is struggling. Decide it now, not at the time.
    Read the full built to last guide →

    Sell more

    The part most hosting checklists skip. Peak traffic is worth more when the people arriving can find what they came for.

    • Read your on-site search terms report. It is free and it is already in your admin.
    • Find the searches that returned zero results but describe something you actually stock.
    • Add the words your customers use to the product copy. They are not the words you use.
    • Check your delivery cut-off dates are correct, published, and visible before checkout.
    • Look at where your orders actually come from, and compare it to where you advertise.
    • Test the site on a mid-range Android phone on a normal connection, not on your laptop.
    • Make sure your search box works on mobile and returns something useful for a two-word query.
    Read the full sell more guide →

    If you only do one thing

    Ask your host to restore your store to a staging environment, and to tell you how long it took.

    Nearly every merchant has backups. Very few have ever restored one and timed it. The number matters, because on the busiest Friday of the year the question is not whether a backup exists, it is whether you are down for twenty minutes or six hours.

    How comfortably your host answers that question tells you more about your hosting than any specification sheet. If the answer is vague, that is your answer.

    Magento peak season: frequently asked questions

    Frequently Asked Questions

    Friday 27 November 2026, with Cyber Monday on 30 November. That is the date everyone plans around, and it is the wrong date to plan around if you are thinking about changing anything. The date that matters is the start of your code freeze, which for most Magento merchants falls around the end of October.

    If you want to move host, the honest last sensible date to start is around 2 October 2026. A migration plus DNS propagation, a full test cycle and a few weeks of running live on the new platform before you freeze changes takes roughly eight weeks end to end. Start later than that and you are learning your new environment during the busiest trading days of the year, which is the opposite of what you wanted.

    A code freeze is a date after which you stop deploying anything that is not a fix for something broken. Most serious Magento merchants freeze about four weeks before Black Friday, so around 30 October 2026. You need one because the failures that hurt during peak are almost never the traffic. They are a deploy that went out on the Tuesday and quietly broke a payment method nobody tested.

    Rarely the homepage, because it is full-page cached and it is the one thing everybody tests. What breaks is the part cache cannot reach: logged-in carts, checkout, search, and the indexers and cron jobs behind them. A store can show a 1.2 second homepage and still lose the sale at the payment step under load.

    No. Most of this checklist is work you can do wherever you are hosted, and we have written it so that it is useful even if you never speak to us. Move host if your current one cannot answer the questions in the reliability section, particularly how long a full restore takes and who picks up the phone at nine on a Friday night in November.

    Testing a restore. Nearly every merchant has backups. Very few have ever restored one and timed it. If you do one thing from this page, ask your host to restore your store to a staging environment and tell you how long it took. The answer, and how comfortably they give it, tells you more about your hosting than any specification sheet.

    Want us to run the checklist against your store?

    We will do a free Peak Readiness Check: your Magento version and patch exposure, any credential files reachable from the web, security headers, and real-world mobile performance. You do not need to be a customer, there is nothing to install, and we will send you the result in plain English.

    EveryHost hosts Magento and Adobe Commerce on-premise, and nothing else. If you are weighing up a move before the freeze, the migration page sets out how we do it without downtime.