The window is already open
Independence Day has just gone. Thiruvonam sits at the end of this month. For a Kerala business that sells, books, or takes enquiries online, that is not a branding season. It is a short stretch where people actually look at the site on a phone, often in a hurry, often after a WhatsApp forward, and they will not wait for a slider.
This is the wrong fortnight to redesign the homepage. It is the right fortnight to make the pages that take money or messages tell the truth and load. Hours, stock, contact, and speed on those URLs. Everything else — a new palette, a new story, a festival skin that hides the phone number — can wait until September, when you can see what actually broke.
If you have ten working days, spend them on the list below. If you have three, do hours, contact, and the payment or enquiry URL. A prettier hero will not save a closed-on-Onam page that still says “open today”, and it will not save a checkout that hitchs when the chat widget loads.
Hours that match the door
Write the hours the way a person in a car would use them. Festival weeks are not your April hours. If the counter is shut on Thiruvonam and open the Sunday after, the site must say that on the contact page, the footer, and any “visit us” block that still claims 9–6. A Google Business hour that disagrees with the site is a second lie. Fix both or fix neither — disagreement is worse than a missing line.
If you take orders for pickup, say the last order time, not only the shop hours. If you deliver, say the cutoff and the places you will not reach that week. People forgive a closed day they can see. They do not forgive a form that accepted an order you cannot fill.
Put the exception in a sentence at the top of the page that already ranks — not in a popup the phone user will dismiss into the wrong branch. A banner that says “Closed 26 Aug; orders resume 27 Aug, 10 a.m.” is enough. A festive animation that covers the sentence is not.
If different branches have different hours, do not hide that in a PDF. One page, one list, names a person in Kochi would recognise. If you cannot maintain three branches on one page, you are not ready for three landing pages either. Tell the truth on one URL first.
Stock you will not sell
If the site shows items, hide or mark what you will not have. A “buy” on an empty SKU during Onam is not optimism. It is a queue of angry calls. If stock lives in a sheet, update the sheet before you update the banner. If stock lives in a system, make sure the site reads it. A static product page from June is a trap in August.
If you cannot do live stock, do a human sentence: “Popular packs may sell out; WhatsApp us before you travel.” That is uglier than a green badge. It is also honest. Honesty converts better than a checkout that fails after the OTP.
Pre-orders need a date you will keep. “After Onam” is not a date. If you will ship in the first week of September, write that. If you will not take pre-orders, take the button off. A disabled button that still submits is the worst of both.
Gift and hamper pages are where this goes wrong first. They are built in a rush, they clone last year’s copy, and they still list a tin you cannot buy. Walk the page with the person who packs the box. If they laugh, take the SKU down. The walk is an hour. The refunds are not.
Contact that a phone can finish
The click-to-call number must be the number that rings. Not a missed-call hunting line that nobody picks up after 7 p.m., unless you say so. WhatsApp, if you use it, should be a link that opens a chat with a starter sentence, not an image of a QR code that a desktop user cannot use and a phone user has to pinch.
Forms should ask for less this fortnight. Name, phone, what they want, when they can be called. A twelve-field “get in touch” that demands a company GSTIN will be abandoned in a relative’s house on a mid-range Android. You can ask for the GSTIN when a human calls back.
If the form emails a mailbox nobody will open on Saturday, route it to the phone that will. A ticket that sits until Tuesday is a lost Onam order. Test the form on Tuesday this week from a network that is not the office. If the success page says “we will reply in one business day” and you mean “after the festival”, change the sentence.
Maps and pins: one correct pin. A second pin from 2018 that drops people at the old gate is how you get a one-star week. Drive the link yourself. If you moved, the old embed is a defect, not nostalgia.
Speed on the money URLs
Money URLs are checkout, booking, pay-now, and the enquiry page you actually use. They are not the blog and they are not the animated festival landing you are tempted to ship. Those money URLs should stay fast on a phone in traffic. The usual killers are a chat bubble, a tag manager, a map on every page, and a hero video. Load those after the first paint, or drop them for a fortnight. A 40 KB widget is still a busy main thread when someone taps Pay.
Images: the real size they display, width and height set, not a 4 MB PNG of a sadhya. Festival photography is where LCP dies. Compress before you publish. If you cannot compress in time, use fewer photographs. One sharp pack shot beats a carousel that jumps the “Pay” button. That jump is CLS, and it is how people tap the wrong thing.
Field data, not office fibre. Search Console’s Core Web Vitals report, mobile, on the URLs that already get impressions. If you do not know which those are, you are not ready to redesign anything. Read Core Web Vitals explained and fix the poor money URL first. A lab 100 on the homepage does not save a red checkout.
Hosting and cache should already be boring: compression on, static files cached, the server close to users. If the site is still on a crowded plan in another continent, this is not a CSS problem. It is a host problem. You may not migrate in ten days. You can still stop shipping new weight onto that host this week.
Payments, OTP, and the back button
If you take cards or UPI, run a live payment of a small amount on Tuesday, on a phone, on a network that is not the office. Complete it. Fail it on purpose. Use the back button. See whether the order exists twice, exists zero times, or exists in a state nobody in the shop can name. Festival traffic will do all three of those if you have not.
OTP pages time out. Say what to do when they do. A spinner that never returns is a support call you will not staff on Thiruvonam. If the gateway needs a whitelist of return URLs, check them after the last deploy. A new www versus non-www is enough to break the return. That is a slash problem dressed as a payment problem.
Do not launch a new gateway this week unless the old one is already dead. A new integration is a project. This fortnight is for the integration you already have to tell the truth.
What not to ship
A redesign. A new menu that hides Contact. A festival microsite with no link back to hours. A popup that asks for email before the phone number is visible. A slider of eight campaign images on the page that used to load in two seconds. A chat vendor who wants to “go live before Onam” and has not been on a Kerala phone.
Do not publish a blog series instead of fixing the footer. Do not buy a week of ads onto a URL you have not opened on mobile. Do not migrate WordPress to something else in this window because a vendor had a slot. Migration is a September job, after you have notes on what failed.
Do not let a designer “just update the banner” by replacing a sized image with an unsized one. That is how a stable page becomes a shifting page. If they must change the banner, keep the dimensions and compress the file. Brand is allowed. Layout shift is not.
A week you can actually run
- Walk the money URLs and the contact page on a mid-range Android, not on office Wi-Fi.
- Write festival hours and cutoffs. Match the door, the site, and the Business Profile.
- Take down or mark stock you will not sell. Walk hampers with the person who packs.
- Send a test enquiry and a test payment. Confirm who sees them on Saturday.
- Kill or defer chat, maps-on-every-page, and the heaviest hero on those URLs.
- Set image dimensions. Compress what you just uploaded.
- Write a one-line banner for closed days. No animation on top of it.
That is web development as operations, not as a campaign. If you need help, ask for this list, not for a new look. A new look is a project with a definition of done. This list is a definition of “we will not embarrass ourselves next week”.
After the festival
Leave the honest hours up until they are wrong again. Do not snap back to “9–6 daily” on the 28th if you are still on stock take. Keep the money URLs thin. The chat widget can stay off if the phone already rings. Look at Search Console in September for the URLs that took the traffic. Those are next year’s list, written by users rather than by a moodboard.
Write down what failed: the form that sat, the SKU you forgot, the pin, the OTP, the page that jumped. That note is worth more than a retrospective slide. It is also the brief for a real site improvement when the house is no longer full. Festival traffic is a load test you did not schedule. Treat the results as data, not as a reason to redesign in a panic on 27 August.
If the site is really a web application people work in — packing, billing, slot changes — do not judge it by a Lighthouse score this week. Judge it by whether staff invent a sheet beside it because the screen was slow or wrong. Fix that query. The public page and the packing screen can share a brand. They do not share this punch-list.