jurassicfruit.com website review

26 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

8 third-party services load with your homepage (omnisnippet1.com, Shopify and Clarity and others), adding 1.2 MB and 406 ms of main-thread time.

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

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

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

Soundest costs a phone 0 ms of main-thread work and 699 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.

About 144 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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.

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

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

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

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

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

Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Dein köstlichstes Abenteuer auf Erden”. Most of its time is element render delay (2.6 s).

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-10-31, real Chrome visitors' tap response (inp) went from 192 ms to 225 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.9 MB in 285 requests on a phone: images 2.3 MB (65), other files 1.3 MB (132) and scripts 702 KiB (67). Under 2 MB keeps phones on slow connections fast.

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

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

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

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

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

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

Alternative text of images should not be repeated as text: 20 elements on the page fail this check, rated minor by axe-core.

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

Your title is 78 characters, so Google will cut it off around 60: “JURASSIC FRUIT | #1 für exotische Bio Früchte, Nüsse, Datteln – Jurassic Fruit”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Dein köstlichstes Abenteuer auf Erden” and “Nur heute: 1 Kiste Kokosnüsse gekauft = 1 Kiste g…”). One clear main headline is easier for people and search engines.

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

The homepage links to 132 pages on jurassicfruit.com and 7 external pages.

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.

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

https://www.jurassicfruit.com/policies/privacy-policy and https://www.jurassicfruit.com/collections/fruechte-asien have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.jurassicfruit.com/pages/date-sale, whose canonical is https://www.jurassicfruit.com/collections/datteln. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-static.okendo.io/reviews-widget-plus/css/okendo-reviews-styles.c5b9c195.css' f…”.

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

18 images are served at too low a resolution for sharp phone screens.

The homepage carries about 709 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.

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

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.

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