Report Summary

  • 56

    Performance

    Renders faster than
    74% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 93% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

gatsbyjs.org

The Fastest Frontend for the Headless Web | Gatsby

Page Load Speed

9.6 sec in total

First Response

194 ms

Resources Loaded

8.5 sec

Page Rendered

943 ms

gatsbyjs.org screenshot

About Website

Welcome to gatsbyjs.org homepage info - get ready to check Gatsby Js best content for United States right away, or after learning these important things about gatsbyjs.org

Gatsby is a React-based open source framework with performance, scalability and security built-in. Collaborate, build and deploy 1000x faster with Gatsby Cloud.

Visit gatsbyjs.org

Key Findings

We analyzed Gatsbyjs.org page load time and found that the first response time was 194 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

gatsbyjs.org performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value3,310 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

gatsbyjs.org

194 ms

gatsbyjs.org

275 ms

www.gatsbyjs.org

1445 ms

component---src-pages-index-js-5f4b9e33866956edf0d8.js

357 ms

3-d8717880414eb9b638c6.js

731 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 90% of them (18 requests) were addressed to the original Gatsbyjs.org, 5% (1 request) were made to Earlymonitoring.firebaseapp.com and 5% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Gatsbyjs.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 123.4 kB (69%)

Content Size

177.5 kB

After Optimization

54.1 kB

In fact, the total size of Gatsbyjs.org main page is 177.5 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. HTML takes 146.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 116.4 kB

  • Original 146.3 kB
  • After minification 145.7 kB
  • After compression 29.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 116.4 kB or 80% of the original size.

JavaScript Optimization

-22%

Potential reduce by 7.0 kB

  • Original 31.3 kB
  • After minification 31.2 kB
  • After compression 24.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 7.0 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (83%)

Requests Now

12

After Optimization

2

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

Accessibility Review

gatsbyjs.org accessibility score

97

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

Best Practices

gatsbyjs.org 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

gatsbyjs.org 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 Gatsbyjs.org 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 Gatsbyjs.org 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 Gatsby Js. 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: