digi.ai.in
← digi.ai.in / blog
2026-08-099 min readHiring a studio

What We Check Before We Ever Touch Code

Before writing code, we verify SEO groundwork, performance budgets, accessibility, browser compatibility, and India-specific data law compliance.

·

Before we write a single line of code for a website or app, we run through a fixed set of checks covering SEO groundwork, performance budgets, accessibility, browser compatibility, and India-specific legal requirements. This isn't paperwork for its own sake — skipping any one of these categories tends to show up later as rework, a failed audit, or a launch delay.

·

This post lays out what's actually in that pre-code review, why each item matters, and what's specific to building for the Indian market.

+

There's no agreed checklist length — only agreed categories

·

If you look across the industry, the exact number of pre-launch checks varies enormously. One agency lists 49 things to do before a website launch, another condenses it to 28 things to check before you launch your site. A third source breaks the whole process into five phases, starting with a review of page layouts, proofread copy, optimized images, and required legal pages before any technical or SEO work begins.

·

The number of items doesn't matter much. What matters is that every credible checklist, regardless of length, covers the same core categories: technical setup, design QA, SEO, compliance, and performance. As one 2026 guide puts it, a proper pre-launch process "covers technical setup, design QA, SEO, compliance, and performance to ensure the site functions properly and supports long-term growth". We use that as our own frame: five buckets, checked before code, not after.

+

Technical and SEO groundwork

·

A site can look finished and still be invisible to search engines or broken for real users. Before we consider a build code-complete, we confirm:

·
+

Performance: Core Web Vitals aren't optional

·

Google defines Core Web Vitals as "the subset of Web Vitals that apply to all web pages, should be measured by all site owners, and will be surfaced across all Google tools". Each metric — Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) — represents a distinct facet of how a real person experiences a page loading and responding.

·

These aren't abstract scores. Google's own performance documentation cites measurable business results: QuintoAndar increased year-over-year conversions by 36% by improving INP by 80%, and Disney+ Hotstar increased weekly card views by 100% on living room devices by reducing INP by 61%. That's the kind of number that should change how a founder thinks about performance — it's not a developer nicety, it's a conversion lever.

·

The current numeric targets, per a secondary source citing web.dev, are:

·
Metric Target
LCP Within 2.5 seconds
INP 200 milliseconds or less
CLS 0.1 or less
·

These figures come from brilliant.digital's 2026 summary of web.dev's thresholds. Google periodically revises these numbers, so we treat this table as a starting point and verify it directly against web.dev before setting a project's performance budget.

·

We set these thresholds as budgets before design and development start — not as an afterthought QA gate. That means image weight, font-loading strategy, and third-party script count get decided at the planning stage, not retrofitted after launch when a client asks why the site feels sluggish.

+

Accessibility: WCAG as the reference standard

·

The W3C's Web Content Accessibility Guidelines (WCAG) are the standard we check builds against, even though — as covered below — India doesn't mandate this for private-sector sites. WCAG has evolved in layers:

·

The U.S. Access Board summarizes the scale of additions across versions: WCAG 2.2 adds nine new Success Criteria to WCAG 2.1, which added 17 Success Criteria to WCAG 2.0.

·

Worth being direct about: no source we found establishes a binding Indian legal requirement for WCAG conformance on private commercial websites. It's a voluntary international best-practice standard here, not an enforced regulation. We still check against it because it's the closest thing to an agreed baseline for usable, robust markup — and because clients selling into government or enterprise contracts sometimes get asked for WCAG conformance as a procurement condition even without a general legal mandate.

+

Cross-browser and device compatibility

·

MDN frames this plainly: "Cross-browser testing is the practice of ensuring that a website works across various browsers and devices", including older browsers that lack full JavaScript or CSS support, and the full range of device classes a real audience uses.

·

MDN's guidance on legacy support also recommends testing a bare, CSS-less version of a page to confirm the fallback experience remains accessible — a useful sanity check for what happens when a script fails to load or a stylesheet doesn't render as expected on a low-end Android device, which is still a meaningful share of the Indian market.

+

What's specific to building for India

·

This is the layer most Western checklists skip entirely, and it's the part we spend the most deliberate time on with Indian clients.

·

The timeline matters and is commonly misunderstood. The Act was passed in 2023, but MeitY notified the Digital Personal Data Protection Rules 2025 only on 13 November 2025, following a ten-month wait since the draft Rules were released. Full compliance is expected by 13 May 2027. "The law exists" and "the law is enforceable" are two different dates — a distinction clients often conflate, assuming that because the Act passed in 2023, they're either already compliant or already exposed. Neither is quite right; the operative Rules only just landed.

·

Practically, the Rules require that data fiduciaries provide clear and concise privacy notices specifying purpose of processing, categories of data processed, retention periods, and mechanisms to withdraw consent. We treat this as a pre-code gate for any build that collects user data — forms, logins, checkout, analytics — because retrofitting consent flows and data-retention logic after launch is far more expensive than designing for it from the start.

·

This isn't a hypothetical risk. A PwC India audit found that 41% of websites of Indian enterprises analysed specified data principal rights in their privacy policies, while only 9% of organisations sought consent that was free, specific and informed. Most existing Indian business websites would already fail a DPDP-readiness review. That's a strong argument for building consent and data-handling logic in from day one on a new project, rather than treating it as a policy-page afterthought.

·

Hosting location. For clients in regulated sectors, hosting choice carries specific weight. MeitY's cloud empanelment framework requires that cloud services offered are hosted within India and that data is limited within the boundaries of India, and private sector organizations in regulated industries, like financial services and telecommunications, frequently adopt its guidelines even without a strict legal obligation to do so. If a client operates in finance, insurance, or telecom, we ask about hosting jurisdiction before we ask about hosting price.

·

Intermediary rules. Separately, the Information Technology Rules 2021 were developed jointly by MeitY and the Ministry of Information and Broadcasting, with intermediaries required to comply by 25 May 2021. Relevant for any build with user-generated content, comments, or a marketplace component.

+

A working checklist

·

Here's the condensed version of what we run through before code, organized by the categories above rather than by item count:

·
  • SEO groundwork: sitemap submitted, robots.txt clean, indexing confirmed, analytics installed
  • Functional basics: SSL active, forms tested, redirects working
  • Performance budget: LCP, INP, and CLS targets set before design begins, verified against current web.dev thresholds
  • Accessibility: WCAG 2.1 or 2.2 conformance level agreed with the client, especially if the site will be used in procurement or government-adjacent contexts
  • Cross-browser and cross-device: fallback experience checked with CSS stripped
  • Data protection: privacy notice drafted with purpose, retention, and consent-withdrawal mechanisms per DPDP Rules 2025
  • Hosting: jurisdiction confirmed against MeitY empanelment guidance if the client is in a regulated sector
  • Content moderation: IT Rules 2021 obligations checked if the site accepts user-generated content
·

None of this replaces good judgment on a specific project. But it does mean the conversation about data handling, performance targets, and accessibility happens before a design file is opened — not after a client asks why the site is slow, or a lawyer asks why the privacy notice doesn't mention retention periods.

+

Questions people also ask

+

Does WCAG accessibility compliance is legally required in India?

·

No source we reviewed establishes a binding Indian legal mandate for private-sector websites to meet WCAG. It functions as a voluntary international best-practice standard rather than an enforced regulation, though it's frequently required in government and enterprise procurement.

+

Is the Digital Personal Data Protection Act already enforceable?

·

The Act was passed in 2023, but the operative Rules were only notified on 13 November 2025, with full compliance expected by 13 May 2027. So the law exists, but the compliance clock and its enforcement machinery are only now becoming operational.

+

What are the current Core Web Vitals thresholds?

·

Per a 2026 industry summary of web.dev's guidance: LCP within 2.5 seconds, INP at 200 milliseconds or less, and CLS at 0.1 or less. Google revises these periodically, so it's worth checking web.dev's Core Web Vitals page directly before finalizing a performance budget.

Written by the studio behind digi.ai.in. Questions? hi@digi.ai.in or WhatsApp +91 98605 96905
WhatsApp us