D · Poor

Page SEO Inspection

https://www.myntra.com/
Crawled 16 Nov, 05:11 UTC (31 min ago)
HTTP 200 0 KB 59 ms TTFB
Download PDF

PDF export is a paid feature

A PDF of the full report, ready to send to a client or a colleague, comes with Basic at $19 a month and every plan above it, along with saved history. The report itself stays free to read.

See the plans

Analyse this page again?

This page was crawled 31 min ago. Running it again costs one report from your allowance, and a page that has not changed since will score the same.

On-Page Checklist 49% Complete
Primary focus: No viewport meta tag, so the page will render zoomed out on mobile and fail mobile usability. Fix now →
Filter:

Full diagnostics

Every check that ran, grouped by what it affects. Problems appear first in each group.

Meta Tags & Search Snippet Simulator

The tags that decide how this page is titled and described in search results.

! 1i 10% · needs work
Live snippet simulation
Title width: 154px / 580px
M Myntra.com www.myntra.com
Site Maintenance

No meta description, Google will generate a snippet from the page.

Meta description

The page has no meta description, so search engines will improvise the snippet.

How to fix
How to fix
<meta name="description" content="A 120 to 160 character summary with a clear call to action.">
Title tag 154px of 580px

The title is 16 characters. Short titles are fine, but there may be room to say more about what the page offers.

Rendered width

Desktop154px/ 580px
Mobile139px/ 920px

Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 16.

Crawling & indexing

Whether search engines can reach, read and index this page at all.

✕ 1! 7i 1✓ 847% · needs work
Viewport

No viewport meta tag, so the page will render zoomed out on mobile and fail mobile usability.

How to fix
How to fix
<meta name="viewport" content="width=device-width, initial-scale=1">
Canonical tag

No canonical tag, so duplicate URLs may compete with each other.

How to fix
How to fix
<link rel="canonical" href="https://www.myntra.com/">
Language

The html element has no lang attribute, which affects both search targeting and screen readers.

How to fix
How to fix
<html lang="en">
Character encoding

No character encoding is declared, so browsers must guess and may render text incorrectly.

How to fix
How to fix
<meta charset="utf-8">, as the first element in <head>.
robots.txt

No robots.txt was found. Crawlers will request it on every visit and receive an error.

How to fix
How to fix
Create https://www.myntra.com/robots.txt with at least:
User-agent: *
Allow: /
XML sitemap

No sitemap was found at /sitemap.xml, and robots.txt does not declare one.

https://www.myntra.com/sitemap.xml
How to fix
How to fix
Publish a sitemap and reference it from robots.txt:
Sitemap: https://www.myntra.com/sitemap.xml
Missing pages (404) HTTP 200

A page that does not exist returns HTTP 200. Search engines can index endless empty pages, and Search Console reports them as soft 404s.

https://www.myntra.com/wrp-missing-e26ba57370 answered HTTP 200
How to fix
How to fix
Make the server or the application return a 404 status for unknown addresses. The not-found page can look the same; only the status code has to change.
www and https versions 1 found

1 other spelling of this address does not lead here, so search engines can treat them as separate pages and split the ranking between them.

http://www.myntra.com/ answers HTTP 200 itself
How to fix
How to fix
Redirect every spelling (http and https, with and without www) to https://www.myntra.com/ with a single 301.
Favicon

No favicon is declared. Google shows one beside your result on mobile.

How to fix
How to fix
<link rel="icon" href="/favicon.svg" type="image/svg+xml">
HTTP status HTTP 200

The page returns 200 OK.

Redirect chain

The URL resolves without redirects.

Robots directives

No directive prevents indexing.

hreflang

No hreflang annotations, which is correct for a single-language page.

Mixed content

All resources load securely.

URL length 23 characters

The URL is 23 characters.

URL readability

The URL is clean and readable.

URL depth 0 levels deep

The page is 0 levels deep.

URL parameters

The URL has no query parameters.

Content & metadata

What the page says it is about, and how it reads.

! 1i 2✓ 457% · fair
Word count 8 Thin content
Headings 1 Little structure
H1 tags 1 Exactly one
Text ratio 12.4% Text vs markup
Heading outline 1 headings
H1 Oops! Something went wrong
Content length 8 words

The page has roughly 8 words, too little for search engines to tell what it is about.

How to fix
How to fix
Expand the page to answer the questions a reader arrives with.
Open Graph tags

Open Graph tags are incomplete: og:title, og:description, og:image missing.

Open Graph tags

Tag Status
og:title✕Missing
og:description✕Missing
og:image✕Missing
og:url✓Present
og:type✓Present
How to fix
How to fix
<meta property="og:image" content="https://example.com/share-1200x630.jpg">
Twitter card

No twitter:card tag, so shared links render as a small preview.

How to fix
How to fix
<meta name="twitter:card" content="summary_large_image">
H1 tag

The page has exactly one h1.

Oops! Something went wrong
Heading hierarchy

The heading outline descends in order.

Text-to-HTML ratio 12.4% text

Text is 12.4% of the page source.

Table headers

No data tables on this page, so there are no columns to label.

Keyword usage

The page has too little text for keyword analysis to mean anything.

AI & answer readiness

Whether answer engines and AI overviews can extract and trust this page.

i 5✓ 229% · needs work
AI crawlers n/a All allowed
Readable without JS Yes Served complete
Identity None No structured data
Quotable signals 0/4 Schema, date, author, answers
Answer readiness 0 found

No heading is followed by a concise 40 to 60 word answer, the shape featured snippets and AI overviews extract.

How to fix
How to fix
Open at least one section with a direct 40 to 60 word answer to the question its heading poses.
Content freshness

The page publishes no date. Not expected on a page like this; worth adding if its content goes out of date.

How to fix
How to fix
<time datetime="2026-09-17">17 September 2026</time>, or datePublished in Article structured data.
Attribution

Nothing on the page identifies who is behind it: no author, publisher, or about and contact links.

How to fix
How to fix
Add an author byline with Person structured data, and link to about and contact pages.
Answer schema

No structured data an answer engine can lift directly, such as FAQPage, HowTo or Article.

How to fix
How to fix
Mark up question-and-answer content as FAQPage, or step-by-step content as HowTo.
llms.txt for AI agents

No llms.txt. AI coding agents have no curated map of this site.

https://www.myntra.com/llms.txt returned nothing
How to fix
How to fix
A markdown file at /llms.txt listing your most useful pages with one-line descriptions. It does not affect how AI assistants cite you in answers, and nobody has shown that it does. What it helps is agents reading your documentation directly: Anthropic supports it, Perplexity uses it to choose pages, and Cursor, Continue and Cline navigate docs with it. Worth doing for a documentation or API site, and safe to skip otherwise.
Extractable structure

The page is too short to assess structure.

Entity identity

The page has no structured data, so there is no entity to check.

Readable without JavaScript

The page reads the same with and without JavaScript.

AI crawler access

No robots.txt, so no AI crawler is excluded by one.

Speed & delivery

What makes the page slow, and what the loading experience measures.

✕ 1! 4i 1✓ 545% · needs work
Rendered page
The page as it rendered on a mobile viewport during the performance test
Mobile, measured
The page as it rendered on a desktop viewport
Desktop, measured
LCP Poor
4.78s

Largest Contentful Paint

Target ≤ 2.5s

What this measures

How long until the largest thing on screen, usually the hero image, video or headline block, has finished rendering. It is a proxy for "when did this page feel loaded".

What moves it: Serve the hero image in a modern format at the size it is displayed, preload it, and remove render-blocking CSS and JavaScript ahead of it. A slow server response delays it too, so check TTFB first.

INP Needs work
381ms

Interaction to Next Paint

Target ≤ 200ms

What this measures

How long the page takes to respond visibly after a tap, click or key press, measured across every interaction, not just the first. High INP is what makes a page feel unresponsive even once it looks ready.

What moves it: Break up long JavaScript tasks so the main thread is free to respond, defer work that is not needed for the interaction, and avoid large re-renders on every event.

CLS Needs work
0.2

Cumulative Layout Shift

Target ≤ 0.1

What this measures

How much visible content jumps around while the page loads. This is what makes someone tap the wrong thing because a banner or image pushed the layout down underneath their finger.

What moves it: Give images and video explicit width and height so the browser reserves the space, reserve room for ads and embeds, and avoid inserting content above what is already on screen.

FCP Needs work
2.34s

First Contentful Paint

Target ≤ 1.8s

What this measures

How long until anything at all appears, the first text or image painted. It separates "the page starts slowly" from "the biggest element is slow": a fast FCP with a slow LCP points at the hero, while both slow points at the server.

What moves it: Cut render-blocking CSS and JavaScript in the head, inline the styles needed for the first screen, and improve the server response time.

TTFB Needs work
1605ms

Real-user response time

Target ≤ 800ms

What this measures

How long real visitors waited for the first byte of the response, the 75th percentile across everyone who actually loaded the page, not a single test from one location.

What moves it: Cache the response at the edge, host closer to your visitors, and reduce the work done before the first byte is sent, database queries, template rendering and third-party calls.

Compression

The HTML is served uncompressed. Gzip or Brotli typically cuts it by 70%.

How to fix
How to fix
Enable Brotli or gzip compression for text responses.
Render-blocking resources 0 found

0 render-blocking resources in the head.

HTML size 0 KB

The HTML document is 0 KB.

Deprecated tags

No deprecated HTML tags are used.

Inline styles 0 found

0 inline style attributes.

Page weight 1 requests · 1 KB

The page loads 1 requests totalling 1 KB.

What loaded, by type

Type RequestsTransferred
document11 KB

Of these, 0 requests (0 KB) come from third-party domains.

Security

Transport security, reputation and the response headers that protect visitors.

! 1i 6✓ 646% · needs work
Clickjacking protection

Nothing prevents this page being embedded in a frame, which allows clickjacking.

How to fix
How to fix
Content-Security-Policy: frame-ancestors 'self'
MIME sniffing

No X-Content-Type-Options header, so browsers may guess a resource type and execute it.

How to fix
How to fix
X-Content-Type-Options: nosniff
Referrer policy

No Referrer-Policy header, so full URLs may leak to third-party sites.

How to fix
How to fix
Referrer-Policy: strict-origin-when-cross-origin
Content Security Policy

No Content-Security-Policy, the main defence against cross-site scripting.

How to fix
How to fix
Content-Security-Policy: default-src 'self'
Permissions policy

No Permissions-Policy header, so any script or embed on the page may ask for the camera, microphone or location.

How to fix
How to fix
Permissions-Policy: camera=(), microphone=(), geolocation=()
Version disclosure

Response headers disclose exact software versions, which helps an attacker target known vulnerabilities.

server: Apache/2.4.1 (Unix)
How to fix
How to fix
Suppress version numbers from Server and X-Powered-By, and remove the version from the generator meta tag (in WordPress, a one-line filter or most security plugins).
security.txt

No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.

https://www.myntra.com/.well-known/security.txt
How to fix
How to fix
Publish /.well-known/security.txt with a Contact: line (an email address or a form) and an Expires: date.
Email addresses in the page

No email addresses are written into the page for harvesting bots to collect.

HSTS

HTTPS is enforced with Strict-Transport-Security.

max-age=15768000 ; includeSubDomains
Cookie flags

The page sets no cookies, so there are none to expose.

TLS certificate 40 days left

The TLS certificate is valid for another 40 days, issued by GlobalSign nv-sa.

40 days remaining
Google Web Risk

Not listed by Google Web Risk for malware, phishing or unwanted software.

TLS version TLS 1.3

Connections use TLS 1.3.

Server & domain

The server and the domain behind the page: protocol, network, registration and email records.

✓ 7100% · excellent
HTTP/2 HTTP/2

Served over HTTP/2, which loads a page's files in parallel over one connection.

CDN Akamai

Served through Akamai, a CDN, so visitors get the page from a server near them.

Domain expiry 1853 days left

myntra.com is registered until 13 Dec 2031 with GoDaddy.com, LLC.

1853 days remaining
Domain age 19 years old

myntra.com was registered on 13 Dec 2006, 19 years ago. Age is not a ranking factor, but an established name is one buyers and partners look for.

IPv6

www.myntra.com has an IPv6 address, so IPv6-only networks reach it directly.

SPF record

myntra.com publishes an SPF record: v=spf1 ip4:148.139.0.0/16 ip4:149.96.0.0/16 ip4:199.91.136.0/21 ip4:103.23.64.0/22 ip4:37.98.232.0/21 include:sendclean.net include:eu._netblocks.mimecast.com include:_spf.google.com include:_spf1.myntra.com include:_spf2.myntra.com include:amazonses.com include:spf.falconide.com -all

DMARC policy

myntra.com has a DMARC policy of quarantine.

ads.txt

No ad network loads on this page, so ads.txt is not needed.

Links, media & schema

Links, images and structured data.

i 10% · needs work
Social share preview From this page's Open Graph tags
Structured data

The page has no structured data, so it cannot qualify for rich results.

How to fix
How to fix
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","headline":"…"}</script>
Links

The page contains no links.

Images

The page contains no images.

Links

No links were available to check.

What to fix first

Ranked by impact against effort, the top of this list buys the most for the least work.

1
✕ Critical No viewport meta tag, so the page will render zoomed out on mobile and fail mobile usability.
<meta name="viewport" content="width=device-width, initial-scale=1">
quick fix
2
✕ Critical Largest Contentful Paint is 4.8s (real-user data), above the 2.5s target and in the poor range.
Optimise the hero image, remove render-blocking CSS and JS, and improve server response time.
moderate
3
! Recommended The page has no meta description, so search engines will improvise the snippet.
<meta name="description" content="A 120 to 160 character summary with a clear call to action.">
quick fix
4
! Recommended The HTML is served uncompressed. Gzip or Brotli typically cuts it by 70%.
Enable Brotli or gzip compression for text responses.
quick fix
5
! Recommended 1 other spelling of this address does not lead here, so search engines can treat them as separate pages and split the ranking between them.
Redirect every spelling (http and https, with and without www) to https://www.myntra.com/ with a single 301.
quick fix
6
! Recommended Real users wait 1605ms for the first byte, above the 800ms target.
Cache at the edge, move hosting closer to visitors, or cut server work before the first byte.
moderate
7
! Recommended No canonical tag, so duplicate URLs may compete with each other.
<link rel="canonical" href="https://www.myntra.com/">
quick fix
8
! Recommended No character encoding is declared, so browsers must guess and may render text incorrectly.
<meta charset="utf-8">, as the first element in <head>.
quick fix
9
! Recommended Nothing prevents this page being embedded in a frame, which allows clickjacking.
Content-Security-Policy: frame-ancestors 'self'
quick fix
10
! Recommended No sitemap was found at /sitemap.xml, and robots.txt does not declare one.
Publish a sitemap and reference it from robots.txt: Sitemap: https://www.myntra.com/sitemap.xml
quick fix
11
! Recommended A page that does not exist returns HTTP 200. Search engines can index endless empty pages, and Search Console reports them as soft 404s.
Make the server or the application return a 404 status for unknown addresses. The not-found page can look the same; only the status code has to change.
quick fix
12
! Recommended Cumulative Layout Shift is 0.200 (real-user data), above the 0.1 target.
Set width and height on images, reserve space for ads and embeds, and preload webfonts.
quick fix

Score breakdown

How each area scored. Categories that could not be measured are excluded rather than counted as zero.

Indexability & Crawling38 checks · 17 issues
9
On-Page Content & Structure15 checks · 9 issues
71
Core Web Vitals11 checks · 6 issues
38
Schema & Rich Snippets1 checks · 1 issue
98
Media & LinksNot assessed
n/a
Overall scoreGrade D · 32/73 passed
43