Tools & Wizards About Us
vortrinken.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

vortrinken.com

Lustige Trinkspiele für deinen Partyabend und für jede Party

Page Load Speed

4.7 sec in total

First Response

833 ms

Resources Loaded

3.6 sec

Page Rendered

259 ms

vortrinken.com screenshot

About Website

Click here to check amazing Vortrinken content for Germany. Otherwise, check out these important facts you probably never knew about vortrinken.com

Lustige Trinkspiele zu zweit oder in Gruppen Partyspiele mit Karten oder Würfelspiele perfekt zum Vortrinken Saufspiele online mit Hangovergarantie.

Visit vortrinken.com

Key Findings

We analyzed Vortrinken.com page load time and found that the first response time was 833 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

vortrinken.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value4.4 s

75/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

www.vortrinken.com

833 ms

wp-emoji-release.min.js

369 ms

front.css

188 ms

postratings-css.css

190 ms

bootstrap.min.css

562 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 21% of them (23 requests) were addressed to the original Vortrinken.com, 14% (15 requests) were made to Dmp.theadex.com and 7% (8 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (833 ms) belongs to the original domain Vortrinken.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 617.7 kB (57%)

Content Size

1.1 MB

After Optimization

469.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vortrinken.com main page is 1.1 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. 55% of websites need less resources to load. Javascripts take 623.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 47.6 kB

  • Original 61.8 kB
  • After minification 60.2 kB
  • After compression 14.2 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 47.6 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 3.5 kB

  • Original 168.8 kB
  • After minification 165.3 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. Vortrinken images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 373.5 kB

  • Original 623.3 kB
  • After minification 621.3 kB
  • After compression 249.8 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 373.5 kB or 60% of the original size.

CSS Optimization

-83%

Potential reduce by 193.1 kB

  • Original 233.5 kB
  • After minification 223.6 kB
  • After compression 40.4 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. Vortrinken.com needs all CSS files to be minified and compressed as it can save up to 193.1 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

91

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.vortrinken.com

www.vortrinken.com

833 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

369 ms

front.css

front.css

188 ms

postratings-css.css

postratings-css.css

190 ms

bootstrap.min.css

bootstrap.min.css

562 ms

style.css

style.css

467 ms

font-awesome.min.css

font-awesome.min.css

266 ms

css

css

79 ms

css

css

90 ms

style.css

style.css

281 ms

lightbox.css

lightbox.css

207 ms

jquery.js

jquery.js

469 ms

jquery-migrate.min.js

jquery-migrate.min.js

298 ms

adsbygoogle.js

adsbygoogle.js

5 ms

front.js

front.js

206 ms

postratings-js.js

postratings-js.js

289 ms

bootstrap.min.js

bootstrap.min.js

509 ms

scripts.js

scripts.js

432 ms

select2.min.js

select2.min.js

581 ms

lightbox.js

lightbox.js

430 ms

wp-embed.min.js

wp-embed.min.js

478 ms

getads.js

getads.js

11 ms

analytics.js

analytics.js

23 ms

vt_bier_back3.jpg

vt_bier_back3.jpg

319 ms

vt_logo_230x90.png

vt_logo_230x90.png

143 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

139 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

170 ms

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

170 ms

ca-pub-1977423538151329.js

ca-pub-1977423538151329.js

133 ms

zrt_lookup.html

zrt_lookup.html

148 ms

show_ads_impl.js

show_ads_impl.js

81 ms

2dBELi3ZbivnVPt1KR2lhQ.woff

2dBELi3ZbivnVPt1KR2lhQ.woff

135 ms

mjitrc9VnL7D7tS-i3g3XQ.woff

mjitrc9VnL7D7tS-i3g3XQ.woff

136 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

198 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

115 ms

collect

collect

46 ms

rating_over.gif

rating_over.gif

144 ms

ads

ads

279 ms

osd.js

osd.js

46 ms

ads

ads

282 ms

t.js

t.js

128 ms

106 ms

adj

adj

103 ms

beacon

beacon

75 ms

impr

impr

130 ms

6227945966308215795

6227945966308215795

70 ms

abg.js

abg.js

72 ms

m_js_controller.js

m_js_controller.js

89 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

47 ms

x_button_blue2.png

x_button_blue2.png

8 ms

s

s

20 ms

26 ms

0

0

108 ms

surly.js

surly.js

75 ms

index.html

index.html

242 ms

verify_selector.js

verify_selector.js

176 ms

blank.gif

blank.gif

176 ms

adex.js

adex.js

264 ms

rtb

rtb

160 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

6 ms

ba.html

ba.html

14 ms

pixel

pixel

25 ms

4.gif

4.gif

16 ms

lidar.js

lidar.js

13 ms

sbhK2lTE.js

sbhK2lTE.js

12 ms

4311.js

4311.js

14 ms

cTrvNaRi.html

cTrvNaRi.html

8 ms

pixel

pixel

75 ms

pixel

pixel

75 ms

F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js

F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js

4 ms

match

match

101 ms

ad2.js

ad2.js

205 ms

verifyr.js

verifyr.js

33 ms

beacon.js

beacon.js

39 ms

0

0

21 ms

bg.png

bg.png

37 ms

adchoices.en.png

adchoices.en.png

63 ms

Rejuvenation_728x90_logo.gif

Rejuvenation_728x90_logo.gif

32 ms

MommyMakeover_728x90_bg.jpg

MommyMakeover_728x90_bg.jpg

64 ms

loadImages.js

loadImages.js

12 ms

t.js

t.js

89 ms

t.js

t.js

182 ms

sd

sd

23 ms

box_19_top-right.png

box_19_top-right.png

11 ms

ci.png

ci.png

10 ms

0

0

95 ms

analytic.js

analytic.js

93 ms

172 ms

1.gif

1.gif

173 ms

adj.php

adj.php

206 ms

nuggad

nuggad

97 ms

90 ms

pixel

pixel

20 ms

redirect

redirect

315 ms

redirect

redirect

305 ms

pixel

pixel

20 ms

cm.gif

cm.gif

200 ms

2.gif

2.gif

190 ms

cm.gif

cm.gif

187 ms

2.gif

2.gif

179 ms

1f37b.png

1f37b.png

155 ms

2.gif

2.gif

93 ms

2.gif

2.gif

93 ms

redirect

redirect

366 ms

redirect

redirect

382 ms

155

155

98 ms

activeview

activeview

14 ms

2.gif

2.gif

89 ms

2.gif

2.gif

89 ms

Accessibility Review

vortrinken.com accessibility score

82

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

vortrinken.com 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

vortrinken.com SEO score

99

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 Vortrinken.com 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 Vortrinken.com 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

vortrinken.com

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