Website review, no card needed

crazybulk.in logo

crazybulk.in website review

Visit site (opens in a new tab)Reviewed 16 November 202644 issues · 94 checks

This review found 44 issues worth fixing on crazybulk.in, 14 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
3.9 s1.5 sMay 30Nov 142.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.6 s
Jun 6, 20262.2 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.1 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.2 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.2 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.3 s
Oct 3, 20262.9 s
Oct 10, 20262.6 s
Oct 17, 20263.6 s
Oct 24, 20263.6 s
Oct 31, 20261.8 s
Nov 7, 20262.2 s
Nov 14, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
149 ms112 msMay 30Nov 14132 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026123 ms
Jun 6, 2026119 ms
Jun 13, 2026121 ms
Jun 20, 2026123 ms
Jun 27, 2026119 ms
Jul 4, 2026119 ms
Jul 11, 2026118 ms
Jul 18, 2026119 ms
Jul 25, 2026120 ms
Aug 1, 2026116 ms
Aug 8, 2026116 ms
Aug 15, 2026116 ms
Aug 22, 2026120 ms
Aug 29, 2026130 ms
Sep 5, 2026132 ms
Sep 12, 2026140 ms
Sep 19, 2026145 ms
Sep 26, 2026136 ms
Oct 3, 2026141 ms
Oct 10, 2026126 ms
Oct 17, 2026126 ms
Oct 24, 2026130 ms
Nov 14, 2026132 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

Full-page screenshot of crazybulk.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. crazybulk.in at 4.4 s4.4 s
  2. crazybulk.in at 8.7 s8.7 s
  3. crazybulk.in at 13.1 s13.1 s
  4. crazybulk.in at 17.5 s17.5 s
  5. crazybulk.in at 21.9 s21.9 s
  6. crazybulk.in at 26.2 s26.2 s
  7. crazybulk.in at 30.6 s30.6 s
  8. crazybulk.in at 35.0 s35.0 s

Speed

12 to fix49
  • Reduce unused JavaScript

    2.4 s · 751 KiB

    About 751 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Use efficient cache lifetimes

    2.5 s · 548 KiB

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

  • Mobile performance score: 49

    49/100

    Your mobile performance score is 49. 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 (Shopify, razorpay.com and Facebook and others), adding 2.7 MB and 1.1 s of main-thread time.

  • Improve image delivery

    450 ms · 240 KiB

    13 images could be 240 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 116 KiB

    About 116 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Legacy JavaScript

    450 ms · 62 KiB

    Polyfills for old browsers add 62 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

  • Main-thread work: 3.5 s

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

  • Shopify adds 230 ms

    230 ms

    Shopify costs a phone 230 ms of main-thread work and 1.0 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.

  • Render-blocking requests

    300 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • razorpay.com adds 198 ms

    198 ms

    razorpay.com costs a phone 198 ms of main-thread work and 815 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,944 HTML elements

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

  • 10 long tasks on the main thread

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

  • Minify JavaScript

    53 KiB

    53 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

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

    6 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 15.7 s

    15.7 s

    Your largest element takes 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 20.2 s

    20.2 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • Total Blocking Time: 535 ms

    535 ms

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

  • 41 images without width and height

    41 images have no width and height attributes, so the layout jumps as each one loads.

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 123 ms to 132 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.9 s

    1.9 s

    Real visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 522 ms

    522 ms

    Real visitors wait 522 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.9 MB in 443 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 443 requests on a phone: scripts 1.8 MB (80), other files 1.7 MB (251) and images 843 KiB (69). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

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

  • About 1.4 g of CO₂ per visit

    1.38 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 7887
  • 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.

  • 11 images without alt text

    11 images have no alt text, which hurts accessibility and image search.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

  • 33 links without text

    33 visible links have no text or label, so screen readers cannot say where they go.

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

5 to fixGoogle 7768
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (12 characters)

    Your title is only 12 characters: “CrazyBulk.in”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.crazybulk.in/search?q={search_term_string}")”.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 66 internal links, 49 external

    The homepage links to 66 pages on crazybulk.in and 49 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.crazybulk.in/.

  • 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.crazybulk.in/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.crazybulk.in/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 8 pages without a meta description

    https://www.crazybulk.in/pages/offers, https://www.crazybulk.in/blogs/testimonials, https://www.crazybulk.in/collections/man-boobs, https://www.crazybulk.in/pages/social-pr, https://www.crazybulk.in/blogs/news and https://www.crazybulk.in/collections/all and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.crazybulk.in/collections/stacks, https://www.crazybulk.in/collections/women, https://www.crazybulk.in/pages/social-pr, https://www.crazybulk.in/collections/bulking, https://www.crazybulk.in/collections/strength and https://www.crazybulk.in/collections/cutting 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 27 found) and read each the way a search engine does.

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

  • 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

3 to fixGoogle 6588
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    30 of 31 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 41 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

5 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Track Your Order”, “Buy Now” and “SHOP THE ENTIRE RANGE”.

  • 9 short forms

    9 short forms (1 field at most) are right on the homepage.

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 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.

  • 26 other companies contacted

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

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

contlo.com · bvcservices.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on crazybulk.in, including 18 speed issues, 5 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

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