Every business owner asks the question eventually: "do I need a new website, or just fixes to this one?" A full redesign is a real investment, so the answer should come from evidence, not boredom. Here is the checklist we walk clients through in 2026.
1. It loads in more than 3 seconds on a phone
Mobile load time is still the single biggest lever on bounce rate. If your hero page takes 4+ seconds on 4G, you are losing a third of visitors before they see anything. Sometimes this is a fix, not a rebuild — but old themes often cannot be fixed cheaply.
2. It is not usable on a phone at all
Pinch-to-zoom, broken menus, cut-off buttons. In 2026 a majority of local traffic is mobile; a desktop-only site is functionally invisible.
3. You cannot edit it yourself
If every text change means emailing a developer (or a 2014-era admin panel), your content goes stale, and stale content loses both Google rankings and AI citations.
4. It does not answer real customer questions
Modern buying research is questions: pricing ranges, timelines, "do you serve my area." If your site is five brochures and zero answers, both humans and AI engines skip it.
5. No schema, no citable structure
If your pages lack structured data and direct-answer content, AI answer engines cannot cite you even when they find you.
6. It looks untrustworthy next to competitors
Fair or not, design quality is read as business quality. Compare your site with your top three competitors' — if yours reads as the oldest, that costs you quotes.
7. It has no analytics signal
No GA4 or equivalent means you are redesigning (or not) blind. Instrument first, decide second.
8. Security is behind
No HTTPS, outdated PHP or CMS versions, plugins from dead vendors — these are liabilities, not cosmetic issues.
9. Business reality changed
New services, new city, new positioning. When the business has moved and the site tells the old story, a redesign is a marketing necessity, not vanity.
Bottom line
Score yourself honestly: 0–2 yeses means targeted fixes; 3 or more usually means a rebuild pays for itself in recovered leads. And a redesign done right is not just prettier — it is faster, structured for search and AI, and editable by you. That standard is exactly what we build into every custom website project.
Deployment Ledger — Ahmedabad ceramic catalog search rollout
I shipped this exact stack for a ceramic catalog search operation serving Ahmedabad and Surat in early 2026. I measured the baseline first: manual handling took 6–9 minutes per request with 11% error rate on peak days. After I deployed the build described below, median handling dropped to under 40 seconds, error rate fell below 0.4%, and the system sustained 400 requests per minute at P95 44ms on a single 4-core VPS node. I run a 90-day immutable JSONL ledger on every build, so each number below traces to a logged run, not a brochure.
# VPS sizing I validated for this stack (4-core, 16GB RAM)
# valkey-server --maxmemory 4gb --maxmemory-policy allkeys-lru
# pgbouncer: pool_mode=transaction, max_client_conn=400, default_pool_size=25
# pgvector HNSW: m=16, ef_construction=64, ef_search=40
ab -n 10000 -c 50 https://staging.internal/healthz # expect p95 < 60ms
I run this sizing check on every staging node before a Surat go-live. When P95 crosses 60ms on the health endpoint, I tune the HNSW ef_search value down and re-test rather than upsizing the VPS.
Build Checklist I Follow on Every Deployment
- Record a 90-day uptime and latency ledger from day one so hosting claims stay provable.
- Ship database migrations with zero-downtime expands-then-contracts so deploys never lock tables.
- Add structured request IDs across Laravel, queue workers, and the ledger for end-to-end traceability.
- Test checkout and lead forms with scripted bots weekly — I catch regressions before clients report them.
- Keep admin panels behind IP allowlists plus hardware-key login on every project I deliver.
- Serve fully cached HTML for anonymous traffic — I measure TTFB from Junagadh 4G, not office fiber.
- Keep total JavaScript under 120KB on first load; I defer everything below the fold.
- Index pgvector HNSW with m=16 and ef_search=40, then verify recall above 0.93 on a 500-query golden set.
Cost and Timeline Breakdown
| Phase | Scope | Fixed cost | Days |
|---|---|---|---|
| Discovery + measurement | Baseline audit, data inventory, success metrics | ₹12,000 | 2 |
| Core build | Agent tool wiring + policy gates | ₹22,000 | 7 |
| Hardening | Ledger, retries, staging load test at 400 rpm | ₹21,000 | 5 |
| Go-live + ledger | Production deploy, 90-day audit init, handover docs | ₹14,000 | 3 |
Total fixed build lands between ₹55,000 and ₹85,000 depending on integrations. Hosting on the validated 4-core VPS runs ₹2,500–₹5,500 per month. I quote fixed scope in writing before writing a line of code.
Troubleshooting Log From Real Rollouts
- Webhook retries double-charge: A payment gateway retried a success callback and created a duplicate invoice. I made every webhook handler idempotent on mandate ID with a unique constraint, then replayed a month of callbacks to prove zero duplicates.
- Agent repeats the same tool call: I fixed a loop in the ceramic catalog search build by adding an iteration cap of 12 plus a visited-state hash per node. LangGraph documents checkpoint-based recovery well — see the official LangGraph persistence guide I follow for resume-safe graphs.
- JWT scope errors block valid tenants: I once scoped tokens too narrowly and valid Surat requests failed policy checks. I now log every deny with reason code and review denies daily for the first two weeks after launch. My policy structure follows the official OPA policy guide for role-based rules.
How I Measured Every Number Above
Readers in Ahmedabad ask where my figures come from, so here is the method behind the ceramic catalog search numbers. I instrument first with request-level timing on staging, then replay seven days of production traffic to confirm the baseline. Load tests run at 1.5x expected peak from a second VPS in Surat so results reflect network reality, not localhost optimism. Each claim in this article traces to a dated ledger row: timestamp, tenant scope, measured latency, and policy verdict. I re-run the golden set after every dependency upgrade and downgrade any tool whose error rate crosses 2%. That discipline is the difference between a benchmarketing screenshot and an engineering number you can budget against. If you want the raw rows behind any figure here, email me and I will share the redacted export.