2.6 sec in total
391 ms
1.5 sec
630 ms
Click here to check amazing Map S Georgetown content for United States. Otherwise, check out these important facts you probably never knew about maps.georgetown.edu
The Georgetown University Campus Maps shows the locations of university buildings on Georgetown’s main campus, medical center, law center and downtown Washington locations. The campus map also highlig...
Visit maps.georgetown.eduWe analyzed Maps.georgetown.edu page load time and found that the first response time was 391 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster. This domain responded with an error, which can significantly jeopardize Maps.georgetown.edu rating and web reputation
maps.georgetown.edu performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.006
100/100
15%
Value0
0/100
10%
391 ms
58 ms
27 ms
45 ms
34 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 8% of them (8 requests) were addressed to the original Maps.georgetown.edu, 18% (18 requests) were made to Maps.googleapis.com and 14% (14 requests) were made to Gucms-ui.georgetown.edu. The less responsive or slowest element that took the longest time to load (391 ms) belongs to the original domain Maps.georgetown.edu.
Page size can be reduced by 765.3 kB (38%)
2.0 MB
1.3 MB
In fact, the total size of Maps.georgetown.edu main page is 2.0 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. 70% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 56.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 56.7 kB or 81% of the original size.
Potential reduce by 109.6 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. Obviously, Map S Georgetown needs image optimization as it can save up to 109.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 475.0 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 475.0 kB or 62% of the original size.
Potential reduce by 124.0 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. Maps.georgetown.edu needs all CSS files to be minified and compressed as it can save up to 124.0 kB or 82% of the original size.
Number of requests can be reduced by 34 (37%)
91
57
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Map S 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 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
maps.georgetown.edu
391 ms
zat8mnd.js
58 ms
global.base.css
27 ms
global.styles.css
45 ms
tt-styles.css
34 ms
templates.css
30 ms
jquery.js
51 ms
plugins.js
34 ms
media_queries.js
33 ms
tt-scripts.js
36 ms
map.css
8 ms
js
24 ms
jquery.min.js
28 ms
jquery.autocomplete.min.js
14 ms
gumap.js
20 ms
ff
94 ms
np-georgetown.png
185 ms
bg-seal.png
182 ms
analytics.js
149 ms
settings
115 ms
loading.gif
121 ms
btn-submit-bg.gif
119 ms
seal.png
121 ms
np-university.png
115 ms
icon-search.png
116 ms
icon-menu.png
114 ms
btn-search-icon.png
114 ms
facebook.png
115 ms
instagram.png
116 ms
twitter.png
116 ms
linkedin.png
116 ms
youtube.png
117 ms
servicetypes
40 ms
campusmaps
42 ms
aggregated
100 ms
p.gif
56 ms
GjKIy-3ZgdeZSD1Kott0Qjpa25yg_HKYhUf5MYQcEm3ffFPgggM9eMI6MK6f5Mb.eot
254 ms
j4b0KRoLCw9N_MBym1vGIXCITO1N8M0eEJR7bWC8VtIffw7gggM9eMI6MK6f5Mb.eot
254 ms
8ePo6ZC8CrWEpqAq0diLapCCk7jAvBodVZoTAdCvOj3ff5L-ggM9eMI6MK6f5Mt.eot
254 ms
40xALwZW0SgN66ZnwCaRuisdv3_F9cPopp_y1mXhDLCff5d-ggM9eMI6MK6f5gI.eot
253 ms
2IXjGE4Hr4Pjc5OGFXsYFqn8oNnUqwpPIHmGp9QxPjjff5R-ggM9eMI6MK6f5Mb.eot
254 ms
CwxlecAmKDtJouPhvCsTAxZML1gC-odS1En5xXfijOMff5W-ggM9eMI6MK6f5MS.eot
254 ms
K7CahI3_6m4ziTyGUpdzIHnzNRHNneSf6BXhxDvjtdSffw0gggM9eMI6MK6f5Mt.eot
254 ms
InZmb4t07Lzywvsto--LCsRRBsbUP-4SEaJdHsqpd_vffFAgggM9eMI6MK6f5Mt.eot
253 ms
collect
16 ms
collect
61 ms
collect
11 ms
collect
232 ms
common.js
64 ms
map.js
64 ms
util.js
55 ms
marker.js
54 ms
4680198840_1d601b5027_m.jpg
142 ms
6283222722_1b83da0252.jpg
211 ms
4774980994_18dda660c5_m.jpg
130 ms
15478555832_be11524a1f_m.jpg
205 ms
9199231077_8b84454682_m_d.jpg
152 ms
staticmap
115 ms
4724703738_800ab3855b_m.jpg
119 ms
4728309538_690630f0e9_m.jpg
113 ms
5099486849_a955c1769e_m.jpg
116 ms
4682458594_8bd026dd01_m.jpg
114 ms
4774183777_01c9f0d8dd_m.jpg
116 ms
4774692677_2841ddf1ee_m.jpg
143 ms
4748757761_0d49b3ca44_m_d.jpg
139 ms
4774934836_4ed4f38ab5_m.jpg
116 ms
4386021483_7c33bf385b_m.jpg
142 ms
4775552122_5d54e9bbe9_m.jpg
137 ms
4793861086_4e1725fe7b_m.jpg
140 ms
4777856890_88e7ec28ee_m.jpg
140 ms
4777246893_68ed49e236_m.jpg
188 ms
4388959666_468c002793_m.jpg
187 ms
4774705834_9a9435568f_m.jpg
184 ms
4767425169_8c9010b9d4_m.jpg
185 ms
printer.png
22 ms
chain_plus.png
89 ms
onion.js
64 ms
openhand_8_8.cur
90 ms
stats.js
57 ms
controls.js
53 ms
ViewportInfoService.GetViewportInfo
98 ms
blue-dot.png
63 ms
transparent.png
43 ms
css
67 ms
google4.png
46 ms
mapcnt6.png
45 ms
sv5.png
44 ms
tmapctrl.png
19 ms
cb_scout5.png
20 ms
tmapctrl4.png
20 ms
imgs8.png
18 ms
vt
14 ms
vt
13 ms
vt
12 ms
vt
16 ms
vt
17 ms
vt
19 ms
vt
20 ms
vt
21 ms
vt
32 ms
AuthenticationService.Authenticate
26 ms
maps.georgetown.edu accessibility score
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
<frame> or <iframe> elements do not have a title
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
maps.georgetown.edu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
maps.georgetown.edu SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Maps.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 Maps.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.
maps.georgetown.edu
Open Graph description is not detected on the main page of Map S 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: