Tools & Wizards About Us
travelink.de screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

travelink.de

traveLink – it's all about travel, art & food

Page Load Speed

3.3 sec in total

First Response

334 ms

Resources Loaded

2 sec

Page Rendered

970 ms

travelink.de screenshot

About Website

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

traveLink - Portal zu den Themen Reise, Technik und News.

Visit travelink.de

Key Findings

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

Performance Metrics

travelink.de performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.093

91/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

travelink.de

334 ms

www.travelink.de

608 ms

views.css

182 ms

css_4bdc1f5f8620f0f3d1e1024c370d5c30.css

190 ms

js_f400a18ce3406c32f39ba4c67bacd319.js

290 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 18% of them (14 requests) were addressed to the original Travelink.de, 26% (20 requests) were made to Files.travelink.de and 10% (8 requests) were made to Fx-rate.net. The less responsive or slowest element that took the longest time to load (608 ms) belongs to the original domain Travelink.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 561.2 kB (52%)

Content Size

1.1 MB

After Optimization

521.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Travelink.de 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. 50% of websites need less resources to load. Javascripts take 375.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 133.0 kB

  • Original 167.3 kB
  • After minification 163.3 kB
  • After compression 34.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 133.0 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 16.8 kB

  • Original 267.8 kB
  • After minification 251.1 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. TraveLink images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 190.6 kB

  • Original 375.7 kB
  • After minification 367.4 kB
  • After compression 185.2 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 190.6 kB or 51% of the original size.

CSS Optimization

-81%

Potential reduce by 220.9 kB

  • Original 271.6 kB
  • After minification 270.1 kB
  • After compression 50.6 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. Travelink.de needs all CSS files to be minified and compressed as it can save up to 220.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (53%)

Requests Now

72

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

travelink.de

travelink.de

334 ms

www.travelink.de

www.travelink.de

608 ms

views.css

views.css

182 ms

css_4bdc1f5f8620f0f3d1e1024c370d5c30.css

css_4bdc1f5f8620f0f3d1e1024c370d5c30.css

190 ms

js_f400a18ce3406c32f39ba4c67bacd319.js

js_f400a18ce3406c32f39ba4c67bacd319.js

290 ms

element.js

element.js

48 ms

fx-rates.php

fx-rates.php

18 ms

css

css

23 ms

image-747.jpg

image-747.jpg

388 ms

q

q

248 ms

q

q

267 ms

q

q

272 ms

NU5xA6ty0a4

NU5xA6ty0a4

132 ms

2404649906_78f2e9ea4b.jpg

2404649906_78f2e9ea4b.jpg

125 ms

eu.png

eu.png

34 ms

4ef73ce977c87

4ef73ce977c87

269 ms

header_bg.png

header_bg.png

125 ms

rss_feed.png

rss_feed.png

128 ms

menu_bg.png

menu_bg.png

130 ms

menu_arrow_right.png

menu_arrow_right.png

130 ms

fade.png

fade.png

209 ms

read_more.png

read_more.png

227 ms

beach-sunglasses-sonnenbrille.jpg

beach-sunglasses-sonnenbrille.jpg

419 ms

airplane-vonunten.jpg

airplane-vonunten.jpg

379 ms

airport-warten-blackwhite.jpg

airport-warten-blackwhite.jpg

420 ms

pfc_logo300x300.png

pfc_logo300x300.png

376 ms

rss.jpg

rss.jpg

377 ms

blogger.jpg

blogger.jpg

415 ms

facebook_icon.png

facebook_icon.png

419 ms

googleplus.jpg

googleplus.jpg

419 ms

linkedin.jpg

linkedin.jpg

420 ms

paper-li.jpg

paper-li.jpg

506 ms

pinterest.jpg

pinterest.jpg

511 ms

RebelMouse.png

RebelMouse.png

511 ms

tumblr.jpg

tumblr.jpg

512 ms

twitter.jpg

twitter.jpg

513 ms

weebly.png

weebly.png

514 ms

wordpress.png

wordpress.png

597 ms

Drupallogo.gif

Drupallogo.gif

604 ms

timme_hosting_logo.png

timme_hosting_logo.png

605 ms

Newsletter260px.JPG

Newsletter260px.JPG

606 ms

translateelement.css

translateelement.css

49 ms

main.js

main.js

94 ms

s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff

s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff

30 ms

EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff

EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff

40 ms

au.png

au.png

49 ms

ch.png

ch.png

38 ms

gb.png

gb.png

36 ms

hk.png

hk.png

37 ms

jp.png

jp.png

37 ms

us.png

us.png

38 ms

footer_hightlight.png

footer_hightlight.png

133 ms

footer_divider.png

footer_divider.png

133 ms

piwik.js

piwik.js

426 ms

www-embed-player-vflRGs1ko.css

www-embed-player-vflRGs1ko.css

84 ms

www-embed-player.js

www-embed-player.js

112 ms

base.js

base.js

171 ms

element_main.js

element_main.js

43 ms

a-logo-amazon.png

a-logo-amazon.png

357 ms

513VlP3y7JL._AC_SR98,95_.jpg

513VlP3y7JL._AC_SR98,95_.jpg

33 ms

ir

ir

251 ms

json

json

248 ms

cart.gif

cart.gif

245 ms

json

json

227 ms

41JPUblH9jL._AC_SR98,95_.jpg

41JPUblH9jL._AC_SR98,95_.jpg

9 ms

json

json

219 ms

51UiSoQslCL._AC_SR98,95_.jpg

51UiSoQslCL._AC_SR98,95_.jpg

8 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

15 ms

ad_status.js

ad_status.js

47 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

58 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

71 ms

extlink.png

extlink.png

94 ms

translate_24dp.png

translate_24dp.png

68 ms

l

l

38 ms

cleardot.gif

cleardot.gif

12 ms

te_ctrl3.gif

te_ctrl3.gif

10 ms

loading.gif

loading.gif

19 ms

googlelogo_color_68x28dp.png

googlelogo_color_68x28dp.png

10 ms

Accessibility Review

travelink.de accessibility score

98

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.

Best Practices

travelink.de best practices score

83

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

Page has valid source maps

SEO Factors

travelink.de 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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Travelink.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Travelink.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

travelink.de

Open Graph description is not detected on the main page of TraveLink. 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: