627 ms in total
46 ms
297 ms
284 ms
Click here to check amazing Reunion Georgetown content for United States. Otherwise, check out these important facts you probably never knew about reunion.georgetown.edu
Join us May 31–June 2, 2024 for reunion!
Visit reunion.georgetown.eduWe analyzed Reunion.georgetown.edu page load time and found that the first response time was 46 ms and then it took 581 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
reunion.georgetown.edu performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value32.0 s
0/100
25%
Value9.3 s
13/100
10%
Value1,180 ms
21/100
30%
Value0.236
53/100
15%
Value14.6 s
8/100
10%
46 ms
17 ms
20 ms
111 ms
29 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 77% of them (27 requests) were addressed to the original Reunion.georgetown.edu, 11% (4 requests) were made to Google-analytics.com and 6% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (122 ms) belongs to the original domain Reunion.georgetown.edu.
Page size can be reduced by 70.3 kB (24%)
293.4 kB
223.1 kB
In fact, the total size of Reunion.georgetown.edu main page is 293.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. 30% of websites need less resources to load. Images take 210.3 kB which makes up the majority of the site volume.
Potential reduce by 10.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. This page needs HTML code to be minified as it can gain 5.1 kB, which is 39% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 10.2 kB or 79% of the original size.
Potential reduce by 14.8 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. Reunion Georgetown images are well optimized though.
Potential reduce by 33.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 33.3 kB or 60% of the original size.
Potential reduce by 12.1 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. Reunion.georgetown.edu needs all CSS files to be minified and compressed as it can save up to 12.1 kB or 82% of the original size.
Number of requests can be reduced by 4 (12%)
34
30
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reunion 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 5 to 1 for JavaScripts and as a result speed up the page load time.
reunion.georgetown.edu
46 ms
jsapi
17 ms
RW12.js
20 ms
reunion.css
111 ms
jquery.min.js
29 ms
banner_2016.jpg
61 ms
regbtn.png
15 ms
magbtn.png
34 ms
nav_whoscoming.gif
32 ms
nav_schedule.gif
32 ms
nav_details.gif
18 ms
nav_classes.gif
59 ms
nav_dentistry.gif
60 ms
nav_giving.gif
61 ms
btn_YT.gif
63 ms
btn_TW.gif
57 ms
btn_LI.gif
61 ms
btn_FB.gif
58 ms
btn_REG.gif
60 ms
RU-header.jpg
62 ms
RU-footer.jpg
122 ms
footer_2016.gif
61 ms
analytics.js
31 ms
BG-seal.gif
70 ms
BG-Main.png
31 ms
home-gates.jpg
48 ms
BG-content.png
49 ms
BG-nav.gif
29 ms
RU-BG.jpg
30 ms
bullet.gif
29 ms
linkid.js
15 ms
collect
31 ms
collect
69 ms
collect
25 ms
collect
71 ms
reunion.georgetown.edu accessibility score
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
ARIA IDs are not unique
reunion.georgetown.edu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
reunion.georgetown.edu SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reunion.georgetown.edu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Reunion.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.
reunion.georgetown.edu
Open Graph description is not detected on the main page of Reunion 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: