Tools & Wizards About Us
lostcry.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

lostcry.com

Share Your Ancestor's Story | LostCry.com - Holocaust Stories, War Stories, And More

Page Load Speed

2.7 sec in total

First Response

23 ms

Resources Loaded

1.9 sec

Page Rendered

779 ms

lostcry.com screenshot

About Website

Welcome to lostcry.com homepage info - get ready to check Lost Cry best content right away, or after learning these important things about lostcry.com

LostCry.com is the only website which allows you to post your ancestor’s story of hardship. Read, share, learn and interact with true stories about people’s ancestors from the Holocaust, Civil War, Ar...

Visit lostcry.com

Key Findings

We analyzed Lostcry.com page load time and found that the first response time was 23 ms and then it took 2.7 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

lostcry.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value4.7 s

70/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

lostcry.com

23 ms

lostcry.com

1215 ms

css

57 ms

icon-font.min.css

127 ms

css

26 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 82% of them (89 requests) were addressed to the original Lostcry.com, 5% (5 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Lostcry.com.

Page Optimization Overview & Recommendations

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

Content Size

2.5 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-90%

Potential reduce by 102.8 kB

  • Original 114.8 kB
  • After minification 110.1 kB
  • After compression 12.0 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 102.8 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 1.7 kB

  • Original 2.1 MB
  • After minification 2.1 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 Cry images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 45.1 kB

  • Original 148.4 kB
  • After minification 148.4 kB
  • After compression 103.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 45.1 kB or 30% of the original size.

CSS Optimization

-12%

Potential reduce by 11.5 kB

  • Original 96.1 kB
  • After minification 96.1 kB
  • After compression 84.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. Lostcry.com needs all CSS files to be minified and compressed as it can save up to 11.5 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (42%)

Requests Now

99

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lostcry.com

lostcry.com

23 ms

lostcry.com

lostcry.com

1215 ms

css

css

57 ms

icon-font.min.css

icon-font.min.css

127 ms

css

css

26 ms

js

js

82 ms

style.css

style.css

25 ms

tooltipster.css

tooltipster.css

32 ms

quotemention.css

quotemention.css

39 ms

editor.css

editor.css

42 ms

vanillicon.css

vanillicon.css

40 ms

signature.css

signature.css

33 ms

buttonbar.css

buttonbar.css

39 ms

custom.css

custom.css

45 ms

reactions.css

reactions.css

44 ms

1579457819.css

1579457819.css

56 ms

hotthreads.css

hotthreads.css

52 ms

jquery.min.js

jquery.min.js

44 ms

jquery.form.js

jquery.form.js

49 ms

jquery.popup.js

jquery.popup.js

46 ms

jquery.gardenhandleajaxform.js

jquery.gardenhandleajaxform.js

49 ms

jquery.atwho.js

jquery.atwho.js

52 ms

global.js

global.js

70 ms

discussions.js

discussions.js

73 ms

buttonbar.js

buttonbar.js

56 ms

jquery.hotkeys.js

jquery.hotkeys.js

61 ms

friendships.js

friendships.js

98 ms

hotthreadswidget.js

hotthreadswidget.js

62 ms

editor.js

editor.js

73 ms

jquery.ui.widget.js

jquery.ui.widget.js

67 ms

jquery.iframe-transport.js

jquery.iframe-transport.js

66 ms

jquery.fileupload.js

jquery.fileupload.js

97 ms

showallemojis.js

showallemojis.js

98 ms

css

css

41 ms

css

css

52 ms

js

js

48 ms

analytics.js

analytics.js

19 ms

bootstrap.css

bootstrap.css

73 ms

bootstrap-theme.css

bootstrap-theme.css

33 ms

steamicons.css

steamicons.css

32 ms

overdose.css

overdose.css

23 ms

steamenu.css

steamenu.css

6 ms

steamenumob.css

steamenumob.css

7 ms

steamcustom.css

steamcustom.css

26 ms

pe-icon-7-stroke.css

pe-icon-7-stroke.css

30 ms

animate.css

animate.css

28 ms

collect

collect

80 ms

logo.png

logo.png

278 ms

nAM4X6B4U8OMQ.JPG

nAM4X6B4U8OMQ.JPG

31 ms

n2R0I9PU73T6R.jpg

n2R0I9PU73T6R.jpg

32 ms

pexels-photo-175773.jpeg

pexels-photo-175773.jpeg

149 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

33 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

53 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

116 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

145 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

144 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

144 ms

101108418ffb71bda7efc4eb46bd188b.svg

101108418ffb71bda7efc4eb46bd188b.svg

135 ms

poland-2421090__340.jpg

poland-2421090__340.jpg

80 ms

smiley.png

smiley.png

14 ms

blush.png

blush.png

15 ms

relaxed.png

relaxed.png

11 ms

grin.png

grin.png

11 ms

joy.png

joy.png

12 ms

sweat_smile.png

sweat_smile.png

16 ms

yum.png

yum.png

23 ms

relieved.png

relieved.png

19 ms

love.png

love.png

16 ms

smirk.png

smirk.png

17 ms

expressionless.png

expressionless.png

23 ms

unamused.png

unamused.png

22 ms

sweat.png

sweat.png

25 ms

pensive.png

pensive.png

21 ms

kissing.png

kissing.png

24 ms

kissing_heart.png

kissing_heart.png

28 ms

kissing_smiling_eyes.png

kissing_smiling_eyes.png

25 ms

kissing_closed_eyes.png

kissing_closed_eyes.png

25 ms

tongue.png

tongue.png

28 ms

worried.png

worried.png

30 ms

angry.png

angry.png

26 ms

rage.png

rage.png

25 ms

persevere.png

persevere.png

26 ms

triumph.png

triumph.png

28 ms

frowning.png

frowning.png

30 ms

anguished.png

anguished.png

31 ms

fearful.png

fearful.png

31 ms

weary.png

weary.png

31 ms

sleepy.png

sleepy.png

32 ms

tired_face.png

tired_face.png

32 ms

bawling.png

bawling.png

33 ms

hushed.png

hushed.png

33 ms

cold_sweat.png

cold_sweat.png

34 ms

scream.png

scream.png

36 ms

astonished.png

astonished.png

35 ms

flushed.png

flushed.png

34 ms

sleeping.png

sleeping.png

28 ms

dizzy.png

dizzy.png

29 ms

no_mouth.png

no_mouth.png

28 ms

mask.png

mask.png

27 ms

star.png

star.png

25 ms

cookie.png

cookie.png

25 ms

warning.png

warning.png

26 ms

mrgreen.png

mrgreen.png

25 ms

heartbreak.png

heartbreak.png

22 ms

+1.png

+1.png

21 ms

-1.png

-1.png

22 ms

grey_question.png

grey_question.png

21 ms

trollface.png

trollface.png

21 ms

Accessibility Review

lostcry.com accessibility score

57

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

lostcry.com best practices score

67

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

lostcry.com SEO score

54

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

Language and Encoding

  • Language Detected

    EN

  • 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 Lostcry.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Lostcry.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

lostcry.com

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