Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

gbt.org

ETS- Great Books Education

Page Load Speed

987 ms in total

First Response

100 ms

Resources Loaded

621 ms

Page Rendered

266 ms

gbt.org screenshot

About Website

Visit gbt.org now to see the best up-to-date Gbt content for United States and also check out these interesting facts you probably never knew about gbt.org

Escondido Tutorial Service delivers Great Books education to homeschool families through the Internet and localy.

Visit gbt.org

Key Findings

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

Performance Metrics

gbt.org performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value30.3 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value5,030 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.104

88/100

15%

TTI (Time to Interactive)

Value27.3 s

0/100

10%

Network Requests Diagram

gbt.org

100 ms

style.css

59 ms

style.css

110 ms

insert1.jpg

71 ms

videoseries

155 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 50% of them (7 requests) were addressed to the original Gbt.org, 14% (2 requests) were made to S.ytimg.com and 14% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (155 ms) relates to the external source Youtube.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 347.2 kB (63%)

Content Size

553.3 kB

After Optimization

206.0 kB

In fact, the total size of Gbt.org main page is 553.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. 25% of websites need less resources to load. CSS take 249.1 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 5.7 kB

  • Original 7.7 kB
  • After minification 7.3 kB
  • After compression 2.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 5.7 kB or 74% of the original size.

Image Optimization

-7%

Potential reduce by 6.8 kB

  • Original 100.9 kB
  • After minification 94.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. Gbt images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 128.4 kB

  • Original 195.6 kB
  • After minification 195.5 kB
  • After compression 67.2 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 128.4 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 206.3 kB

  • Original 249.1 kB
  • After minification 248.4 kB
  • After compression 42.7 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. Gbt.org needs all CSS files to be minified and compressed as it can save up to 206.3 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gbt. According to our analytics all requests are already optimized.

Accessibility Review

gbt.org accessibility score

78

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

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

SEO Factors

gbt.org SEO score

81

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

Links do not have descriptive text

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

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gbt.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 Gbt.org main page’s claimed encoding is windows-1252. 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

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