Tools & Wizards About Us
ferngeschehen.de screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

ferngeschehen.de

Ferngeschehen Reiseblog, Reiseberichte und Reisetipps

Page Load Speed

3.5 sec in total

First Response

360 ms

Resources Loaded

2.7 sec

Page Rendered

466 ms

ferngeschehen.de screenshot

About Website

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

Ob Reiseberichte, Reisefotografie, Reisetipps oder clevere Tipps für günstige Flüge. Alles fürs Reisen: Für Träumer. Für Entdecker. Für dich!

Visit ferngeschehen.de

Key Findings

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

Performance Metrics

ferngeschehen.de performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value490 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

ferngeschehen.de

360 ms

ferngeschehen.de

584 ms

gtm.js

68 ms

sprite.php

234 ms

image-renderer.css

334 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 43% of them (37 requests) were addressed to the original Ferngeschehen.de, 55% (48 requests) were made to Data.ferngeschehen.de and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Data.ferngeschehen.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 83.6 kB (6%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-86%

Potential reduce by 73.5 kB

  • Original 85.3 kB
  • After minification 85.0 kB
  • After compression 11.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 73.5 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 1.6 kB

  • Original 1.3 MB
  • After minification 1.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. Ferngeschehen images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 8.5 kB

  • Original 39.4 kB
  • After minification 39.4 kB
  • After compression 30.9 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 8.5 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (48%)

Requests Now

83

After Optimization

43

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ferngeschehen.de

ferngeschehen.de

360 ms

ferngeschehen.de

ferngeschehen.de

584 ms

gtm.js

gtm.js

68 ms

sprite.php

sprite.php

234 ms

image-renderer.css

image-renderer.css

334 ms

assistant.woff

assistant.woff

449 ms

assistant-bold.woff

assistant-bold.woff

444 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

19 ms

lazyload.min.js

lazyload.min.js

335 ms

cedc72eca8b9fe78b181b2ccfecf5c77.js

cedc72eca8b9fe78b181b2ccfecf5c77.js

898 ms

au.png

au.png

570 ms

rundreise-norwegen-schweden-01-600x400.jpg

rundreise-norwegen-schweden-01-600x400.jpg

116 ms

lofoten-01-1200x800.jpg

lofoten-01-1200x800.jpg

441 ms

reisebericht-runde-01-1200x800.jpg

reisebericht-runde-01-1200x800.jpg

562 ms

reisebericht-jostedalsbreen-01-1200x800.jpg

reisebericht-jostedalsbreen-01-1200x800.jpg

651 ms

rundreise-namibia-1-1200x800.jpeg

rundreise-namibia-1-1200x800.jpeg

433 ms

reisebericht-kapstadt-01-1200x800.jpg

reisebericht-kapstadt-01-1200x800.jpg

562 ms

namib-wueste-15-1200x800.jpg

namib-wueste-15-1200x800.jpg

656 ms

swakopmund-1-1-1200x800.jpg

swakopmund-1-1-1200x800.jpg

663 ms

spitzkoppe-1-1200x800.jpeg

spitzkoppe-1-1200x800.jpeg

671 ms

bg.png

bg.png

584 ms

cn.png

cn.png

586 ms

cr.png

cr.png

592 ms

dk.png

dk.png

590 ms

de.png

de.png

590 ms

gb.png

gb.png

682 ms

ee.png

ee.png

693 ms

fj.png

fj.png

696 ms

fr.png

fr.png

699 ms

in.png

in.png

700 ms

id.png

id.png

700 ms

ie.png

ie.png

799 ms

il.png

il.png

805 ms

it.png

it.png

805 ms

jp.png

jp.png

809 ms

kh.png

kh.png

809 ms

co.png

co.png

810 ms

la.png

la.png

909 ms

lv.png

lv.png

915 ms

lt.png

lt.png

915 ms

my.png

my.png

918 ms

mt.png

mt.png

917 ms

ma.png

ma.png

918 ms

mm.png

mm.png

1029 ms

na.png

na.png

1030 ms

nz.png

nz.png

1031 ms

ni.png

ni.png

1031 ms

nl.png

nl.png

1030 ms

at.png

at.png

1040 ms

pa.png

pa.png

1111 ms

pt.png

pt.png

1132 ms

ro.png

ro.png

1133 ms

ru.png

ru.png

1137 ms

se.png

se.png

1138 ms

ch.png

ch.png

1140 ms

reset.css

reset.css

524 ms

styles.css

styles.css

531 ms

modules.css

modules.css

620 ms

single.css

single.css

629 ms

mburger.css

mburger.css

634 ms

mmenu.css

mmenu.css

642 ms

slick.css

slick.css

645 ms

responsive.css

responsive.css

644 ms

fixes.css

fixes.css

729 ms

dark.css

dark.css

737 ms

block_core.css

block_core.css

747 ms

block_fern_affiliate.css

block_fern_affiliate.css

747 ms

block_fern_comparison.css

block_fern_comparison.css

749 ms

block_fern_map.css

block_fern_map.css

748 ms

block_fern_question.css

block_fern_question.css

839 ms

block_fern_space.css

block_fern_space.css

845 ms

block_fern_teaser.css

block_fern_teaser.css

859 ms

block_fern_toc.css

block_fern_toc.css

861 ms

block_misc.css

block_misc.css

862 ms

mapbox-gl.css

mapbox-gl.css

862 ms

sg.png

sg.png

662 ms

es.png

es.png

665 ms

lk.png

lk.png

663 ms

za.png

za.png

664 ms

kr.png

kr.png

664 ms

tw.png

tw.png

665 ms

th.png

th.png

651 ms

cz.png

cz.png

665 ms

hu.png

hu.png

664 ms

us.png

us.png

664 ms

va.png

va.png

663 ms

vn.png

vn.png

665 ms

Accessibility Review

ferngeschehen.de accessibility score

95

Accessibility Issues

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

Links do not have a discernible name

Best Practices

ferngeschehen.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ferngeschehen.de SEO score

90

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

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

ferngeschehen.de

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