Website review, no card needed

cropel.in logo

cropel.in website review

Visit site (opens in a new tab)Reviewed 21 November 202639 issues · 77 checks

This review found 39 issues worth fixing on cropel.in, 14 of them high impact, across 77 checks. The most urgent: improve image delivery. 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 cropel.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cropel.in at 0.5 s0.5 s
  2. cropel.in at 1.0 s1.0 s
  3. cropel.in at 1.5 s1.5 s
  4. cropel.in at 2.0 s2.0 s
  5. cropel.in at 2.5 s2.5 s
  6. cropel.in at 3.0 s3.0 s
  7. cropel.in at 3.5 s3.5 s
  8. cropel.in at 4.0 s4.0 s

Speed

6 to fix57
  • Improve image delivery

    8.8 s · 4.2 MB

    26 images could be 4.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.8 s faster on a phone.

  • Render-blocking requests

    3.1 s

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

  • Use efficient cache lifetimes

    1.8 s · 788 KiB

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

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    300 ms · 69 KiB

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

  • Font display

    300 ms

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

  • Reduce unused JavaScript

    150 ms · 26 KiB

    About 26 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (JSDelivr CDN, flaticon.com and Google Fonts), adding 106 KiB and 9 ms of main-thread time.

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 116 ms of it running JavaScript. That is comfortably low.

  • Server response: 245 ms

    245 ms

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

Core Web Vitals

6 to fix55
  • Largest Contentful Paint: 27.5 s

    27.5 s

    Your largest element takes 27.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NUMBER OF COUNTRIES GLOBALLY EXPORT + NUMBER OF TEAM MEMBER…”.

  • Time to Interactive: 28.6 s

    28.6 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • 41 images without width and height

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

  • Cumulative Layout Shift: 0.189

    0.189

    The layout shifts by 0.189 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 2.3 s

    2.3 s

    The first text or image appears after 2.3 s on a phone. Good is under 1.8 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
  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 7.1 MB in 74 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 74 requests on a phone: images 6.6 MB (41), fonts 258 KiB (8) and scripts 140 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 18 images far larger than shown

    1.6 MB

    18 images are downloaded at several times the size a phone draws them, for example home-about-banner.jpg at 1,542 px wide, shown at 313 px. Resized copies would save about 1.6 MB.

  • 1 image over 500 KB

    home-about-banner.jpg weighs 568 KiB. On a phone connection a single image that size takes seconds.

  • 24 images in older formats

    24 images (4.7 MB) 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.

  • 18 images below the first screen load straight away

    18 images further down the page (3.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.0 g of CO₂ per visit

    2.03 g

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

Accessibility

8 to fixGoogle 7285
  • 12 buttons without a name

    12 buttons have no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

  • 3 tap targets too small

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

  • 10 images without alt text

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 25 links without text

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

  • 6 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 32 automated accessibility rules passed

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

SEO

4 to fixGoogle 8387
  • 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.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 41 internal links, 12 external

    The homepage links to 41 pages on cropel.in and 12 external pages.

5 checks passed
  • Meta description: 105 characters

    Your meta description is 105 characters: “A best clean, modern, stylish, creative, responsive theme for different eCommerce business or industries.”.

  • One H1 headline

    Your main headline reads: “About Us”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Cropel International Pvt. Ltd.”.

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

AI search readiness

1 to fix88
  • 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://cropel.in/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 (534 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 8 pages share a title

    /, https://cropel.in/about-us.php, https://cropel.in/product.php, https://cropel.in/gallery.php, https://cropel.in/certificate.php and https://cropel.in/blog.php and 2 others all use the title “Cropel International Pvt. Ltd.”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    https://cropel.in/about-us.php, https://cropel.in/product.php, https://cropel.in/gallery.php, https://cropel.in/certificate.php, https://cropel.in/blog.php and https://cropel.in/contact.php and 1 other use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://cropel.in/product.php, https://cropel.in/gallery.php, https://cropel.in/certificate.php, https://cropel.in/blog.php and https://cropel.in/quality-policy.php have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://cropel.in/gallery.php and https://cropel.in/certificate.php 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.

  • 7 internal pages checked

    We fetched 7 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 7 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 7 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 7 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9283
  • 9 small tap targets

    9 of 11 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 null (reading 'querySelectorAll')”.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 447 words of visible text.

3 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact”, “Contact Us” and “Contact Details”.

  • 1 short form

    A short form (6 fields at most) is right on the homepage, asking for an email.

  • Direct contact links

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

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.

  • 4 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2023.

Stack

Framework
jQuery
Hosting
Hostinger

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on cropel.in, including 12 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

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