Website review, no card needed

abcfruits.com logo

abcfruits.com website review

Visit site (opens in a new tab)Reviewed 19 October 202643 issues · 76 checks

This review found 43 issues worth fixing on abcfruits.com, 22 of them high impact, across 76 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

Full-page screenshot of abcfruits.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abcfruits.com at 1.3 s1.3 s
  2. abcfruits.com at 2.5 s2.5 s
  3. abcfruits.com at 3.8 s3.8 s
  4. abcfruits.com at 5.1 s5.1 s
  5. abcfruits.com at 6.4 s6.4 s
  6. abcfruits.com at 7.6 s7.6 s
  7. abcfruits.com at 8.9 s8.9 s
  8. abcfruits.com at 10.2 s10.2 s

Speed

10 to fix36
  • Use efficient cache lifetimes

    11.5 s · 4.2 MB

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

  • Render-blocking requests

    5.3 s

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

  • Reduce unused CSS

    2.5 s · 422 KiB

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

  • Improve image delivery

    1.4 s · 1.4 MB

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

  • Reduce unused JavaScript

    1.2 s · 196 KiB

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

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 7.0 s

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

  • 4,830 HTML elements

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

  • Minify CSS

    300 ms · 46 KiB

    46 KiB could be saved by minifying CSS.

  • 15 long tasks on the main thread

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (cdn-cookieyes.com, zohocdn.com and zohopublic.in and others), adding 348 KiB and 95 ms of main-thread time.

  • Font display

    50 ms

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

  • Legacy JavaScript

    25 KiB

    Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

    119 ms

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

Core Web Vitals

6 to fix45
  • Largest Contentful Paint: 20.7 s

    20.7 s

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

  • Time to Interactive: 21.0 s

    21.0 s

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

  • First Contentful Paint: 6.5 s

    6.5 s

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

  • Speed Index: 13.4 s

    13.4 s

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

  • Total Blocking Time: 822 ms

    822 ms

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

  • 2 images without width and height

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

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

    0.029

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

Images and page weight

1 to fix70
  • Page weight: 4.7 MB in 248 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 248 requests on a phone: images 2.7 MB (66), scripts 874 KiB (77) and stylesheets 614 KiB (79). 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.35 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.35 g of CO₂e: 161.5 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
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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

10 to fixGoogle 5437
  • Page is set to noindex

    The robots meta tag says “noindex, nofollow, max-snippet:-1, max-image-preview:large,…”: Google is told not to list this page at all.

  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No H1 headline

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (17 characters)

    Your title is only 17 characters: “Home - ABC Fruits”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (392 characters)

    Your meta description is 392 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.abcfruits.com/sitemap.rss, so Google discovers your pages only by following links.

  • 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.com and 6 external pages.

2 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

AI search readiness

2 to fix53
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), 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.

  • No llms.txt

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

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

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

1 to fixGoogle 9697
  • 1 distorted image

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • 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

4 to fix67
  • Thin social proof

    Social proof on the homepage: 2 trust badges. 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.

  • A 13-field form

    Your longest form asks for 13 fields (11 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 440 words of copy

    The homepage carries about 440 words of visible text.

2 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”.

Privacy and tracking

  • 11 cookies set on arrival

    11

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

  • 8 other companies contacted

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

2 checks passed
  • Consent tool: CookieYes

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

  • 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 abcfruits.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on abcfruits.com, including 16 speed issues, 10 SEO issues and 4 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