Tools & Wizards About Us
feuma.de screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

feuma.de

FEUMA modern high-performance machines for everyday kitchen use

Page Load Speed

5 sec in total

First Response

685 ms

Resources Loaded

3.5 sec

Page Rendered

757 ms

feuma.de screenshot

About Website

Welcome to feuma.de homepage info - get ready to check FEUMA best content right away, or after learning these important things about feuma.de

Innovative and award-winning kitchen machines from FEUMA for your kitchen, catering companies, hotels, restaurants and fruit or vegetable processing companies.

Visit feuma.de

Key Findings

We analyzed Feuma.de page load time and found that the first response time was 685 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

feuma.de performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value1,720 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.722

6/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

685 ms

main.css

331 ms

mi-marketing.css

324 ms

borlabs.css

322 ms

frontend-lite.min.css

459 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that all of those requests were addressed to Feuma.de and no external sources were called. The less responsive or slowest element that took the longest time to load (957 ms) belongs to the original domain Feuma.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 243.1 kB (16%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Feuma.de main page is 1.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 632.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 219.3 kB

  • Original 267.2 kB
  • After minification 258.1 kB
  • After compression 47.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 219.3 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 13.9 kB

  • Original 632.6 kB
  • After minification 618.7 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. FEUMA images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 486 B

  • Original 422.9 kB
  • After minification 422.9 kB
  • After compression 422.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 9.4 kB

  • Original 168.7 kB
  • After minification 168.7 kB
  • After compression 159.3 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Feuma.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 61 (73%)

Requests Now

83

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FEUMA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

685 ms

main.css

main.css

331 ms

mi-marketing.css

mi-marketing.css

324 ms

borlabs.css

borlabs.css

322 ms

frontend-lite.min.css

frontend-lite.min.css

459 ms

swiper.min.css

swiper.min.css

325 ms

post-2633.css

post-2633.css

352 ms

frontend-lite.min.css

frontend-lite.min.css

429 ms

global.css

global.css

449 ms

post-5873.css

post-5873.css

453 ms

post-5728.css

post-5728.css

466 ms

post-5492.css

post-5492.css

467 ms

post-5633.css

post-5633.css

538 ms

borlabs-cookie-1-en.css

borlabs-cookie-1-en.css

568 ms

jquery.min.js

jquery.min.js

674 ms

jquery-migrate.min.js

jquery-migrate.min.js

562 ms

rbtools.min.js

rbtools.min.js

733 ms

rs6.min.js

rs6.min.js

957 ms

mi-marketing.js

mi-marketing.js

643 ms

borlabs-cookie-config-en.json.js

borlabs-cookie-config-en.json.js

669 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

671 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

863 ms

widget-icon-box.min.css

widget-icon-box.min.css

769 ms

widget-icon-list.min.css

widget-icon-list.min.css

769 ms

widget-nested-carousel.min.css

widget-nested-carousel.min.css

770 ms

widget-loop-builder.min.css

widget-loop-builder.min.css

769 ms

widget-carousel.min.css

widget-carousel.min.css

769 ms

borlabs-cookie-prioritize.min.js

borlabs-cookie-prioritize.min.js

752 ms

borlabs-cookie.min.js

borlabs-cookie.min.js

752 ms

post-6370.css

post-6370.css

753 ms

post-6367.css

post-6367.css

753 ms

language-switcher.min.css

language-switcher.min.css

820 ms

animations.min.css

animations.min.css

823 ms

post-5888.css

post-5888.css

824 ms

style-1656.css

style-1656.css

824 ms

forminator-icons.min.css

forminator-icons.min.css

825 ms

forminator-utilities.min.css

forminator-utilities.min.css

826 ms

forminator-grid.open.min.css

forminator-grid.open.min.css

760 ms

forminator-form-default.base.min.css

forminator-form-default.base.min.css

783 ms

buttons.min.css

buttons.min.css

778 ms

style-1657.css

style-1657.css

773 ms

style-548.css

style-548.css

778 ms

style-3780.css

style-3780.css

699 ms

style-3884.css

style-3884.css

736 ms

style-2490.css

style-2490.css

748 ms

rs6.css

rs6.css

754 ms

plugins.js

plugins.js

807 ms

main.js

main.js

806 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

733 ms

jquery.sticky.min.js

jquery.sticky.min.js

738 ms

imagesloaded.min.js

imagesloaded.min.js

773 ms

jquery.validate.min.js

jquery.validate.min.js

717 ms

forminator-form.min.js

forminator-form.min.js

689 ms

front.multi.min.js

front.multi.min.js

689 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

628 ms

webpack.runtime.min.js

webpack.runtime.min.js

690 ms

frontend-modules.min.js

frontend-modules.min.js

564 ms

hooks.min.js

hooks.min.js

564 ms

i18n.min.js

i18n.min.js

587 ms

frontend.min.js

frontend.min.js

586 ms

waypoints.min.js

waypoints.min.js

579 ms

core.min.js

core.min.js

602 ms

frontend.min.js

frontend.min.js

594 ms

elements-handlers.min.js

elements-handlers.min.js

594 ms

Exo2-Regular.woff

Exo2-Regular.woff

837 ms

exo-2-v5-latin_latin-ext-regular.woff

exo-2-v5-latin_latin-ext-regular.woff

671 ms

Exo2-Medium.woff

Exo2-Medium.woff

606 ms

exo-2-v5-latin_latin-ext-500.woff

exo-2-v5-latin_latin-ext-500.woff

771 ms

Exo2-SemiBold.woff

Exo2-SemiBold.woff

768 ms

exo-2-v5-latin_latin-ext-600.woff

exo-2-v5-latin_latin-ext-600.woff

768 ms

Exo2-Bold.woff

Exo2-Bold.woff

765 ms

exo-2-v5-latin_latin-ext-700.woff

exo-2-v5-latin_latin-ext-700.woff

765 ms

Logo-Feuma.png

Logo-Feuma.png

753 ms

feuma-logo-ohne-kreis.png

feuma-logo-ohne-kreis.png

721 ms

rotor-lips-feuma-rot.jpg

rotor-lips-feuma-rot.jpg

776 ms

vac-star-logo.png

vac-star-logo.png

808 ms

feuma-gastromaschinen-kuechengeraete-qriuxbqu2r5z40j7d94nhhp5ynbush4lpldb7txpzk.jpg

feuma-gastromaschinen-kuechengeraete-qriuxbqu2r5z40j7d94nhhp5ynbush4lpldb7txpzk.jpg

756 ms

rotor-lips-produkte-bei-feuma-pjl3qtznqi087dt5t58xsd8c243jkvvxsw95hlwbf4.jpg

rotor-lips-produkte-bei-feuma-pjl3qtznqi087dt5t58xsd8c243jkvvxsw95hlwbf4.jpg

752 ms

rotor-lips-feuma-rot-1024x153.jpg

rotor-lips-feuma-rot-1024x153.jpg

765 ms

vac-star-vakuum-kuechengaerat-feuma-qrx5u59oomob4erncw9amsfe6dpafh0oac1o6p7ikw.jpg

vac-star-vakuum-kuechengaerat-feuma-qrx5u59oomob4erncw9amsfe6dpafh0oac1o6p7ikw.jpg

727 ms

vac-star-logo-1024x203.png

vac-star-logo-1024x203.png

717 ms

23-ted-lightgreen-sa-gruen-gn-weisskraut-i.jpg

23-ted-lightgreen-sa-gruen-gn-weisskraut-i.jpg

692 ms

supra_6e_detail.jpg

supra_6e_detail.jpg

694 ms

feuma-ruehrmaschinen-768x1103.jpg

feuma-ruehrmaschinen-768x1103.jpg

811 ms

hu_1030_h_sas_feuma.jpg

hu_1030_h_sas_feuma.jpg

730 ms

fleischwolf-tw-h-82-meat-mincer-768x764.jpg

fleischwolf-tw-h-82-meat-mincer-768x764.jpg

733 ms

feuma-asetsm-apfelbearbeitungsmaschine-1-768x555.jpg

feuma-asetsm-apfelbearbeitungsmaschine-1-768x555.jpg

669 ms

EFRE-EU-Logo-FEUMA-1024x179.jpg

EFRE-EU-Logo-FEUMA-1024x179.jpg

707 ms

feuma-lounge-eingang-e1722428417600-1024x679.jpg

feuma-lounge-eingang-e1722428417600-1024x679.jpg

817 ms

feuma-logo-rot-kreis.png

feuma-logo-rot-kreis.png

775 ms

roter-pfeil.svg

roter-pfeil.svg

714 ms

feuma-gastromaschinen-kuechengeraete.jpg

feuma-gastromaschinen-kuechengeraete.jpg

742 ms

Accessibility Review

feuma.de accessibility score

86

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

Low

No form fields have multiple labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

feuma.de best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

feuma.de SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Feuma.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Feuma.de main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

feuma.de

Open Graph data is detected on the main page of FEUMA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: