Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

storykeeper.com

Your Life Story Book | Memory Keepsake Book - StoryKeeper - Make Memories Last Forever USA

Page Load Speed

7.1 sec in total

First Response

2.2 sec

Resources Loaded

3.8 sec

Page Rendered

1.2 sec

About Website

Visit storykeeper.com now to see the best up-to-date Story Keeper content and also check out these interesting facts you probably never knew about storykeeper.com

Create a memory-based keepsake book by answering questions each week. Share stories with your loved ones and preserve your personal history

Visit storykeeper.com

Key Findings

We analyzed Storykeeper.com page load time and found that the first response time was 2.2 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

storykeeper.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,780 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

storykeeper.com

2213 ms

css;charset=utf-8;base64,LypibGFuayov

1 ms

dashicons.min.css

343 ms

extra.min.css

234 ms

front.css

235 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 96% of them (50 requests) were addressed to the original Storykeeper.com, 4% (2 requests) were made to . The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Storykeeper.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 980.2 kB (61%)

Content Size

1.6 MB

After Optimization

635.3 kB

In fact, the total size of Storykeeper.com main page is 1.6 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. HTML takes 525.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 416.5 kB

  • Original 525.5 kB
  • After minification 514.1 kB
  • After compression 109.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 416.5 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 16.8 kB

  • Original 351.8 kB
  • After minification 335.0 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. Story Keeper images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 187.5 kB

  • Original 307.5 kB
  • After minification 299.3 kB
  • After compression 120.1 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 187.5 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 359.4 kB

  • Original 430.7 kB
  • After minification 402.3 kB
  • After compression 71.3 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. Storykeeper.com needs all CSS files to be minified and compressed as it can save up to 359.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (90%)

Requests Now

48

After Optimization

5

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

Accessibility Review

storykeeper.com 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.

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

storykeeper.com 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

storykeeper.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a valid hreflang

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Storykeeper.com 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 Storykeeper.com 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 data is detected on the main page of Story Keeper. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: