Tools & Wizards About Us
lost-places.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

lost-places.com

Home » lost-places.com - Bilderarchiv von verlassen Orten

Page Load Speed

2.7 sec in total

First Response

367 ms

Resources Loaded

1.9 sec

Page Rendered

495 ms

lost-places.com screenshot

About Website

Click here to check amazing Lost Places content for Germany. Otherwise, check out these important facts you probably never knew about lost-places.com

Visit lost-places.com

Key Findings

We analyzed Lost-places.com page load time and found that the first response time was 367 ms and then it took 2.3 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

lost-places.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value20.5 s

0/100

25%

SI (Speed Index)

Value17.4 s

0/100

10%

TBT (Total Blocking Time)

Value7,080 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value26.6 s

0/100

10%

Network Requests Diagram

lost-places.com

367 ms

adsbygoogle.js

17 ms

background.gif

834 ms

lostplacescom_20.png

830 ms

lostplacescommain_01.gif

326 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 68% of them (46 requests) were addressed to the original Lost-places.com, 7% (5 requests) were made to Pagead2.googlesyndication.com and 6% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Lost-places.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.0 kB (7%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Lost-places.com main page is 1.7 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. 40% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 12.5 kB

  • Original 17.1 kB
  • After minification 17.1 kB
  • After compression 4.6 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 12.5 kB or 73% of the original size.

Image Optimization

-6%

Potential reduce by 99.9 kB

  • Original 1.6 MB
  • After minification 1.5 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. Lost Places images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 6.6 kB

  • Original 72.9 kB
  • After minification 72.8 kB
  • After compression 66.3 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 9 (13%)

Requests Now

67

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lost Places. 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 as a result speed up the page load time.

Network Requests Diagram

lost-places.com

lost-places.com

367 ms

adsbygoogle.js

adsbygoogle.js

17 ms

background.gif

background.gif

834 ms

lostplacescom_20.png

lostplacescom_20.png

830 ms

lostplacescommain_01.gif

lostplacescommain_01.gif

326 ms

lostplacescom_02.gif

lostplacescom_02.gif

210 ms

lostplacescommain_03.gif

lostplacescommain_03.gif

577 ms

lostplacescommain_04.gif

lostplacescommain_04.gif

331 ms

lostplacescommain_05.gif

lostplacescommain_05.gif

334 ms

lostplacescommain_06.gif

lostplacescommain_06.gif

542 ms

lostplacescom_07.gif

lostplacescom_07.gif

465 ms

lostplacescom_08.gif

lostplacescom_08.gif

466 ms

lostplacescom_09.gif

lostplacescom_09.gif

575 ms

lostplacescom_10.gif

lostplacescom_10.gif

574 ms

lostplacescom_11.gif

lostplacescom_11.gif

638 ms

lostplacescom_12.gif

lostplacescom_12.gif

648 ms

lostplacescom_13.gif

lostplacescom_13.gif

750 ms

lostplacescom_14.gif

lostplacescom_14.gif

649 ms

lostplacescom_15.gif

lostplacescom_15.gif

741 ms

lostplacescom_16.gif

lostplacescom_16.gif

749 ms

lostplacescom_17.gif

lostplacescom_17.gif

753 ms

news.png

news.png

949 ms

lostplacescom_19.gif

lostplacescom_19.gif

852 ms

box.png

box.png

859 ms

kalender2016.jpg

kalender2016.jpg

1280 ms

widgets.js

widgets.js

113 ms

sonderformat.png

sonderformat.png

1462 ms

v.gif

v.gif

937 ms

v.gif

v.gif

964 ms

v.gif

v.gif

992 ms

v.gif

v.gif

1079 ms

v.gif

v.gif

1071 ms

v.gif

v.gif

1085 ms

v.gif

v.gif

1110 ms

v.gif

v.gif

1180 ms

v.gif

v.gif

1192 ms

v.gif

v.gif

1200 ms

lostplacescom_21.gif

lostplacescom_21.gif

1213 ms

lostplacescom_22.gif

lostplacescom_22.gif

1282 ms

ca-pub-2731258391356879.js

ca-pub-2731258391356879.js

32 ms

zrt_lookup.html

zrt_lookup.html

25 ms

show_ads_impl.js

show_ads_impl.js

50 ms

ads

ads

278 ms

osd.js

osd.js

17 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

118 ms

ads

ads

239 ms

lostplacescom_23.png

lostplacescom_23.png

1103 ms

syndication

syndication

95 ms

400005057472520192

400005057472520192

187 ms

lostplacescom_24.gif

lostplacescom_24.gif

992 ms

lostplacescom_25.gif

lostplacescom_25.gif

998 ms

lostplacescom_26.gif

lostplacescom_26.gif

1058 ms

m_js_controller.js

m_js_controller.js

18 ms

abg.js

abg.js

33 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

85 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

36 ms

s

s

27 ms

x_button_blue2.svg

x_button_blue2.svg

25 ms

lostplacescom_27.gif

lostplacescom_27.gif

933 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

4 ms

lostplacescom_28.gif

lostplacescom_28.gif

943 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

35 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

66 ms

Logokleinkreis_normal.jpg

Logokleinkreis_normal.jpg

213 ms

lostplacescom_29.gif

lostplacescom_29.gif

877 ms

lostplacescom_30.gif

lostplacescom_30.gif

857 ms

lostplacescom_31.gif

lostplacescom_31.gif

920 ms

jot

jot

23 ms

Accessibility Review

lost-places.com accessibility score

70

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

lost-places.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

lost-places.com SEO score

79

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 uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lost-places.com 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 Lost-places.com main page’s claimed encoding is iso-8859-1. 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

lost-places.com

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