Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

lostplace.net

Lost Places | by Dominik Wojcik

Page Load Speed

4.4 sec in total

First Response

581 ms

Resources Loaded

3.5 sec

Page Rendered

320 ms

lostplace.net screenshot

About Website

Welcome to lostplace.net homepage info - get ready to check Lost Place best content right away, or after learning these important things about lostplace.net

Visit lostplace.net

Key Findings

We analyzed Lostplace.net page load time and found that the first response time was 581 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

lostplace.net performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value90 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.526

14/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

www.lostplace.net

581 ms

prettyPhoto.css

109 ms

styles.css

209 ms

ls-shortcodes.css

216 ms

genericons.css

212 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 85% of them (39 requests) were addressed to the original Lostplace.net, 11% (5 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Lostplace.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (22%)

Content Size

8.2 MB

After Optimization

6.4 MB

In fact, the total size of Lostplace.net main page is 8.2 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. 35% of websites need less resources to load. Images take 7.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 21.2 kB

  • Original 26.0 kB
  • After minification 24.1 kB
  • After compression 4.8 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 21.2 kB or 81% of the original size.

Image Optimization

-20%

Potential reduce by 1.5 MB

  • Original 7.8 MB
  • After minification 6.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. Obviously, Lost Place needs image optimization as it can save up to 1.5 MB 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 162.4 kB

  • Original 242.3 kB
  • After minification 233.2 kB
  • After compression 79.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 162.4 kB or 67% of the original size.

CSS Optimization

-77%

Potential reduce by 106.1 kB

  • Original 137.0 kB
  • After minification 111.7 kB
  • After compression 30.9 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. Lostplace.net needs all CSS files to be minified and compressed as it can save up to 106.1 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (51%)

Requests Now

39

After Optimization

19

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

Accessibility Review

lostplace.net accessibility score

95

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

lostplace.net 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

SEO Factors

lostplace.net SEO score

83

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lostplace.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Lostplace.net 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

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