greenforce.com website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, YouTube and Clarity and others), adding 2.5 MB and 2.9 s of main-thread time.

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

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

YouTube costs a phone 812 ms of main-thread work and 992 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.

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

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

13 images could be 471 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

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

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

33 KiB could be saved by minifying JavaScript.

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

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.

Your largest element takes 15.9 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 29.1 s. Good is under 3.8 s.

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

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

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

2 images 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' tap response (inp) went from 131 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 7.0 MB in 373 requests on a phone: scripts 2.7 MB (102), images 2.6 MB (56) and other files 973 KiB (181). Under 2 MB keeps phones on slow connections fast.

Header_Weisswurst_Launch_-_Mobile.jpg 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).

4 images further down the page (83 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn'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.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (23 elements).

Your title is 70 characters, so Google will cut it off around 60: “GREENFORCE | 100 % pflanzliche Produkte - ein Biss und Du willst mehr!”.

There are 3 <h1> headlines (“SCHARF AUF NEUES?”, “SAU GUAD OHNE SAU” and “GUTER GESCHMACK OHNE KOMPROMISSE.”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("www.greenforce.com/cdn/shop/files/gf-logo.png?v=1678878…”.

The homepage links to 98 pages on greenforce.com and 6 external pages.

The HTML your server sends has 988 of the 1,755 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

Your homepage links to https://www.greenforce.com/pages/im-handel, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.greenforce.com/en is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.greenforce.com/collections/alle-produkte, https://www.greenforce.com/collections/pflanzliche-aufschnitte, https://www.greenforce.com/collections/im-handel, https://www.greenforce.com/collections/vegane-saucen-und-dips, https://www.greenforce.com/collections/accessoires and https://www.greenforce.com/pages/high-protein-produkte have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.greenforce.com/collections/im-handel and https://www.greenforce.com/pages/greenforce-newsletter have no <h1> headline, so visitors and search engines get no clear main topic.

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

17 of 39 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,755 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, Klaviyo and Meta Pixel and 6 mores (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 29 cookies, 4 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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.