Tools & Wizards About Us
gds.org screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

gds.org

Home - Georgetown Day School

Page Load Speed

2.4 sec in total

First Response

43 ms

Resources Loaded

1.6 sec

Page Rendered

765 ms

gds.org screenshot

About Website

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

Home - Georgetown Day School

Visit gds.org

Key Findings

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

Performance Metrics

gds.org performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value19.2 s

0/100

10%

TBT (Total Blocking Time)

Value2,060 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

gds.org

43 ms

www.gds.org

75 ms

gtm.js

72 ms

application-bce5d22b68b57b3828b229556241a394e69dd8de5abfa2a018868e63ffc6d9cc.css

119 ms

styles.cfm

108 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 42% of them (14 requests) were addressed to the original Gds.org, 27% (9 requests) were made to Use.typekit.net and 12% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Gds.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 93.8 kB (10%)

Content Size

908.4 kB

After Optimization

814.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Gds.org main page is 908.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 684.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 90.5 kB

  • Original 106.6 kB
  • After minification 104.4 kB
  • After compression 16.2 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 90.5 kB or 85% of the original size.

JavaScript Optimization

-0%

Potential reduce by 43 B

  • Original 684.6 kB
  • After minification 684.6 kB
  • After compression 684.5 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.

CSS Optimization

-3%

Potential reduce by 3.2 kB

  • Original 117.2 kB
  • After minification 117.2 kB
  • After compression 113.9 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. Gds.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (71%)

Requests Now

17

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gds.org

gds.org

43 ms

www.gds.org

www.gds.org

75 ms

gtm.js

gtm.js

72 ms

application-bce5d22b68b57b3828b229556241a394e69dd8de5abfa2a018868e63ffc6d9cc.css

application-bce5d22b68b57b3828b229556241a394e69dd8de5abfa2a018868e63ffc6d9cc.css

119 ms

styles.cfm

styles.cfm

108 ms

main.css

main.css

91 ms

support.custom.css

support.custom.css

53 ms

in_layout_head-602a1b82d3fe83f66c01d9e7a465a9fc9d4ad042fab4987ea66c36ca3703cbf3.js

in_layout_head-602a1b82d3fe83f66c01d9e7a465a9fc9d4ad042fab4987ea66c36ca3703cbf3.js

157 ms

weglot.min.js

weglot.min.js

49 ms

application-42194fbb516fec6dbbdbb41700528b8c55c333d3f19ba7521aafc67c645fde5e.js

application-42194fbb516fec6dbbdbb41700528b8c55c333d3f19ba7521aafc67c645fde5e.js

244 ms

main.js

main.js

105 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

103 ms

background-pattern-2.svg

background-pattern-2.svg

160 ms

poweredby-7fe9cdfc8db6c2419477639e585e15f5fceee483b4a26452877dabab357cb391.svg

poweredby-7fe9cdfc8db6c2419477639e585e15f5fceee483b4a26452877dabab357cb391.svg

162 ms

webfontloader.js

webfontloader.js

116 ms

undefined

undefined

1071 ms

icomoon.woff

icomoon.woff

39 ms

main.js

main.js

26 ms

skb7ggd.js

skb7ggd.js

170 ms

css

css

41 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

28 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

53 ms

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNi83AHjabf.ttf

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNi83AHjabf.ttf

164 ms

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiSncHjabf.ttf

XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiSncHjabf.ttf

164 ms

d

d

65 ms

d

d

79 ms

d

d

79 ms

d

d

81 ms

d

d

111 ms

d

d

111 ms

d

d

79 ms

d

d

79 ms

p.gif

p.gif

136 ms

Accessibility Review

gds.org accessibility score

76

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-*] attributes do not have valid values

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

gds.org best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

gds.org SEO score

83

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

    UTF-8

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

gds.org

Open Graph data is detected on the main page of Gds. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: