sanygran.com website review

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

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

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

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and wonderpush.com and others), adding 996 KiB and 398 ms of main-thread time.

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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.

Your largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “plant-based food manufacturer”.

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

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

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

The layout shifts by 0.304 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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.

Your homepage downloads 2.6 MB in 60 requests on a phone: scripts 1.4 MB (24), images 681 KiB (17) and stylesheets 412 KiB (6). Under 2 MB keeps phones on slow connections fast.

Inici_01-53d4b2c8.webp 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 0.74 g of CO₂e: 89.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

There are 3 <h1> headlines (“Manufacturer of plant-basedingredients and finish…”, “Manufacturer of plant-based ingredients and finis…” and “Manufacturer of plant-based ingredients and finis…”). One clear main headline is easier for people and search engines.

Structured data found (FoodEstablishment, ImageObject, Organization and Place) but with 1 problem, for example “ImageObject: url is not an absolute URL ("https://sanygran.com/wp-content/uploads/2024/11/Inici_01.jpg")”.

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

The homepage links to 43 pages on sanygran.com and 15 external pages.

There is no https://sanygran.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://sanygran.com/en/plant-based-b2b-solutions and https://sanygran.com/plant-based-b2b-solutions all use the title “Plant-Based B2B Solutions - Sanygran”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sanygran.com/en/plant-based-b2b-solutions and https://sanygran.com/plant-based-b2b-solutions use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://sanygran.com/plant-based-b2b-solutions, whose canonical is https://sanygran.com/en/plant-based-b2b-solutions. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://sanygran.com/en/plant-based-b2b-solutions, https://sanygran.com/plant-based-b2b-solutions, https://sanygran.com/en/our-plant-based-brands, https://sanygran.com/en/about-us, https://sanygran.com/en/recipes and https://sanygran.com/en/contact and 2 others took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Invalid site key or not loaded in api.js: 6LefF54cAAAAAFdUeo8GUKy0VS-UgCsEdRZr-iIT”.

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 291 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 7 cookies (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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.