mafco.com website review

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

Your mobile performance score is 52 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

4 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and Cloudflare and others), adding 920 KiB and 895 ms of main-thread time.

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

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

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

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

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

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

Desktop scores 87 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Global Leader in Licorice Products Featuring MagnaSweet…”.

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

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

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

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

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.

2 images further down the page (41 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 0.52 g of CO₂e: 62.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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.

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

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

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

The homepage links to 45 pages on mafco.com and 5 external pages.

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, which the crawlers above handle.

https://mafco.com/pure-derivatives and https://mafco.com/magnasweet/pure-derivatives all use the title “Pure Derivatives of Glycyrrhiza[br]For Personal Care Products - Mafco…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mafco.com/pure-derivatives and https://mafco.com/magnasweet/pure-derivatives use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mafco.com/magnasweet/pure-derivatives, whose canonical is https://mafco.com/pure-derivatives. 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 16 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

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

Your longest form asks for 15 fields (0 required). Every extra field lowers completion.

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

Before a visitor clicks anything, the page loads 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 2 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.