Tools & Wizards About Us
registrar.georgetown.edu screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

registrar.georgetown.edu

University Registrar | Georgetown University

Page Load Speed

944 ms in total

First Response

39 ms

Resources Loaded

686 ms

Page Rendered

219 ms

registrar.georgetown.edu screenshot

About Website

Welcome to registrar.georgetown.edu homepage info - get ready to check Registrar Georgetown best content for United States right away, or after learning these important things about registrar.georgetown.edu

Visit registrar.georgetown.edu

Key Findings

We analyzed Registrar.georgetown.edu page load time and found that the first response time was 39 ms and then it took 905 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

registrar.georgetown.edu performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.077

95/100

15%

TTI (Time to Interactive)

Value10.0 s

27/100

10%

Network Requests Diagram

registrar.georgetown.edu

39 ms

zat8mnd.js

58 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

6 ms

css_QnDqumlAmBiA-LkPKOOEj-wMlRQlYuHQdMmPGFs03GQ.css

7 ms

css_CR2SCSlcchF_V1JZKALtD7MrcD2v0JPHdUDwNYGkQWk.css

11 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 65% of them (34 requests) were addressed to the original Registrar.georgetown.edu, 6% (3 requests) were made to S7.addthis.com and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (271 ms) relates to the external source Cdn.syndication.twimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 908.7 kB (49%)

Content Size

1.8 MB

After Optimization

928.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Registrar.georgetown.edu main page is 1.8 MB. 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. Javascripts take 899.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 144.9 kB

  • Original 184.0 kB
  • After minification 182.0 kB
  • After compression 39.1 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 144.9 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 18.7 kB

  • Original 600.1 kB
  • After minification 581.3 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. Registrar Georgetown images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 626.7 kB

  • Original 899.9 kB
  • After minification 845.8 kB
  • After compression 273.1 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 626.7 kB or 70% of the original size.

CSS Optimization

-77%

Potential reduce by 118.3 kB

  • Original 153.0 kB
  • After minification 149.7 kB
  • After compression 34.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. Registrar.georgetown.edu needs all CSS files to be minified and compressed as it can save up to 118.3 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (61%)

Requests Now

51

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

registrar.georgetown.edu

registrar.georgetown.edu

39 ms

zat8mnd.js

zat8mnd.js

58 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

6 ms

css_QnDqumlAmBiA-LkPKOOEj-wMlRQlYuHQdMmPGFs03GQ.css

css_QnDqumlAmBiA-LkPKOOEj-wMlRQlYuHQdMmPGFs03GQ.css

7 ms

css_CR2SCSlcchF_V1JZKALtD7MrcD2v0JPHdUDwNYGkQWk.css

css_CR2SCSlcchF_V1JZKALtD7MrcD2v0JPHdUDwNYGkQWk.css

11 ms

css_l8ruAHA1RrFR5V9DmJseqG1J-CcYwbPDmmmG5sAkZxw.css

css_l8ruAHA1RrFR5V9DmJseqG1J-CcYwbPDmmmG5sAkZxw.css

11 ms

css_TaCYXDEC4Uk0hFU6iy3La8w3tMfI4PG75gB9EskoaNg.css

css_TaCYXDEC4Uk0hFU6iy3La8w3tMfI4PG75gB9EskoaNg.css

7 ms

css_yBcF55a8yQlnLRPc9SYxmdF6cNsE9arBx6LvBfYX7ug.css

css_yBcF55a8yQlnLRPc9SYxmdF6cNsE9arBx6LvBfYX7ug.css

6 ms

js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js

js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js

10 ms

js_c0Yvn9PtgS46AYQuwj6SeS1n2-8CwVqZNbennwm6M1s.js

js_c0Yvn9PtgS46AYQuwj6SeS1n2-8CwVqZNbennwm6M1s.js

10 ms

js_i3Jx3j8QJVHmJx496Ngv6fw959FFodX_8RoG2l8umgQ.js

js_i3Jx3j8QJVHmJx496Ngv6fw959FFodX_8RoG2l8umgQ.js

11 ms

addthis_widget.js

addthis_widget.js

20 ms

js_xi-qXcOZ47XnziC9svdUuqbOFt6VJ6WY4h_01SAoQWU.js

js_xi-qXcOZ47XnziC9svdUuqbOFt6VJ6WY4h_01SAoQWU.js

11 ms

js_I8yX6RYPZb7AtMcDUA3QKDZqVkvEn35ED11_1i7vVpc.js

js_I8yX6RYPZb7AtMcDUA3QKDZqVkvEn35ED11_1i7vVpc.js

14 ms

js_HM7CscRes39aCvF5AHwUZ46I94E0fSXzowNU1CeP_ns.js

js_HM7CscRes39aCvF5AHwUZ46I94E0fSXzowNU1CeP_ns.js

13 ms

js_D6qddL5lJeuOXg0C5KbxMhKYHOOCzzB46Y0wtZ2-n2w.js

js_D6qddL5lJeuOXg0C5KbxMhKYHOOCzzB46Y0wtZ2-n2w.js

13 ms

js_VAZLwX1iIAWoG9Gx_0oJ8PqvfIg3Qbp4gW4m64yut1w.js

js_VAZLwX1iIAWoG9Gx_0oJ8PqvfIg3Qbp4gW4m64yut1w.js

12 ms

analytics.js

analytics.js

74 ms

sdk.js

sdk.js

67 ms

widgets.js

widgets.js

65 ms

300lo.json

300lo.json

80 ms

np-georgetown.png

np-georgetown.png

59 ms

np-university.png

np-university.png

77 ms

btn-search-icon.png

btn-search-icon.png

6 ms

bg-content.jpg

bg-content.jpg

59 ms

bg-shadow.png

bg-shadow.png

58 ms

JQP_commencement_0.jpg

JQP_commencement_0.jpg

78 ms

law_center_0.jpg

law_center_0.jpg

76 ms

med_center.jpg

med_center.jpg

80 ms

marker-list.gif

marker-list.gif

80 ms

TrendingJack.jpg

TrendingJack.jpg

79 ms

trendingarrowsmall_0.jpg

trendingarrowsmall_0.jpg

120 ms

twitter100.png

twitter100.png

80 ms

facebook100.png

facebook100.png

78 ms

bg-healy.png

bg-healy.png

229 ms

bg-dossier-seal.jpg

bg-dossier-seal.jpg

81 ms

icon-social.png

icon-social.png

116 ms

btn-arrow.gif

btn-arrow.gif

80 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

79 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

74 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

100 ms

collect

collect

72 ms

collect

collect

213 ms

collect

collect

97 ms

collect

collect

231 ms

223 ms

xd_arbiter.php

xd_arbiter.php

117 ms

xd_arbiter.php

xd_arbiter.php

145 ms

layers.e5ea973510bf60b3db41.js

layers.e5ea973510bf60b3db41.js

26 ms

syndication

syndication

182 ms

387997653633486849

387997653633486849

271 ms

css_xtcR-lbTi1Ocoz-L5TvqyMrfy3RW2JFpskYXotkhRsA.css

css_xtcR-lbTi1Ocoz-L5TvqyMrfy3RW2JFpskYXotkhRsA.css

21 ms

Accessibility Review

registrar.georgetown.edu accessibility score

97

Accessibility Issues

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

registrar.georgetown.edu 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

SEO Factors

registrar.georgetown.edu SEO score

83

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 Registrar.georgetown.edu 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 Registrar.georgetown.edu 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

registrar.georgetown.edu

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