Website review, no card needed
dagga.in website review
Visit site (opens in a new tab)Reviewed 7 November 202641 issues · 75 checks
This review found 41 issues worth fixing on dagga.in, 12 of them high impact, across 75 checks. The most urgent: mobile performance score: 48. 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
63D- #118,026 of 124,300 reviewed websitesbeats 4%
- #68,295 of 69,848 online storesbeats 2%
- #62,395 of 63,521 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (cloudfront.net, Google Tag Manager and Facebook and others), adding 2.0 MB and 1.8 s of main-thread time.
cloudfront.net adds 952 ms
952 mscloudfront.net costs a phone 952 ms of main-thread work and 1.2 MB 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 JavaScript
300 ms · 698 KiBAbout 698 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 296 ms
296 msGoogle Tag Manager costs a phone 296 ms of main-thread work and 402 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.
Use efficient cache lifetimes
276 KiB4 files are served with short cache lifetimes, so returning visitors download them again (276 KiB).
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 256 ms. During a long task the page ignores taps.
2,121 HTML elements
The page has 2,121 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
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: 358 ms
358 msYour server sent the HTML in 358 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 9.9 s
9.9 sVisually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.4 s
13.4 sThe page becomes fully interactive after 13.4 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.408
0.408The layout shifts by 0.408 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 735 ms
735 msScripts block taps and scrolling for 735 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 3.0 s
3.0 sYour largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “undefined__undefined”. Most of its time is resource load delay (1.6 s).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.1 MB in 95 requests
2.1 MBYour homepage downloads 2.1 MB in 95 requests on a phone: scripts 1.4 MB (44), images 390 KiB (16) and other files 185 KiB (31). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 71.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
20 buttons without a name
20 buttons have no accessible name, so screen readers announce just “button”.
Hidden but focusable
27 elements hidden from screen readers can still receive keyboard focus.
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (32 elements)
All page content should be contained by landmarks: 32 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 105 images in the HTML carry an alt attribute.
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 7 failed. 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (171 characters)
Your meta description is 171 characters; Google truncates after about 160, so the end of your pitch is cut.
45 internal links, 3 external
The homepage links to 45 pages on dagga.in and 3 external pages.
4 checks passed
Title: 46 characters
Your title is a healthy 46 characters: “DAGGA | Genuine Leather Shoes for Men in India”.
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.
XML sitemap found
Your XML sitemap is reachable at https://dagga.in/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
Some text only appears after JavaScript runs
49%The HTML your server sends has 264 of the 536 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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://dagga.in/llms.txt (3 KiB, 16 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a title
https://dagga.in/orders and https://dagga.in/bag have no <title>, so Google invents the link text in results.
8 pages share 4 titles
https://dagga.in/SHOES/collection/RXdJbS50 and https://dagga.in/collection/RXdJbS50 all use the title “SHOES for Men | Genuine Leather Footwear | DAGGA”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://dagga.in/orders and https://dagga.in/bag have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages share a meta description
https://dagga.in/SHOES/collection/RXdJbS50 and https://dagga.in/collection/RXdJbS50 use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://dagga.in/orders, https://dagga.in/bag, https://dagga.in/Aston-Black-Perforated-Leather-Oxford-Shoes-for-Men-%E2%80%93-Office/catalogue/LSU8oTsA/VU1Zhqqw, https://dagga.in/Vero-Black-Oxford-Brogue-Casual-Cum-Formal-Leather-Shoes-For/catalogue/8-Shh2Ov/Yl4cFRm6, https://dagga.in/Imperial-Black-Wholecut-Brogue-Genuine-Leather-Shoes-%E2%80%93-Formal-Oxfords/catalogue/BP6ltbPT/sEjhCBa_ and https://dagga.in/Windsor-Black-Double-Monk---Genuine-Leather-Shoes-For/catalogue/tQfc12vD/lO_CFAAk have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://dagga.in/orders and https://dagga.in/bag have 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.
3 pages slow to respond
https://dagga.in/Imperial-Black-Wholecut-Brogue-Genuine-Leather-Shoes-%E2%80%93-Formal-Oxfords/catalogue/BP6ltbPT/sEjhCBa_, https://dagga.in/Windsor-Black-Double-Monk---Genuine-Leather-Shoes-For/catalogue/tQfc12vD/lO_CFAAk and https://dagga.in/NEW-ARRIVALS/collection/TmSPBSG- took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistrations')”.
2 checks passed
Tap targets are thumb-sized
109 of 134 tappable elements near the top are at least 24 px.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 49 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 536 words of copy
The homepage carries about 536 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
23 other companies contacted
Loading the homepage contacts 23 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 dagga.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- 10 Shopify Products;Shopify;Shopify Plus
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on dagga.in, including 14 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.