Website review, no card needed
fo2.in website review
Visit site (opens in a new tab)Reviewed 6 November 202624 issues · 69 checks
This review found 24 issues worth fixing on fo2.in, 9 of them high impact, across 69 checks. The most urgent: fails Core Web Vitals for real visitors. 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.7 s |
| May 23, 2026 | 4.6 s |
| May 30, 2026 | 4.6 s |
| Jun 6, 2026 | 4.6 s |
| Jun 13, 2026 | 4.6 s |
| Jun 20, 2026 | 4.6 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 4.8 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.6 s |
| Aug 1, 2026 | 4.6 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.7 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 4.9 s |
| Sep 19, 2026 | 4.9 s |
| Sep 26, 2026 | 5.0 s |
| Oct 3, 2026 | 5.1 s |
| Oct 10, 2026 | 5.2 s |
| Oct 17, 2026 | 5.2 s |
| Oct 24, 2026 | 5.1 s |
| Oct 31, 2026 | 5.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 130 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 129 ms |
| Jun 6, 2026 | 128 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 127 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 126 ms |
| Aug 1, 2026 | 126 ms |
| Aug 8, 2026 | 125 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 125 ms |
| Aug 29, 2026 | 126 ms |
| Sep 5, 2026 | 127 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 128 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 127 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
Render-blocking requests
750 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 61 ms. During a long task the page ignores taps.
Reduce unused JavaScript
51 KiBAbout 51 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
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.
2 third-party services on the page
2 third-party services load with your homepage (Google Fonts and Amazon Web Services), adding 5 KiB and 0 ms of main-thread time.
3 checks passed
Mobile performance score: 97
97/100Your mobile performance score is 97. That is in Google's “good” band (90 and up).
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 643 ms of it running JavaScript. That is comfortably low.
Server response: 442 ms
442 msYour server sent the HTML in 442 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 LCP: 5.1 s
5.1 sReal visitors wait 5.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 130 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.7 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 128 ms
128 msReal visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Time to Interactive: 2.7 s
2.7 sThe page is fully interactive after 2.7 s.
Largest Contentful Paint: 1.8 s
1.8 sYour largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Instant Camera | Official Distributor”.
Cumulative Layout Shift: 0.016
0.016The layout barely moves while loading (CLS 0.016, good is under 0.1).
Total Blocking Time: 6 ms
6 msScripts block the page for only 6 ms while loading. Good is under 200 ms.
Images and page weight
About 0.06 g of CO₂ per visit
0.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.06 g of CO₂e: 7.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 228 KiB in 23 requests
228 KiBYour homepage downloads 228 KiB in 23 requests on a phone: scripts 170 KiB (9), HTML 51 KiB (1) and images 5 KiB (10). That is a lean page.
Accessibility
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
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.
16 links without text
16 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. 3 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.
Canonical points to another host
Your canonical URL points to fo2.in, not mydukaan.io, so Google may credit that host instead.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (304 characters)
Your meta description is 304 characters; Google truncates after about 160, so the end of your pitch is cut.
46 internal links, 14 external
The homepage links to 46 pages on fo2.in and 14 external pages.
4 checks passed
Title: 49 characters
Your title is a healthy 49 characters: “India's Exclusive Online Camera Store & Community”.
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://mydukaan.io/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.
No llms.txt
There is no https://mydukaan.io/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 (390 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://mydukaan.io/fo2/collections and https://mydukaan.io/fo2/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.
1 page with very little text
https://mydukaan.io/fo2/collections 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 and read each the way a search engine does.
6 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.
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 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://dukaan-core-file-service.s3.ap-southeast-1.amazonaws.com/upload_file_service/eaae2ae3-90a9-43b2-8b92-049ef2b649e1/f-1.png.
15 small tap targets
15 of 58 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fonts.googleapis.com/css2?family=GalanoGrotesque:wght@400;700&display=swap' from o…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
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 372 words of copy
The homepage carries about 372 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start shopping”.
2 calls to action
The homepage has 2 calls to action, for example “Subscribe” and “Start shopping”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 fo2.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
- Next.js
- Hosting
- Growthpond Technology Pvt Ltd
Hiring
- Hiring
- 4 open roles
- Job board
- careers page
- Careers page
- mydukaan.io/careers (opens in a new tab)
Company
- Headquarters
- House
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on fo2.in, including 8 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.