tryfum.co.uk website review

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

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

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

About 755 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

8 third-party services load with your homepage (Shopify, Hotjar and gotolstoy.com and others), adding 1.8 MB and 704 ms of main-thread time.

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

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

cloudfront.net costs a phone 114 ms of main-thread work and 388 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 49 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.

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

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

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

11 KiB could be saved by minifying JavaScript.

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.

2 KiB could be saved by minifying CSS.

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 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “2,903 REVIEWS CRAVINGS, MEET YOUR MATCH Ridiculously Fidget…”.

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

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

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

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

6 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 194 ms to 176 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 2.6 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.9 MB in 446 requests on a phone: images 2.4 MB (79), scripts 1.6 MB (121) and other files 991 KiB (127). Under 2 MB keeps phones on slow connections fast.

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

2 images are downloaded at several times the size a phone draws them, for example FUM_ShopAll_BackgroundBlock_v1.jpg at 1,300 px wide, shown at 293 px. Resized copies would save about 57 KiB.

1 image (31 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h6, h4 → h6 and h1 → h4), which makes the page harder to scan with a screen reader.

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

Your title is only 21 characters: “Füm - The Good Habit™”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 8 <h1> headlines (“”, “Cravings, Meet Your Match” and “FLAVORED AIR DEVICE”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 76 pages on tryfum.co.uk and 25 external pages.

There is no https://tryfum.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://tryfum.com/collections/all, https://tryfum.com/pages/refer-a-friend, https://tryfum.com/pages/science, https://tryfum.com/blogs/fum, https://tryfum.com/pages/about and https://tryfum.com/pages/careers and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://tryfum.com/products/journey-pack 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.

https://tryfum.com/blogs/fum took over 3 s to send its HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 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 ()”.

1 image is served at too low a resolution for sharp phone screens.

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

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

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