Website review, no card needed

fey1926.com logo

fey1926.com website review

Visit site (opens in a new tab)Reviewed 26 October 202625 issues · 81 checks

This review found 25 issues worth fixing on fey1926.com, 9 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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

Real-visitor load time (LCP)75th percentile, phones
1.0 s491 msMay 9Oct 24559 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026764 ms
May 16, 2026726 ms
May 23, 2026722 ms
May 30, 2026768 ms
Jun 6, 2026768 ms
Jun 13, 2026912 ms
Jun 20, 2026967 ms
Jun 27, 2026885 ms
Jul 4, 2026829 ms
Jul 11, 2026708 ms
Jul 18, 2026771 ms
Jul 25, 2026737 ms
Aug 1, 2026787 ms
Aug 8, 2026828 ms
Aug 15, 2026780 ms
Aug 22, 2026767 ms
Aug 29, 2026694 ms
Sep 5, 2026611 ms
Sep 12, 2026576 ms
Sep 19, 2026559 ms
Sep 26, 2026554 ms
Oct 3, 2026573 ms
Oct 10, 2026555 ms
Oct 17, 2026553 ms
Oct 24, 2026559 ms
Real-visitor tap response (INP)75th percentile, phones
72 ms57 msMay 9Oct 2465 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202666 ms
May 16, 202669 ms
May 23, 202668 ms
May 30, 202669 ms
Jun 6, 202670 ms
Jun 13, 202670 ms
Jul 25, 202662 ms
Aug 1, 202663 ms
Aug 8, 202667 ms
Aug 15, 202665 ms
Aug 22, 202668 ms
Aug 29, 202664 ms
Sep 5, 202662 ms
Sep 12, 202661 ms
Sep 19, 202659 ms
Sep 26, 202659 ms
Oct 3, 202664 ms
Oct 10, 202666 ms
Oct 17, 202666 ms
Oct 24, 202665 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of fey1926.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fey1926.com at 0.4 s0.4 s
  2. fey1926.com at 0.8 s0.8 s
  3. fey1926.com at 1.1 s1.1 s
  4. fey1926.com at 1.5 s1.5 s
  5. fey1926.com at 1.9 s1.9 s
  6. fey1926.com at 2.3 s2.3 s
  7. fey1926.com at 2.6 s2.6 s
  8. fey1926.com at 3.0 s3.0 s

Speed

3 to fix80
  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 80

    80/100

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

  • website-files.com adds 87 ms

    87 ms

    website-files.com costs a phone 87 ms of main-thread work and 662 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.

  • Reduce unused CSS

    150 ms · 30 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (website-files.com, cloudfront.net and Google Tag Manager), adding 693 KiB and 108 ms of main-thread time.

  • Minify CSS

    150 ms · 5 KiB

    5 KiB could be saved by minifying CSS.

  • 2 long tasks on the main thread

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

  • Reduce unused JavaScript

    83 KiB

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

  • Improve image delivery

    35 KiB

    1 image could be 35 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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.

2 checks passed
  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 325 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 4.2 s

    4.2 s

    Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Genieße die nächtliche Ruhe, erwache mit der Sonne und begi…”.

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Time to Interactive: 4.2 s

    4.2 s

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.6 s

    0.6 s

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

  • Real-user INP: 65 ms

    65 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.5 s

    0.5 s

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

  • Real-user TTFB: 251 ms

    251 ms

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

  • Largest content (LCP) got 25% faster for real visitors

    -25%

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

  • Total Blocking Time: 197 ms

    197 ms

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

  • Speed Index: 2.3 s

    2.3 s

    Visually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • 1 image in older formats

    1 image (50 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.

  • About 0.3 g of CO₂ per visit

    0.25 g

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

3 checks passed
  • Page weight: 910 KiB in 27 requests

    910 KiB

    Your homepage downloads 910 KiB in 27 requests on a phone: images 502 KiB (8), scripts 297 KiB (6) and fonts 69 KiB (3). That is a lean page.

  • 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

7 to fixGoogle 7484
  • 5 text elements with low contrast

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

  • 2 tap targets too small

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Links must have discernible text (1 element)

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

  • All page content should be contained by landmarks (8 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h1 → h4 and h1 → h5), 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. (2 elements).

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 27 automated accessibility rules passed

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

SEO

2 to fixGoogle 9291
  • 2 H1 headlines

    There are 2 <h1> headlines (“A Century of Quality Sleep.” and “Genieße die nächtliche Ruhe, erwache mit der Sonn…”). One clear main headline is easier for people and search engines.

  • Structured data has 2 problems

    Structured data found (Organization) but with 2 problems, for example “Organization: url is not an absolute URL ("/")”.

  • 21 internal links, 0 external

    The homepage links to 21 pages on fey1926.com and 0 external pages.

6 checks passed
  • Meta description: 74 characters

    Your meta description is 74 characters: “Enjoy the peaceful nights, rise with the sun, and welcome a brand new day.”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Fey - A Century of Quality Sleep”.

  • Canonical URL set

    The canonical URL is https://www.fey1926.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.fey1926.com/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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.fey1926.com/llms.txt (19 KiB, 93 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 2 pages share a title

    / and https://www.fey1926.com/old-home all use the title “Fey - A Century of Quality Sleep”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.fey1926.com/produkte/boxspringbetten, https://www.fey1926.com/produkte/kissen and https://www.fey1926.com/produkte/zipzu-spannbettlaken have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.fey1926.com/ueber-uns and https://www.fey1926.com/kontakt use the same meta description. A description written for each page earns more clicks.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Unexpected token '<'”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    8 of 9 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • No call to action on the first screen

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

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 194 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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.

2 checks passed
  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 6 other companies contacted

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

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 fey1926.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google Analytics
Hosting
Webflow

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on fey1926.com, including 7 speed issues, 2 SEO issues and 4 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