Website review, no card needed
ampm.in website review
Visit site (opens in a new tab)Reviewed 20 October 202640 issues · 76 checks
This review found 40 issues worth fixing on ampm.in, 19 of them high impact, across 76 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
69D- #101,552 of 118,152 reviewed websitesbeats 12%
- #61,630 of 67,126 online storesbeats 7%
- #56,972 of 61,204 Shopify storesbeats 6%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 2.9 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 137 ms |
| May 9, 2026 | 139 ms |
| May 16, 2026 | 140 ms |
| May 23, 2026 | 137 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 139 ms |
| Jul 4, 2026 | 147 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 132 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 131 ms |
| Aug 15, 2026 | 140 ms |
| Aug 22, 2026 | 140 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 112 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 116 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 127 ms |
| Oct 10, 2026 | 138 ms |
| Oct 17, 2026 | 137 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
8.2 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.2 s faster on a phone.
Main-thread work: 13.5 s
A phone's processor spends 13.5 s on main-thread work while loading, 7.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Avoid multiple page redirects
1.2 sThe page goes through 1 redirect before it starts loading, costing about 1.2 s. Link and advertise the final URL directly.
Mobile performance score: 1
1/100Your mobile performance score is 1 (desktop: 15). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 536 ms. During a long task the page ignores taps.
Google Tag Manager adds 92 ms
92 msGoogle Tag Manager costs a phone 92 ms of main-thread work and 469 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.
Reduce unused CSS
150 ms · 83 KiBAbout 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Bootstrap CDN and others), adding 863 KiB and 127 ms of main-thread time.
Minify JavaScript
150 ms · 25 KiB25 KiB could be saved by minifying JavaScript.
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
1 checks passed
Server response: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 9.3 s
9.3 sThe first text or image appears after 9.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 26.0 s
26.0 sYour largest element takes 26.0 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 16.4 s
16.4 sVisually, the page fills in at 16.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 46.6 s
46.6 sThe page becomes fully interactive after 46.6 s. Good is under 3.8 s.
Total Blocking Time: 3.4 s
3.4 sScripts block taps and scrolling for 3.4 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.885
0.885The layout shifts by 0.885 while loading, so content jumps under the reader's thumb. Good is under 0.1.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 137 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 162 ms
162 msReal visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 430 ms
430 msReal visitors wait 430 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 7.5 MB in 614 requests
7.5 MBYour homepage downloads 7.5 MB in 614 requests on a phone: scripts 4.5 MB (250), other files 1.4 MB (278) and HTML 665 KiB (7). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Mobile_Banner_53b73ebf-99f6-4238-9ea3-7a3dcfea7ca8.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
8 images in older formats
8 images (752 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
4 images far larger than shown
296 KiB4 images are downloaded at several times the size a phone draws them, for example Mobile_Banner_53b73ebf-99f6-4238-9ea3-7a3dcfea7ca8.webp at 2,000 px wide, shown at 390 px. Resized copies would save about 296 KiB.
4 images below the first screen load straight away
4 images further down the page (166 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.12 g of CO₂e: 254.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
11 links crawlers can't follow
11 links have no real href, so search engines can't follow them.
86 internal links, 4 external
The homepage links to 86 pages on ampm.in and 4 external pages.
7 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “AMPM is India's luxury designer fashion house. Explore our dresses, suits, kurtas, jackets & more. ✓Free Shipping ✓Easy…”.
Title: 54 characters
Your title is a healthy 54 characters: “AMPM- Luxury Designer Clothing & Accessories for Women”.
Canonical URL set
The canonical URL is https://ampm.in/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://ampm.in/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
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.
llms.txt published
The site publishes https://ampm.in/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://ampm.in/collections/anarkali-suits/sale, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
https://ampm.in/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://ampm.in/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://ampm.in/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
11 links to non-canonical URLs
Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://ampm.in/collections/designer-dresses/sale, whose canonical is https://ampm.in/collections/designer-dresses. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages without an H1
https://ampm.in/customer_authentication/redirect, https://ampm.in/collections/women-shirts-tops/sale, https://ampm.in/collections/women-kurtas/sale, https://ampm.in/collections/women-jackets/sale and https://ampm.in/collections/ladies-bags/sale have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.
1 checks passed
Titles are unique
Every page we checked has its own title.
Best practices
12 small tap targets
12 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “gtag is not defined”.
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.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 104 words
The homepage has only about 104 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Get in touch” and “Track your order”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.
26 cookies set on arrival
26Opening the homepage sets 26 cookies, 7 of them by other companies (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.
43 other companies contacted
Loading the homepage contacts 43 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 ampm.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
Hiring
- Hiring
- 2 open roles
- Teams
- Operations (1), Sales (1)
- Job board
- greenhouse
- Careers page
- boards.greenhouse.io/ampm (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on ampm.in, including 13 speed issues, 2 SEO issues and 4 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.