Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

grapevine.de

Schatzsuche - Escape game - Krimidinner - Grapevine.de

Page Load Speed

9.4 sec in total

First Response

710 ms

Resources Loaded

8.5 sec

Page Rendered

170 ms

grapevine.de screenshot

About Website

Click here to check amazing Grapevine content for Germany. Otherwise, check out these important facts you probably never knew about grapevine.de

Fertige Schatzsuchen, Escape games, GPS-Schatzsuchen, Schnitzeljagden, Krimidinner, Quizzen und Partyspiele - Alles zum Ausdrucken.

Visit grapevine.de

Key Findings

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

Performance Metrics

grapevine.de performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.1 s

0/100

25%

SI (Speed Index)

Value23.9 s

0/100

10%

TBT (Total Blocking Time)

Value4,270 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.195

63/100

15%

TTI (Time to Interactive)

Value24.6 s

0/100

10%

Network Requests Diagram

www.grapevine.de

710 ms

platform.js

40 ms

A.style.min.css,qver=81fb161b4c36db5220bf3a9baca190be.pagespeed.cf.7dkSrUVuLL.css

286 ms

A.frontend.css,qver=5.49.1.pagespeed.cf.Iw31Rs01dX.css

388 ms

A.badges.css,qver=5.49.1.pagespeed.cf.GgYWJ4KUaL.css

298 ms

Our browser made a total of 183 requests to load all elements on the main page. We found that 90% of them (165 requests) were addressed to the original Grapevine.de, 2% (4 requests) were made to Googletagmanager.com and 2% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Grapevine.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 948.6 kB (8%)

Content Size

11.3 MB

After Optimization

10.3 MB

In fact, the total size of Grapevine.de main page is 11.3 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. Only a small number of websites need less resources to load. Images take 10.2 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 936.8 kB

  • Original 1.0 MB
  • After minification 988.0 kB
  • After compression 84.3 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 936.8 kB or 92% of the original size.

Image Optimization

-0%

Potential reduce by 8.8 kB

  • Original 10.2 MB
  • After minification 10.1 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. Grapevine images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 3.0 kB

  • Original 122.5 kB
  • After minification 122.5 kB
  • After compression 119.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.

Requests Breakdown

Number of requests can be reduced by 75 (43%)

Requests Now

175

After Optimization

100

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

Accessibility Review

grapevine.de accessibility score

75

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

grapevine.de SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 doesn't use 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 Grapevine.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 Grapevine.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

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