Website review, no card needed

frezzor.eu logo

frezzor.eu website review

Visit site (opens in a new tab)Reviewed 10 November 202628 issues · 71 checks

This review found 28 issues worth fixing on frezzor.eu, 7 of them high impact, across 71 checks. The most urgent: 4 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of frezzor.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. frezzor.eu at 0.6 s0.6 s
  2. frezzor.eu at 1.1 s1.1 s
  3. frezzor.eu at 1.7 s1.7 s
  4. frezzor.eu at 2.2 s2.2 s
  5. frezzor.eu at 2.8 s2.8 s
  6. frezzor.eu at 3.4 s3.4 s
  7. frezzor.eu at 3.9 s3.9 s
  8. frezzor.eu at 4.5 s4.5 s

Speed

5 to fix69
  • Reduce unused JavaScript

    900 ms · 179 KiB

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

  • Mobile performance score: 69

    69/100

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

  • Render-blocking requests

    300 ms

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

  • Main-thread work: 2.2 s

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

  • Shopify adds 146 ms

    146 ms

    Shopify costs a phone 146 ms of main-thread work and 315 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 on the page

    8 third-party services load with your homepage (Shopify, minmaxify.com and sealsubscriptions.com and others), adding 446 KiB and 237 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 44 KiB

    About 44 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.

  • Minify JavaScript

    150 ms · 41 KiB

    41 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    150 ms · 26 KiB

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

  • 2 long tasks on the main thread

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix69
  • Largest Contentful Paint: 6.4 s

    6.4 s

    Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 6.1 s

    6.1 s

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

  • Time to Interactive: 6.4 s

    6.4 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 1 image without width and height

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

  • Not enough real-visitor data yet

    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 checks passed
  • Total Blocking Time: 76 ms

    76 ms

    Scripts block the page for only 76 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.0 MB in 218 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 218 requests on a phone: other files 748 KiB (92), scripts 601 KiB (98) and images 435 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.58 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9296
  • 4 text elements with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8583
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • 2 H1 headlines

    There are 2 <h1> headlines (“.logo__image--home { width: 135px; height: 56.542…” and “Omega-3 Black”). One clear main headline is easier for people and search engines.

  • 2 links crawlers can't follow

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 62 internal links, 8 external

    The homepage links to 62 pages on frezzor.eu and 8 external pages.

5 checks passed
  • Title: 34 characters

    Your title is a healthy 34 characters: “FREZZOR - Nutrition with Integrity”.

  • Canonical URL set

    The canonical URL is https://www.frezzor.eu/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.frezzor.eu/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (608 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.frezzor.eu/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

7 to fix50
  • 1 page without a title

    https://www.frezzor.eu/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 8 pages point its canonical at the homepage

    https://www.frezzor.eu/discount/FIRSTORDER, https://www.frezzor.eu/products/manuka-honey-uaf1000, https://www.frezzor.eu/products/collagen-peptides, https://www.frezzor.eu/products/super-greens, https://www.frezzor.eu/products/calcium-plus and https://www.frezzor.eu/products/vitamin-d3-k2 and 2 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 2 linked pages hidden from search

    https://www.frezzor.eu/blogs/news and https://www.frezzor.eu/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 11 pages share 2 titles

    /, https://www.frezzor.eu/discount/FIRSTORDER, https://www.frezzor.eu/products/manuka-honey-uaf1000, https://www.frezzor.eu/products/collagen-peptides, https://www.frezzor.eu/products/super-greens and https://www.frezzor.eu/products/calcium-plus and 3 others all use the title “FREZZOR - Nutrition with Integrity”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://www.frezzor.eu/collections/shop, https://www.frezzor.eu/discount/FIRSTORDER, https://www.frezzor.eu/products/manuka-honey-uaf1000, https://www.frezzor.eu/products/collagen-peptides, https://www.frezzor.eu/products/super-greens and https://www.frezzor.eu/products/calcium-plus and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.frezzor.eu/products/omega-3-black and https://www.frezzor.eu/products/omega-3-black-320 use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.frezzor.eu/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9687
  • 11 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 180 words

    The homepage has only about 180 words of visible text; thin pages give Google and first-time buyers little to go on.

  • Phone number is not tap-to-call

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop” and “Shop Now”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop”, “15% Off your First Order” and “Shop Now”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

Privacy and tracking

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 11 other companies contacted

    Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at frezzor.eu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Transcy · Minmaxify Order Limits · Inbox · Seal Subscriptions

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on frezzor.eu, including 10 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25