Tools & Wizards About Us

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

gram.org

GitHub - gramlang/gram: A programming language for distributed systems.

Page Load Speed

959 ms in total

First Response

51 ms

Resources Loaded

632 ms

Page Rendered

276 ms

About Website

Visit gram.org now to see the best up-to-date Gram content and also check out these interesting facts you probably never knew about gram.org

A programming language for distributed systems. Contribute to gramlang/gram development by creating an account on GitHub.

Visit gram.org

Key Findings

We analyzed Gram.org page load time and found that the first response time was 51 ms and then it took 908 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

gram.org performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

74/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

gram.org

51 ms

439 ms

light-5178aee0ee76.css

49 ms

dark-217d4f9c8e70.css

51 ms

primer-7c8c4d2c4d7e.css

76 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Gram.org, 94% (45 requests) were made to Github.githubassets.com and 4% (2 requests) were made to Github.com. The less responsive or slowest element that took the longest time to load (439 ms) relates to the external source Github.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 178.2 kB (54%)

Content Size

328.3 kB

After Optimization

150.1 kB

  • HTML
  • CSS

In fact, the total size of Gram.org main page is 328.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. 65% of websites need less resources to load. HTML takes 207.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 173.2 kB

  • Original 207.9 kB
  • After minification 197.4 kB
  • After compression 34.7 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 173.2 kB or 83% of the original size.

CSS Optimization

-4%

Potential reduce by 5.0 kB

  • Original 120.4 kB
  • After minification 116.0 kB
  • After compression 115.4 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. Gram.org has all CSS files already compressed.

Requests Breakdown

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

Requests Now

46

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

gram.org accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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

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

gram.org SEO score

91

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 Gram.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 Gram.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 data is detected on the main page of Gram. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: