asepticfruitpurees.com website review

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

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

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

8 third-party services load with your homepage (Google CDN, Shopify and Hubspot and others), adding 2.6 MB and 1.5 s of main-thread time.

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

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

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

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

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

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

LiveChat costs a phone 110 ms of main-thread work and 367 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.

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

About 23 KiB of CSS is downloaded but never applied on this page.

13 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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

Your homepage downloads 5.9 MB in 390 requests on a phone: scripts 2.5 MB (132), other files 1.5 MB (150) and images 1.1 MB (31). Under 2 MB keeps phones on slow connections fast.

hero_banner_mobile_c0c1790e-374e-4038-8c9a-febfa88f946f.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

1 dropdown has no label.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is 73 characters, so Google will cut it off around 60: “Fresh Fruit Ingredient For Natural Beverages – AFP | Aseptic Fruit Purees”.

There are 2 <h1> headlines (“.box-select-mobile{ justify-content: center; } @m…” and “Subscribe To Our News And Specials”). One clear main headline is easier for people and search engines.

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

Structured data found ((untyped), Organization and WebSite) but with 2 problems, for example “block has no @type”.

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

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

The homepage links to 219 pages on asepticfruitpurees.com and 9 external pages.

https://asepticfruitpurees.com/collections/acai, https://asepticfruitpurees.com/collections/apple, https://asepticfruitpurees.com/collections/banana, https://asepticfruitpurees.com/collections/blackberry, https://asepticfruitpurees.com/collections/blood-orange-1 and https://asepticfruitpurees.com/collections/blueberry and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 694 words of visible text.

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

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

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