matchafuel.com website review

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

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

8 third-party services load with your homepage (replocdn.com, alia-prod.com and Shopify and others), adding 4.9 MB and 1.8 s of main-thread time.

14 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

alia-prod.com costs a phone 393 ms of main-thread work and 2.3 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.

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

replocdn.com costs a phone 472 ms of main-thread work and 484 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.

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

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

Google Tag Manager costs a phone 247 ms of main-thread work and 493 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 2,479 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

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

Polyfills for old browsers add 46 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.

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.

Your largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Matcha powder packet and glass with green drink, powder spl…”.

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

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

Real visitors wait 237 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

Your homepage downloads 6.6 MB in 427 requests on a phone: images 2.8 MB (40), scripts 1.9 MB (76) and other files 1.6 MB (281). Under 2 MB keeps phones on slow connections fast.

standing_MOB2.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).

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

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

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

All page content should be contained by landmarks: 17 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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

The homepage links to 43 pages on matchafuel.com and 4 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://matchafuel.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://matchafuel.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://matchafuel.com/customer_authentication/redirect, https://matchafuel.com/a/loop_subscriptions/get-subscription-link and https://matchafuel.com/pages/dailyritualbundle are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://matchafuel.com/customer_authentication/redirect, https://matchafuel.com/collections/best-sellers, https://matchafuel.com/pages/howtoprepare, https://matchafuel.com/pages/refer-a-friend, https://matchafuel.com/a/loop_subscriptions/get-subscription-link and https://matchafuel.com/pages/dailyritualbundle have no meta description, so Google writes the search snippet from whatever text it finds.

https://matchafuel.com/customer_authentication/redirect, https://matchafuel.com/collections/best-sellers, https://matchafuel.com/pages/howtoprepare, https://matchafuel.com/a/loop_subscriptions/get-subscription-link and https://matchafuel.com/pages/dailyritualbundle have no <h1> headline, so visitors and search engines get no clear main topic.

https://matchafuel.com/pages/howtoprepare has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

The homepage carries about 1,879 words of visible text.

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