I Audited 10 Delhi NCR Business Websites in One Evening. 8 Had the Same 3 Bugs.
Your competitor sits above you on Google and you assume they earned it. Paid some agency 2 lakhs, hired an SEO guy, did something you don't know about....
Garvit Sharma
14 June 2026 · 6 MIN READ
I Audited 10 Delhi NCR Business Websites in One Evening. 8 Had the Same 3 Bugs.
webight.comOn this page
Your competitor sits above you on Google and you assume they earned it. Paid some agency 2 lakhs, hired an SEO guy, did something you don't know about. You've opened their site, scrolled for a minute, felt the sting, closed the tab.
Last Thursday I did the opposite. I opened 10 of those sites and read the source code instead of the homepage. Dentists, interior designers, two CA firms, a gym, a wedding photographer, a coaching centre. All Delhi NCR. All businesses sitting on page one or two when you search their category plus "Noida" or "Gurgaon". One evening, zero paid tools.
8 of the 10 had the same 3 bugs.
That number should make you happy. Here is the one idea I want you to take from this post: the businesses ranking around you are running broken websites, and they have no idea. The bar in local search is lying on the floor. Stepping over it takes a weekend.
What I checked
Three things per site, roughly 12 minutes each.
- View page source, look at the metadata.
- The sitemap at /sitemap.xml.
- PageSpeed Insights on mobile.
No crawler. No paid SEO suite. Nothing a non-technical owner couldn't repeat, and at the end of this post I'll give you the exact steps so you can run it on your own site tonight.
Bug 1: metadata that stops at a title
Open the source of most of these sites and the head section is basically this:
<title>Home</title>
That's it. 7 of the 10 had no meta description at all. Open Graph tags were even rarer.
Two things break because of this. First, Google has nothing to show under your name in search results, so it scrapes random text from the page. Sometimes that text is your cookie notice. Your one chance to pitch a searcher, and a robot is writing it by grabbing whatever it finds.
Second, and in NCR this one matters more: WhatsApp. Business here moves through shared links. Someone forwards your site to a friend, and without Open Graph tags it lands as a naked blue URL. No preview image, no pitch line. People judge the link before they tap it. A bare URL from an unknown number gets ignored. A card with a clean image and a clear line gets opened.
The fix is a few lines in the head of every page. Copy this, replace the placeholder text, done:
<title>Interior Designer in Noida | Studio Name</title>
<meta name="description" content="Residential and office interiors across Noida and Greater Noida. Fixed quotes, fixed timelines, no surprises." />
<meta property="og:title" content="Interior Designer in Noida | Studio Name" />
<meta property="og:description" content="Residential and office interiors across Noida and Greater Noida." />
<meta property="og:image" content="https://yourdomain.com/og-cover.jpg" />
<meta property="og:url" content="https://yourdomain.com/" />
<link rel="canonical" href="https://yourdomain.com/" />
If your site is on WordPress, a free plugin like Yoast writes these fields for you. There is no excuse at any budget.
Bug 2: the sitemap is missing or lying
Type /sitemap.xml after the domain. On several of these sites it returned a 404. On others the sitemap loaded fine but listed pages that themselves returned 404s. Dead URLs sitting in the exact file Google reads to understand your site.
Before you laugh at these businesses, listen to this. In June I audited webight.com, my own studio's site. I found 12 deleted case-study URLs still sitting in our sitemap, and canonicals pointing to webight.com while the server 307-redirects everything to www.webight.com. I build websites for a living and that rot still crept in. Sitemaps decay silently. Nobody opens them after launch day. That is exactly why your competitors' sitemaps are broken right now and will stay broken.
See, the sitemap is the list of pages you are asking Google to index. If it's missing, Google guesses. If it's lying, Google spends its limited crawl visits on dead pages and trusts your site a little less each time. Neither problem announces itself. Your traffic just quietly stays smaller than it should be, for years.
Bug 3: mobile load over 8 seconds
This was the ugly one. On the mobile PageSpeed test, the slowest of the 10 took 13.7 seconds to show its main content. The causes repeated across sites: hero images uploaded straight off a phone camera, auto-playing sliders, page builders loading plugin after plugin, fonts pulled from two different CDNs on the same page.
8 seconds on a phone is an eternity. The visitor came from an Instagram tap or a WhatsApp forward. They give you 2, maybe 3 seconds of blank screen before the back gesture. Every rupee that business spent getting the click is burned in that gap.
And the fixes are usually small. My own homepage had a 4,190ms render delay on the hero headline because an opacity animation waited for JavaScript hydration before showing anything. I swapped it for a pure CSS animation, a simple translateY, nothing that waits for JavaScript, and the delay dropped to 382ms. One change, 11x faster on the most important element of the page. For a client, Zulal, I took the PageSpeed score from 39 to 77. I did that one free, for goodwill, and they stayed on retainer after. The score difference reads like months of work. It never is.
Why everyone ships the same three mistakes
These 10 sites came from different builders, different budgets, different years. The bugs are identical because the process is identical: install a template, swap the content, send the invoice. The metadata fields stay empty because the template shipped with them empty. The sitemap is whatever the plugin generated in 2022. The images go up at whatever size the owner emailed.
Psychology has a name for this: the default effect. People stick with whatever came out of the box, even when changing it costs almost nothing. The owner checks the site once, on launch day, on their own phone, looking at colours and photos. All three bugs are invisible to that check. So nothing gets flagged, nothing gets fixed, and the same builder ships the same defaults to the next 50 businesses.
That is the entire opportunity. You are competing against defaults. Fix three invisible things and you are suddenly in a race against the 2 sites out of 10 that bothered.
Run this on your own site tonight
You need a laptop, Chrome, and about 20 minutes. No developer.
Step 1: read your own metadata. Open your homepage, right click, View Page Source, press Ctrl+F and search for "description". If nothing comes up, you have bug 1. Then paste your homepage link into a WhatsApp chat with yourself. No preview card means the same thing.
Step 2: open your sitemap. Type yourdomain.com/sitemap.xml in the address bar. A 404 is bug 2. If it loads, click 5 random URLs from inside it. Any dead link is also bug 2.
Step 3: run the mobile speed test. Go to pagespeed.web.dev, enter your domain, and read the Mobile tab, never the Desktop one. If the page shows its main content after 4 seconds you are losing people. After 8, you have bug 3.
Step 4: ask Google what it has. Search site:yourdomain.com. Deleted pages still showing, or garbage text under your links: both are evidence of bugs 1 and 2.
Screenshot every failure and send it to whoever built or maintains your site. None of these takes more than a day to fix. If they tell you otherwise, that tells you something about them.
So pick an evening this week, run the four steps on your site, then run them on your top three competitors. If you find what I found, you will stop believing the businesses above you on Google are unbeatable, because you will have read their source code and seen how thin the lead actually is.
If you run the audit and something in the results confuses you, send it to me. I reply.
We build custom platforms, websites, and automation.
The two people who build it are the two you talk to, and every price is on the page.

Garvit Sharma
Full-stack developer and co-founder of Webight, a two-person web and AI studio in India. He writes these from real client work. More about us.
Keep reading
// RELATEDA Client Paid 3 Agencies for SEO Before Me. None of Them Opened the Website Code.
webight.comA Client Paid 3 Agencies for SEO Before Me. None of Them Opened the Website Code.
7 MIN READ
One Cloudflare Worker Saved My Client's App When Supabase Got Blocked. It Also Cut TTFB in Half.
webight.comOne Cloudflare Worker Saved My Client's App When Supabase Got Blocked. It Also Cut TTFB in Half.
6 MIN READ
The Contact Form Setup That Stopped Landing in Spam. Resend, Next.js, DKIM.
webight.comThe Contact Form Setup That Stopped Landing in Spam. Resend, Next.js, DKIM.
6 MIN READ