Energy company website: surviving the first blackout day

Demand in this niche behaves unlike any other. It does not grow gradually — it flares up. Scheduled outages are announced, and within hours the number of people searching for a generator or a solar system multiplies. That is the day an energy company website earns more than in the previous month — or goes down and earns nothing. Let us look at how to prepare for peak days in advance.

What the demand spike looks like

The distinctive feature is speed rather than volume. Demand does not warm up over weeks: news about outage schedules appears in the evening, and within an hour people are opening websites and calling. The next day is the same, then the wave subsides.

Three consequences worth understanding in advance. First: the traffic arrives all at once rather than evenly, so average hosting figures tell you nothing. Second: people search from a phone at that moment, often on mobile data that is also overloaded. Third: decisions are made fast — if your site does not open within three seconds, the person moves to the next one.

So the question "will the site hold" really means "will you lose the most valuable traffic of the year".

Why a template energy company website falls over at peak

The reason is technical and simple. A typical site on a heavy template with a dozen plugins builds every page from scratch on every request: it queries the database, assembles the menu, pulls the catalog, renders the blocks. With ten visitors that is imperceptible; with five hundred at once the server starts waiting on itself.

Add uncompressed images, third-party chat and pixel scripts, video on the home page — and you get a page weighing several megabytes that mobile data on a peak evening simply cannot pull.

The solution is not buying more expensive hosting but making sure pages are not assembled from scratch every time.

Caching: the main thing that saves a peak day

The idea is simple: the page is built once and then served ready-made, with no database calls. To a regular visitor there is no difference, while the server handles dozens of times more people on the same hardware.

What should always be cached: the home page, solution and kit pages, the catalog, articles. What must not be cached: the cart, the account, forms, calculator results — those are individual.

Invalidation deserves separate attention. Change a price in the admin panel and that page's cache must clear automatically, otherwise the client sees yesterday's figure. It is configured once and then works by itself.

Mobile speed: what actually matters

On a peak evening you compete not only with other companies but with an overloaded mobile network. So page weight matters more than usual.

The practical minimum: images in a modern format, compressed and lazy-loaded; fonts served locally rather than from someone else's server; third-party scripts — chat, analytics, pixels — loaded after the main content; no autoplay video on the first screen.

The benchmark: the first screen with a price and an enquiry button should appear within one or two seconds on mobile data. Checking is easy: open the site from a phone tethered to another phone in data-saving mode.

What to show on the first screen during peak days

Someone arriving in the evening during outages will not read about the company's advantages. They have three questions: what is in stock, what does it cost, and when will you deliver.

So for the peak it is worth switching on a separate home page mode: an "in stock, delivery tomorrow" block with specific models and prices, a short load-based selector, phone and messenger as a large button. Everything else moves down.

Technically this is done as a seasonal block with dates or a toggle in the admin panel, so nobody has to rebuild the home page by hand each time. We wrote about seasonal block mechanics in tyre-fitting season: preparing the site — the logic is identical, only the trigger differs.

Availability and reservation: how the peak ends

On a peak day the winner is not whoever is cheaper but whoever has stock now. So availability must be visible and truthful: "in stock", "last N", "to order, N days".

The second part is the ability to secure the item immediately. Reservation with a small deposit via LiqPay or Monobank closes the decision at the moment the person is ready. Without it you get an enquiry, call in the morning — and they have already bought elsewhere.

And third: if the item is out of stock, do not stay silent. A "notify me when available" form collects contacts from those who came during the peak and gives you a base for the next wave.

Telephony and handling enquiries

The site held, enquiries came in — and here the second bottleneck appears. On a peak day managers physically cannot keep up, and every missed call is a lost client.

What helps: a call queue with a waiting message instead of a busy tone; automatic logging of missed calls into a callback list; a Viber or Telegram bot doing the initial load-based selection and collecting a contact; prepared answers to typical questions.

The bot is not a toy here: at peak it removes half of the identical "what is in stock" and "how much for a house" questions from the managers.

What to do before the season rather than during it

Preparation takes a few days, but it has to happen in advance — during the peak it is already too late. A practical list.

Check mobile speed and remove heavy elements. Switch caching on and verify that price changes clear it. Prepare an availability block with real items. Set up a peak-day home page mode. Connect reservation with a deposit. Configure call tracking and a call queue. Verify the hosting survives load — a simple test answers that within an hour.

And separately: prepare advertising campaigns in advance so all that remains is switching them on. At peak, bids soar, and the winner is whoever is already set up rather than whoever starts configuring.

After the peak: what most companies skip

The wave subsides and companies return to normal, forgetting the most valuable thing — the base of everyone who visited.

People who enquired during the peak but did not buy have not disappeared: some postponed the decision, some could not find the money immediately. Two or three weeks later an email or message with instalment terms and a calculation brings back a noticeable share of them.

The second group is those who did buy. For them there is service, maintenance, expanding the system with batteries. Those are sales that cost nothing in acquisition. How to measure the return on such repeat business and on the site overall is described in how to calculate a website's return.

What the energy company site itself includes is collected on the page about solar and generator company website development, and how to build a calculation that brings enquiries is in the solar calculator article.

Advertising on peak days: when to switch on and where to send traffic

In the first days of outages auction bids soar: every competitor switches campaigns on at once. The winner is not whoever has the bigger budget but whoever prepared everything in advance.

In practice that means campaigns, ads and landing pages built in summer and sitting switched off. On the peak day you press one button rather than starting to configure while competitors are already showing.

Traffic should go to the availability or kit page with prices, not the home page. And enquiries and calls must be passed to analytics as conversions — otherwise the system optimises for clicks, and on peak days that is the most expensive mistake possible.

Frequently asked questions

Will an energy company website survive a peak on ordinary hosting?

It depends less on the plan than on how the site is built. A light site with caching handles dozens of times more people on ordinary hosting than a heavy template on an expensive server. First remove the excess and switch caching on, and only then, if the load really is large, consider a more powerful server.

How do we check peak readiness in advance?

Two ways. Technically — with a load test: we simulate several hundred simultaneous visitors and see where the site starts to lag. Practically — open the home page and a kit page from a phone on weak mobile data: if the price and button take more than three seconds, the peak will be worse.

Do we need a separate home page mode for peak days?

Not necessarily a separate design — an availability block with prices that switches on at the top with one button in the admin panel is enough. The point is that a person immediately sees what is in stock and when it arrives rather than scrolling past a section about company advantages.

What if an item sells out right during the peak?

Do not hide it; change the status and add a "notify me when available" button. That way you collect contacts instead of losing visitors. And state the delivery time honestly: people are willing to wait when they know exactly how long.

How long does preparing the site for the season take?

If the site is built properly — a few days: caching, image compression, an availability block, reservations. If the site sits on a heavy template and already lags, optimisation or a new site comes first, and that is 2–4 weeks. Which is why preparation belongs in summer rather than October.

In short

An energy company website lives off two or three peak days a season, and those are exactly what to prepare for in advance. Caching so pages are not rebuilt every time; a light mobile version opening in a second; an availability block with prices on the first screen; reservation with a deposit; a call queue and a bot for initial questions. And after the peak — go back to those who enquired and did not buy: those are the cheapest sales you will ever make.