Website review, no card needed
mcdindia.com website review
Visit site (opens in a new tab)Reviewed 26 October 202639 issues · 86 checks
This review found 39 issues worth fixing on mcdindia.com, 19 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.4 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.7 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 188 ms |
| May 16, 2026 | 186 ms |
| May 23, 2026 | 189 ms |
| May 30, 2026 | 190 ms |
| Jun 6, 2026 | 190 ms |
| Jun 13, 2026 | 191 ms |
| Jun 20, 2026 | 191 ms |
| Jun 27, 2026 | 190 ms |
| Jul 4, 2026 | 193 ms |
| Jul 11, 2026 | 192 ms |
| Jul 18, 2026 | 192 ms |
| Jul 25, 2026 | 192 ms |
| Aug 1, 2026 | 190 ms |
| Aug 8, 2026 | 191 ms |
| Aug 15, 2026 | 193 ms |
| Aug 22, 2026 | 193 ms |
| Aug 29, 2026 | 194 ms |
| Sep 5, 2026 | 192 ms |
| Sep 12, 2026 | 186 ms |
| Sep 19, 2026 | 182 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 177 ms |
| Oct 10, 2026 | 177 ms |
| Oct 17, 2026 | 178 ms |
| Oct 24, 2026 | 178 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
2.7 s · 765 KiBAbout 765 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Render-blocking requests
2.1 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Main-thread work: 16.4 s
A phone's processor spends 16.4 s on main-thread work while loading, 10.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
1.2 s · 166 KiBAbout 166 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Google CDN adds 1.2 s
1.2 sGoogle CDN costs a phone 1.2 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 9
9/100Your mobile performance score is 9 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8,490 HTML elements
The page has 8,490 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 third-party services on the page
7 third-party services load with your homepage (Google CDN, Google Tag Manager and GoDaddy and others), adding 1.6 MB and 2.1 s of main-thread time.
Improve image delivery
150 ms · 543 KiB2 images could be 543 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Google Tag Manager adds 505 ms
505 msGoogle Tag Manager costs a phone 505 ms of main-thread work and 341 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 380 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
300 ms · 42 KiB7 files are served with short cache lifetimes, so returning visitors download them again (42 KiB).
Minify JavaScript
150 ms · 9 KiB9 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 3 KiB3 KiB could be saved by minifying CSS.
Phones get a much slower page than desktops
Desktop scores 58 but mobile only 9. A gap that wide usually means heavy scripts and images that hit phones hardest.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 0.68
0.68For real visitors the layout shifts by 0.68 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 11.8 s
11.8 sYour largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 14.8 s
14.8 sThe page becomes fully interactive after 14.8 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.628
0.628The layout shifts by 0.628 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 188 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 193 ms
193 msReal visitors wait 193 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 594 ms
594 msReal visitors wait 594 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.2 MB in 100 requests
4.2 MBYour homepage downloads 4.2 MB in 100 requests on a phone: images 1.7 MB (29), scripts 1.7 MB (32) and other files 367 KiB (12). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.20 g of CO₂e: 143.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
All page content should be contained by landmarks (54 elements)
All page content should be contained by landmarks: 54 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 22 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
21 H1 headlines
There are 21 <h1> headlines (“Summer, served chilled. Your summer sip awaits at…”, “Buddy Meal Grab a Meal for Two 🤜🤛” and “HURRY UP! Fun awaits in your Happy Meal”). One clear main headline is easier for people and search engines.
Meta description is long (161 characters)
Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
33 internal links, 337 external
The homepage links to 33 pages on mcdindia.com and 337 external pages.
5 checks passed
Title: 57 characters
Your title is a healthy 57 characters: “McDonald's® India - Delivering Happiness to Your Doorstep”.
Canonical URL set
The canonical URL is https://mcdindia.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://mcdindia.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://mcdindia.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (9,288 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages are broken
Your homepage links to https://mcdindia.com/558,%20Newslive%20Building,%20GS%20Road,%20Christian%20Basti,%20Dispur,, https://mcdindia.com/Near%20Guru%20Harkrishan%20Public%20School%20at%20Punjabi%20Bagh and https://mcdindia.com/Km%20stone%20172+RHS,%20Block%203A,%20Delhi%20-%20Mumbai%20Expressway, which answer with an error. Visitors hit a dead end and search engines drop them.
11 pages without a meta description
https://mcdindia.com/birthday-page, https://mcdindia.com/mccafe, https://mcdindia.com/mfy, https://mcdindia.com/mcdonalds-india-north-east-strikes-a-chord-with-its-new-campaign-we-get-it, https://mcdindia.com/artists-come-together-to-create-unique-compositions-for-fast-food-giant and https://mcdindia.com/im-lovin-it-live and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page with very little text
https://mcdindia.com/nutritional-information has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Loading the font 'data:application/x-font-ttf;charset=utf-8;base64,AAEAAAALAIAAAwAwT1MvMg8SB/AAAAC8AAAAYGNtYXDV1NUQAAAB…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,685 words of copy
The homepage carries about 1,685 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Download Nutritional Info”, “Order now” and “Subscribe”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 319 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mcdindia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2021.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on mcdindia.com, including 21 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.