Website review, no card needed

abcfruits.net logo

abcfruits.net website review

Visit site (opens in a new tab)Reviewed 7 November 202639 issues · 81 checks

This review found 39 issues worth fixing on abcfruits.net, 21 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
2.9 s2.1 sMay 16Sep 262.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.8 s
May 30, 20262.7 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.5 s
Jun 27, 20262.6 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.3 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
238 ms150 msMay 16Sep 26228 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026160 ms
May 23, 2026171 ms
May 30, 2026179 ms
Jun 6, 2026179 ms
Jun 13, 2026185 ms
Jun 20, 2026182 ms
Jun 27, 2026180 ms
Jul 4, 2026188 ms
Jul 11, 2026176 ms
Jul 18, 2026179 ms
Jul 25, 2026185 ms
Aug 1, 2026182 ms
Aug 8, 2026186 ms
Aug 15, 2026181 ms
Aug 22, 2026186 ms
Aug 29, 2026193 ms
Sep 5, 2026203 ms
Sep 12, 2026226 ms
Sep 19, 2026228 ms
Sep 26, 2026228 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 abcfruits.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abcfruits.net at 1.6 s1.6 s
  2. abcfruits.net at 3.1 s3.1 s
  3. abcfruits.net at 4.7 s4.7 s
  4. abcfruits.net at 6.3 s6.3 s
  5. abcfruits.net at 7.9 s7.9 s
  6. abcfruits.net at 9.4 s9.4 s
  7. abcfruits.net at 11.0 s11.0 s
  8. abcfruits.net at 12.6 s12.6 s

Speed

10 to fix54
  • Use efficient cache lifetimes

    9.6 s · 3.6 MB

    210 files are served with short cache lifetimes, so returning visitors download them again (3.6 MB).

  • Render-blocking requests

    5.7 s

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

  • Improve image delivery

    1.6 s · 1.2 MB

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

  • Reduce unused CSS

    2.3 s · 423 KiB

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

  • Reduce unused JavaScript

    1.8 s · 322 KiB

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

  • 4,326 HTML elements

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

  • Main-thread work: 4.2 s

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

  • Mobile performance score: 54

    54/100

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

  • Font display

    300 ms

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

  • Google Tag Manager adds 176 ms

    176 ms

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

  • Minify CSS

    290 ms · 46 KiB

    46 KiB could be saved by minifying CSS.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and zohocdn.com and others), adding 603 KiB and 260 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 35 KiB

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

  • Minify JavaScript

    120 ms · 11 KiB

    11 KiB could be saved by minifying JavaScript.

  • 10 long tasks on the main thread

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

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

    234 ms

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

Core Web Vitals

11 to fix33
  • 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.4 s

    5.4 s

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

  • Real-user INP: 908 ms

    908 ms

    Real visitors wait 908 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 5.0 s

    5.0 s

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

  • Real-user TTFB: 2.4 s

    2.4 s

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

  • Largest Contentful Paint: 23.2 s

    23.2 s

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

  • Speed Index: 18.3 s

    18.3 s

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

  • Time to Interactive: 23.5 s

    23.5 s

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

  • First Contentful Paint: 5.9 s

    5.9 s

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

  • Tap response (INP) got 38% slower for real visitors

    +38%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 160 ms to 228 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

3 checks passed
  • Real-user CLS: 0.10

    0.10

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

  • Total Blocking Time: 146 ms

    146 ms

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

  • Cumulative Layout Shift: 0.03

    0.03

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

Images and page weight

1 to fix70
  • Page weight: 4.5 MB in 268 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 268 requests on a phone: images 2.1 MB (67), scripts 1.2 MB (90) and stylesheets 620 KiB (80). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (105 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.3 g of CO₂ per visit

    1.28 g

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

2 checks passed
  • 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

9 to fixGoogle 8789
  • 4 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 4 images without alt text

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

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

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

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

  • 18 form fields without a label

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

  • 6 links without text

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 8586
  • No H1 headline

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

  • 13 links with vague text

    13 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 2 links crawlers can't follow

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

  • 91 internal links, 6 external

    The homepage links to 91 pages on abcfruits.net and 6 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “ABC Fruits manufactures and exports fruit and vegetable pulp, puree, concentrates and IQF products in India for global …”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Pulp, Puree & Concentrate Manufacturer & supplier India”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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://abcfruits.com/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://abcfruits.com/llms.txt (36 KiB, 137 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9291
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to image at 'https://www.abcfruits.com/wp-content/uploads/2021/03/slider-bg1-scaled.jpg' from origin 'https://ab…”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    5 of 6 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
  • Thin social proof

    Social proof on the homepage: 16 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 8-field form

    Your longest form asks for 8 fields (7 required). Every extra field lowers completion.

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

    The homepage carries about 441 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: “Browse Shop”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us”, “Talk to Our Team” and “Browse Shop”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 1 of them by other companies (measured from a US location before any click).

  • 11 other companies contacted

    Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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 abcfruits.net, 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
E-commerce
WooCommerce
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 39 issues on abcfruits.net, including 21 speed issues, 3 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