Tools & Wizards About Us
gugelhof.de screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

gugelhof.de

Gugelhof Berlin

Page Load Speed

17.5 sec in total

First Response

333 ms

Resources Loaded

15.9 sec

Page Rendered

1.2 sec

gugelhof.de screenshot

About Website

Visit gugelhof.de now to see the best up-to-date Gugelhof content and also check out these interesting facts you probably never knew about gugelhof.de

Visit gugelhof.de

Key Findings

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

Performance Metrics

gugelhof.de performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value19.4 s

0/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value67.5 s

0/100

10%

Network Requests Diagram

gugelhof.de

333 ms

gugelhofberlin.de

555 ms

style.min.css

160 ms

cookieblocker.min.css

276 ms

style.min.css

318 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gugelhof.de, 69% (62 requests) were made to Gugelhofberlin.de and 17% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (14.2 sec) relates to the external source Gugelhofberlin.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 759.8 kB (12%)

Content Size

6.5 MB

After Optimization

5.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gugelhof.de main page is 6.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. 65% of websites need less resources to load. Images take 5.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 105.8 kB

  • Original 125.4 kB
  • After minification 119.9 kB
  • After compression 19.6 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 105.8 kB or 84% of the original size.

Image Optimization

-10%

Potential reduce by 615.3 kB

  • Original 5.9 MB
  • After minification 5.3 MB

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. Gugelhof images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 20.8 kB

  • Original 332.8 kB
  • After minification 332.8 kB
  • After compression 312.0 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

-14%

Potential reduce by 17.9 kB

  • Original 129.7 kB
  • After minification 129.7 kB
  • After compression 111.7 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. Gugelhof.de needs all CSS files to be minified and compressed as it can save up to 17.9 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (67%)

Requests Now

67

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gugelhof.de

gugelhof.de

333 ms

gugelhofberlin.de

gugelhofberlin.de

555 ms

style.min.css

style.min.css

160 ms

cookieblocker.min.css

cookieblocker.min.css

276 ms

style.min.css

style.min.css

318 ms

theme.min.css

theme.min.css

314 ms

frontend-lite.min.css

frontend-lite.min.css

433 ms

post-5.css

post-5.css

338 ms

elementor-icons.min.css

elementor-icons.min.css

342 ms

swiper.min.css

swiper.min.css

393 ms

frontend-lite.min.css

frontend-lite.min.css

426 ms

global.css

global.css

428 ms

post-36.css

post-36.css

461 ms

post-41.css

post-41.css

463 ms

post-25.css

post-25.css

531 ms

css

css

35 ms

fontawesome.min.css

fontawesome.min.css

638 ms

solid.min.css

solid.min.css

545 ms

regular.min.css

regular.min.css

550 ms

jquery.min.js

jquery.min.js

721 ms

jquery-migrate.min.js

jquery-migrate.min.js

581 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

647 ms

widget-icon-box.min.css

widget-icon-box.min.css

659 ms

widget-call-to-action.min.css

widget-call-to-action.min.css

662 ms

platform.js

platform.js

33 ms

widget-icon-list.min.css

widget-icon-list.min.css

694 ms

animations.min.css

animations.min.css

814 ms

hello-frontend.min.js

hello-frontend.min.js

815 ms

complianz.min.js

complianz.min.js

814 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

815 ms

imagesloaded.min.js

imagesloaded.min.js

815 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

893 ms

webpack.runtime.min.js

webpack.runtime.min.js

893 ms

frontend-modules.min.js

frontend-modules.min.js

943 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

944 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

945 ms

wp-polyfill.min.js

wp-polyfill.min.js

960 ms

hooks.min.js

hooks.min.js

1000 ms

i18n.min.js

i18n.min.js

1005 ms

frontend.min.js

frontend.min.js

1051 ms

platform.js

platform.js

39 ms

waypoints.min.js

waypoints.min.js

890 ms

core.min.js

core.min.js

805 ms

frontend.min.js

frontend.min.js

807 ms

elements-handlers.min.js

elements-handlers.min.js

816 ms

jquery.sticky.min.js

jquery.sticky.min.js

784 ms

image.png

image.png

667 ms

DSC00192-scaled-2.jpg

DSC00192-scaled-2.jpg

1534 ms

image-1-150x150.png

image-1-150x150.png

501 ms

JN5_5945-scaled.jpeg

JN5_5945-scaled.jpeg

1053 ms

JN5_6011-scaled.jpeg

JN5_6011-scaled.jpeg

2006 ms

image-1024x683.jpeg

image-1024x683.jpeg

645 ms

image-2.png

image-2.png

2518 ms

image-1-683x1024.jpeg

image-1-683x1024.jpeg

1028 ms

DSC00192-scaled-1-1024x683.jpg

DSC00192-scaled-1-1024x683.jpg

993 ms

image-1.png

image-1.png

1121 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

31 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

31 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

67 ms

KFOkCnqEu92Fr1MmgVxIIzQ.woff

KFOkCnqEu92Fr1MmgVxIIzQ.woff

79 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

80 ms

KFOlCnqEu92Fr1MmYUtfBBc-.woff

KFOlCnqEu92Fr1MmYUtfBBc-.woff

81 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

80 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff

78 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

77 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

106 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

105 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

105 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

106 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff

105 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff

105 ms

fa-solid-900.woff

fa-solid-900.woff

1314 ms

fa-regular-400.woff

fa-regular-400.woff

1194 ms

DSC00282-scaled-1.jpg

DSC00282-scaled-1.jpg

1386 ms

DSC00263-scaled-1-1024x683.jpg

DSC00263-scaled-1-1024x683.jpg

1406 ms

PLE0232-scaled-1-1024x684.jpg

PLE0232-scaled-1-1024x684.jpg

1526 ms

Bildschirm%C2%ADfoto-2023-07-06-um-21.53.41.png

Bildschirm%C2%ADfoto-2023-07-06-um-21.53.41.png

1741 ms

Bildschirm%C2%ADfoto-2023-07-06-um-21.54.19.png

Bildschirm%C2%ADfoto-2023-07-06-um-21.54.19.png

12757 ms

Bildschirm%C2%ADfoto-2023-07-06-um-21.55.22.png

Bildschirm%C2%ADfoto-2023-07-06-um-21.55.22.png

14153 ms

Bildschirm%C2%ADfoto-2023-07-06-um-21.55.01.png

Bildschirm%C2%ADfoto-2023-07-06-um-21.55.01.png

12546 ms

eicons.woff

eicons.woff

1863 ms

widget.js

widget.js

427 ms

embed

embed

325 ms

js

js

44 ms

hydra-0011i000002kSPXAA2

hydra-0011i000002kSPXAA2

209 ms

all.min.css

all.min.css

58 ms

widget.min.css

widget.min.css

61 ms

widget.body.mod.min.js

widget.body.mod.min.js

78 ms

fa-solid-900.woff

fa-solid-900.woff

5 ms

fa-regular-400.woff

fa-regular-400.woff

3 ms

Accessibility Review

gugelhof.de accessibility score

90

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 progressbar elements do not have accessible names.

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

High

<frame> or <iframe> elements do not have a title

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

gugelhof.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

gugelhof.de SEO score

91

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gugelhof.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Gugelhof.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

gugelhof.de

Open Graph description is not detected on the main page of Gugelhof. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: