lf.coffee website review

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

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

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

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

6 images could be 160 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.

8 third-party services load with your homepage (rechargecdn.com, Shopify and Klaviyo and others), adding 401 KiB and 206 ms of main-thread time.

About 213 KiB of JavaScript is downloaded but never used on this page.

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

4 KiB could be saved by minifying JavaScript.

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

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

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.

The page becomes fully interactive after 9.9 s. Good is under 3.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.4 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are dedicated to providing outstanding coffee, sourced f…”.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 87 ms to 96 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.1 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 23.9 MB in 237 requests on a phone: media 21.8 MB (2), scripts 857 KiB (58) and other files 855 KiB (120). Under 2 MB keeps phones on slow connections fast.

1 image (37 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 6.77 g of CO₂e: 812.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 dropdown has no label.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

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

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

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

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 89 pages on lf.coffee and 10 external pages.

https://www.lf.coffee/en-in/collections/alle-produkte-specialty-coffee, https://www.lf.coffee/en-in/collections/cascara, https://www.lf.coffee/en-in/collections/home, https://www.lf.coffee/en-in/blogs/origin-trip-panama-2023 and https://www.lf.coffee/en-in/pages/abonnement have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lf.coffee/en-in/collections/espresso-specialty-coffee and https://www.lf.coffee/en-in/collections/gutscheine-specialty-coffee use the same meta description. A description written for each page earns more clicks.

https://www.lf.coffee/en-in/collections/archiv-specialty-coffee, https://www.lf.coffee/en-in/pages/roesterei and https://www.lf.coffee/en-in/pages/about have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage carries about 296 words of visible text.

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