Tools & Wizards About Us
gefunden-verloren.de screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

gefunden-verloren.de

gefunden-verloren.de – Das Onlinefundbüro

Page Load Speed

3 sec in total

First Response

444 ms

Resources Loaded

2.3 sec

Page Rendered

251 ms

gefunden-verloren.de screenshot

About Website

Welcome to gefunden-verloren.de homepage info - get ready to check Gefunden Verloren best content for Germany right away, or after learning these important things about gefunden-verloren.de

Onlinefundbüro, hier können Sie kostenlos verlorene und gefundene Sachen suchen oder eintragen

Visit gefunden-verloren.de

Key Findings

We analyzed Gefunden-verloren.de page load time and found that the first response time was 444 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

gefunden-verloren.de performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.287

42/100

15%

TTI (Time to Interactive)

Value2.1 s

99/100

10%

Network Requests Diagram

gefunden-verloren.de

444 ms

style.css

123 ms

plusone.js

106 ms

addthis_widget.js

20 ms

go.js

349 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Gefunden-verloren.de, 31% (38 requests) were made to Onlywire.com and 11% (13 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (608 ms) belongs to the original domain Gefunden-verloren.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 515.2 kB (59%)

Content Size

879.3 kB

After Optimization

364.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gefunden-verloren.de main page is 879.3 kB. 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 597.3 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 80.3 kB

  • Original 109.6 kB
  • After minification 109.4 kB
  • After compression 29.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 80.3 kB or 73% of the original size.

Image Optimization

-20%

Potential reduce by 34.6 kB

  • Original 169.4 kB
  • After minification 134.8 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. Obviously, Gefunden Verloren needs image optimization as it can save up to 34.6 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 398.0 kB

  • Original 597.3 kB
  • After minification 536.1 kB
  • After compression 199.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 398.0 kB or 67% of the original size.

CSS Optimization

-76%

Potential reduce by 2.3 kB

  • Original 3.0 kB
  • After minification 2.5 kB
  • After compression 728 B

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. Gefunden-verloren.de needs all CSS files to be minified and compressed as it can save up to 2.3 kB or 76% of the original size.

Requests Breakdown

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

Requests Now

109

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gefunden-verloren.de

gefunden-verloren.de

444 ms

style.css

style.css

123 ms

plusone.js

plusone.js

106 ms

addthis_widget.js

addthis_widget.js

20 ms

go.js

go.js

349 ms

getads.js

getads.js

19 ms

button_18363

button_18363

46 ms

ads.js

ads.js

235 ms

solo.js

solo.js

305 ms

mad1.php

mad1.php

477 ms

load.js

load.js

63 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

54 ms

btn_donateCC_LG.gif

btn_donateCC_LG.gif

157 ms

pixel.gif

pixel.gif

55 ms

dmd_2012_mach-mit_140x140_680.jpg

dmd_2012_mach-mit_140x140_680.jpg

586 ms

header1.jpg

header1.jpg

123 ms

feed-icon.png

feed-icon.png

245 ms

Twitterbutton1.png

Twitterbutton1.png

608 ms

loader.js

loader.js

17 ms

like.php

like.php

142 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

18 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

13 ms

t.js

t.js

96 ms

impr

impr

102 ms

adex.js

adex.js

255 ms

rtb

rtb

95 ms

match

match

92 ms

bannerad-3-2056.js

bannerad-3-2056.js

433 ms

loadImages.js

loadImages.js

2 ms

0

0

92 ms

t.js

t.js

86 ms

t.js

t.js

170 ms

nuggad

nuggad

91 ms

analytic.js

analytic.js

95 ms

169 ms

1.gif

1.gif

173 ms

pixel

pixel

14 ms

redirect

redirect

222 ms

pixel

pixel

12 ms

ga.js

ga.js

25 ms

cm.gif

cm.gif

86 ms

2.gif

2.gif

86 ms

button_s.css

button_s.css

29 ms

__utm.gif

__utm.gif

30 ms

onlywire_logo_small_square.png

onlywire_logo_small_square.png

32 ms

2.gif

2.gif

88 ms

ads-common.js

ads-common.js

164 ms

115

115

92 ms

redirect

redirect

414 ms

cm

cm

187 ms

all.js

all.js

52 ms

88-7.gif

88-7.gif

295 ms

butt2151.jpg

butt2151.jpg

131 ms

88-31.gif

88-31.gif

287 ms

boost

boost

41 ms

300lo.json

300lo.json

42 ms

214.ffb370adb4977b3c7b93.js

214.ffb370adb4977b3c7b93.js

31 ms

202.75cf69f283ea2d035e0f.js

202.75cf69f283ea2d035e0f.js

30 ms

110.211c6510f17ce975755e.js

110.211c6510f17ce975755e.js

29 ms

56.47bbbe7d71e40b5177c4.js

56.47bbbe7d71e40b5177c4.js

32 ms

209.e7c073a738c1820368ff.js

209.e7c073a738c1820368ff.js

30 ms

188.d49c726ff471d1e35507.js

188.d49c726ff471d1e35507.js

28 ms

253.ba62368867277ab9d8db.js

253.ba62368867277ab9d8db.js

32 ms

137.aca79987e2754a62c172.js

137.aca79987e2754a62c172.js

27 ms

226.45d25142a9af46264f56.js

226.45d25142a9af46264f56.js

27 ms

229.5f773d80b468beda62c7.js

229.5f773d80b468beda62c7.js

27 ms

273.33dc1e6c32820cabb584.js

273.33dc1e6c32820cabb584.js

29 ms

data

data

101 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

51 ms

fastbutton

fastbutton

98 ms

butt20032.gif

butt20032.gif

168 ms

sh.07f0d9bf220d07a763adad1e.html

sh.07f0d9bf220d07a763adad1e.html

53 ms

29 ms

postmessageRelay

postmessageRelay

73 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

43 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

43 ms

xd_arbiter.php

xd_arbiter.php

66 ms

xd_arbiter.php

xd_arbiter.php

75 ms

ismall-close.png

ismall-close.png

42 ms

datetimepicker_css_compressed.js

datetimepicker_css_compressed.js

30 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

98 ms

facebook.png

facebook.png

35 ms

facebook-page.png

facebook-page.png

50 ms

facebook-group.png

facebook-group.png

51 ms

twitter.png

twitter.png

36 ms

google-plus-page-oauth.png

google-plus-page-oauth.png

51 ms

pinterest.png

pinterest.png

49 ms

linkedin.png

linkedin.png

50 ms

linkedin-pages.png

linkedin-pages.png

49 ms

aol-lifestream.png

aol-lifestream.png

56 ms

appnet.png

appnet.png

54 ms

bitly.png

bitly.png

54 ms

blogger.png

blogger.png

54 ms

delicious.png

delicious.png

56 ms

diigo.png

diigo.png

55 ms

feedspot.png

feedspot.png

57 ms

folkd.png

folkd.png

62 ms

hi5.png

hi5.png

62 ms

imgur.png

imgur.png

61 ms

instapaper.png

instapaper.png

61 ms

linkagogo.png

linkagogo.png

61 ms

livejournal.png

livejournal.png

61 ms

medium.png

medium.png

113 ms

myaol.png

myaol.png

62 ms

newsvine.png

newsvine.png

63 ms

plurk.png

plurk.png

63 ms

getpocket.png

getpocket.png

64 ms

reddit.png

reddit.png

64 ms

skyrock.png

skyrock.png

64 ms

tagged.png

tagged.png

64 ms

tumblr.png

tumblr.png

65 ms

wordpress.png

wordpress.png

66 ms

xing.png

xing.png

65 ms

611GO+yZqCL._SL70_.jpg

611GO+yZqCL._SL70_.jpg

39 ms

173 ms

thumb-no-image._SL70_.jpg

thumb-no-image._SL70_.jpg

38 ms

51ub7-WrBnL._SL70_.jpg

51ub7-WrBnL._SL70_.jpg

37 ms

575

575

102 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

52 ms

rpc:shindig_random.js

rpc:shindig_random.js

50 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

2.gif

2.gif

87 ms

Accessibility Review

gefunden-verloren.de accessibility score

96

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

Best Practices

gefunden-verloren.de best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

gefunden-verloren.de SEO score

92

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gefunden-verloren.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Gefunden-verloren.de main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

gefunden-verloren.de

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