Website review, no card needed

ecommfy.com logo

ecommfy.com website review

Visit site (opens in a new tab)Reviewed 10 November 202637 issues · 82 checks

This review found 37 issues worth fixing on ecommfy.com, 14 of them high impact, across 82 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of ecommfy.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ecommfy.com at 1.2 s1.2 s
  2. ecommfy.com at 2.4 s2.4 s
  3. ecommfy.com at 3.5 s3.5 s
  4. ecommfy.com at 4.7 s4.7 s
  5. ecommfy.com at 5.9 s5.9 s
  6. ecommfy.com at 7.1 s7.1 s
  7. ecommfy.com at 8.3 s8.3 s
  8. ecommfy.com at 9.5 s9.5 s

Speed

12 to fix48
  • Render-blocking requests

    8.3 s

    16 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.3 s.

  • Reduce unused JavaScript

    3.7 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.

  • Reduce unused CSS

    1.3 s · 298 KiB

    About 298 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.3 s faster on a phone.

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.8 s

    A phone's processor spends 4.8 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Minify JavaScript

    840 ms · 181 KiB

    181 KiB could be saved by minifying JavaScript.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 1.6 MB and 840 ms of main-thread time.

  • Use efficient cache lifetimes

    955 KiB

    30 files are served with short cache lifetimes, so returning visitors download them again (955 KiB).

  • Font display

    650 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).

  • Google CDN adds 352 ms

    352 ms

    Google CDN costs a phone 352 ms of main-thread work and 743 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.

  • Google Tag Manager adds 305 ms

    305 ms

    Google Tag Manager costs a phone 305 ms of main-thread work and 574 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.

  • 1,901 HTML elements

    The page has 1,901 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 17 long tasks on the main thread

    17 long tasks block the main thread while loading, the longest for 112 ms. During a long task the page ignores taps.

  • Improve image delivery

    111 KiB

    7 images could be 111 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    90 ms · 21 KiB

    21 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    39 KiB

    Polyfills for old browsers add 39 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.

  • 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: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix58
  • First Contentful Paint: 8.1 s

    8.1 s

    The first text or image appears after 8.1 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 12.6 s

    12.6 s

    Your largest element takes 12.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Creating eCommerce Of Today And Tomorrow Start your online …”.

  • Time to Interactive: 27.3 s

    27.3 s

    The page becomes fully interactive after 27.3 s. Good is under 3.8 s.

  • Speed Index: 14.2 s

    14.2 s

    Visually, the page fills in at 14.2 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 310 ms

    310 ms

    Scripts block taps and scrolling for 310 ms in total while the page loads. Good is under 200 ms.

  • 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
  • Cumulative Layout Shift: 0.071

    0.071

    The layout barely moves while loading (CLS 0.071, good is under 0.1).

Images and page weight

3 to fix53
  • Page weight: 5.7 MB in 114 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 114 requests on a phone: scripts 2.4 MB (26), images 1.3 MB (54) and other files 1.3 MB (17). Under 2 MB keeps phones on slow connections fast.

  • 16 images below the first screen load straight away

    16 images further down the page (627 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    17 KiB

    1 image is downloaded at several times the size a phone draws it, for example support.webp at 1,255 px wide, shown at 369 px. Resized copies would save about 17 KiB.

  • 9 images in older formats

    9 images (431 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.

  • About 1.6 g of CO₂ per visit

    1.61 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.61 g of CO₂e: 192.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

9 to fixGoogle 8989
  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • All page content should be contained by landmarks (22 elements)

    All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails 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.

  • 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 46 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • 3 H1 headlines

    There are 3 <h1> headlines (“Creating eCommerce Of Today And Tomorrow”, “Creating eCommerce Of Today And Tomorrow” and “Creating eCommerce Of Today And Tomorrow”). One clear main headline is easier for people and search engines.

  • 35 internal links, 7 external

    The homepage links to 35 pages on ecommfy.com and 7 external pages.

7 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “eCommfy is a B2B and B2C eCommerce platform built using latest technologies to create capable and influential eCommerce…”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “eCommfy - Best eCommerce platform in Jaipur”.

  • Canonical URL set

    The canonical URL is https://www.ecommfy.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://www.ecommfy.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.ecommfy.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.

3 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,546 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    https://www.ecommfy.com/contact-us and https://www.ecommfy.com/[site_url]/contact-us all use the title “Contact us”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.ecommfy.com/contact-us and https://www.ecommfy.com/[site_url]/contact-us use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.ecommfy.com/[site_url]/contact-us, whose canonical is https://www.ecommfy.com/contact-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 13 pages without an H1

    https://www.ecommfy.com/contact-us, https://www.ecommfy.com/pricing, https://www.ecommfy.com/blogs, https://www.ecommfy.com/about-us, https://www.ecommfy.com/[site_url]/contact-us and https://www.ecommfy.com/food-drink-franchises-sell-d2c and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.ecommfy.com/blogs took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9287
  • 3 small tap targets

    3 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 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 'backdrop')”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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,586 words of copy

    The homepage carries about 1,586 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us” and “Schedule a call”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Contact us”, “Pricing” and “Contact Us”.

  • 4 short forms

    4 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 12 customer or partner logos and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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

    10

    Opening the homepage sets 10 cookies, 1 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.

  • 10 other companies contacted

    Loading the homepage contacts 10 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 ecommfy.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

Company

Founded
2016

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on ecommfy.com, including 17 speed issues and 1 SEO issue. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25