Tools & Wizards About Us
gatsbystorefront.com screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

gatsbystorefront.com

Shopify & Gatsby for blazing fast, modern e-commerce

Page Load Speed

20.4 sec in total

First Response

79 ms

Resources Loaded

20 sec

Page Rendered

286 ms

gatsbystorefront.com screenshot

About Website

Welcome to gatsbystorefront.com homepage info - get ready to check Gatsby Storefront best content right away, or after learning these important things about gatsbystorefront.com

Build a blazing fast online store with Shopify & Gatsby JS. Integrate with Contentful, Yotpo, and 2000+ Gatsby JS plugins.

Visit gatsbystorefront.com

Key Findings

We analyzed Gatsbystorefront.com page load time and found that the first response time was 79 ms and then it took 20.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

gatsbystorefront.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value4,210 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

gatsbystorefront.com

79 ms

plausible.js

19910 ms

gtm.js

76 ms

inter.css

38 ms

polyfill-27c3d6cf2a21ec3cc226.js

21 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 43% of them (9 requests) were addressed to the original Gatsbystorefront.com, 19% (4 requests) were made to Mc.yandex.com and 10% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Stats.gatsbystorefront.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 67.1 kB (21%)

Content Size

326.3 kB

After Optimization

259.2 kB

  • HTML
  • JavaScript

In fact, the total size of Gatsbystorefront.com main page is 326.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. 40% of websites need less resources to load. Javascripts take 234.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 67.0 kB

  • Original 91.6 kB
  • After minification 91.5 kB
  • After compression 24.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 67.0 kB or 73% of the original size.

JavaScript Optimization

-0%

Potential reduce by 157 B

  • Original 234.7 kB
  • After minification 234.7 kB
  • After compression 234.6 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 11 (61%)

Requests Now

18

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gatsbystorefront.com

gatsbystorefront.com

79 ms

plausible.js

plausible.js

19910 ms

gtm.js

gtm.js

76 ms

inter.css

inter.css

38 ms

polyfill-27c3d6cf2a21ec3cc226.js

polyfill-27c3d6cf2a21ec3cc226.js

21 ms

component---src-pages-index-js-64f658627e7b9716a0c9.js

component---src-pages-index-js-64f658627e7b9716a0c9.js

27 ms

073e628acd71ed43e16ebe395297a46b4cbb177b-f68bd91e1a2635022e3b.js

073e628acd71ed43e16ebe395297a46b4cbb177b-f68bd91e1a2635022e3b.js

78 ms

30f3b68d612e228f4e21318f26872c6cec451be2-20ddad13547dc05ee1e2.js

30f3b68d612e228f4e21318f26872c6cec451be2-20ddad13547dc05ee1e2.js

77 ms

app-61bb4a0590b774b1af9e.js

app-61bb4a0590b774b1af9e.js

102 ms

styles-719967e2ea75025a1d91.js

styles-719967e2ea75025a1d91.js

77 ms

framework-ddff9c6a94258f6c8286.js

framework-ddff9c6a94258f6c8286.js

49 ms

webpack-runtime-14467fbfa8e0d93a0fd5.js

webpack-runtime-14467fbfa8e0d93a0fd5.js

32 ms

js

js

83 ms

analytics.js

analytics.js

19 ms

tag.js

tag.js

813 ms

wTwFYd9nYQ

wTwFYd9nYQ

75 ms

collect

collect

84 ms

advert.gif

advert.gif

667 ms

sync_cookie_image_decide

sync_cookie_image_decide

159 ms

1

1

134 ms

1

1

256 ms

Accessibility Review

gatsbystorefront.com accessibility score

90

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

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

gatsbystorefront.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

High

Page has valid source maps

SEO Factors

gatsbystorefront.com SEO score

100

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gatsbystorefront.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 Gatsbystorefront.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

gatsbystorefront.com

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