1.3 sec in total
43 ms
985 ms
304 ms
Click here to check amazing Mobile UChicago content for United States. Otherwise, check out these important facts you probably never knew about mobile.uchicago.edu
Visit mobile.uchicago.eduWe analyzed Mobile.uchicago.edu page load time and found that the first response time was 43 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
mobile.uchicago.edu performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value7.6 s
4/100
25%
Value7.3 s
30/100
10%
Value360 ms
73/100
30%
Value0.267
46/100
15%
Value6.8 s
55/100
10%
43 ms
179 ms
18 ms
23 ms
18 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 62% of them (23 requests) were addressed to the original Mobile.uchicago.edu, 11% (4 requests) were made to Google-analytics.com and 8% (3 requests) were made to Identity.uchicago.edu. The less responsive or slowest element that took the longest time to load (411 ms) relates to the external source Events.uchicago.edu.
Page size can be reduced by 909.3 kB (60%)
1.5 MB
607.7 kB
In fact, the total size of Mobile.uchicago.edu main page is 1.5 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. 60% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 107.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 107.0 kB or 76% of the original size.
Potential reduce by 17.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. Mobile UChicago images are well optimized though.
Potential reduce by 681.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 681.0 kB or 68% of the original size.
Potential reduce by 104.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. Mobile.uchicago.edu needs all CSS files to be minified and compressed as it can save up to 104.0 kB or 80% of the original size.
Number of requests can be reduced by 18 (53%)
34
16
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile UChicago. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
mobile.uchicago.edu
43 ms
proximanova.css
179 ms
css_kShW4RPmRstZ3SpIC-ZvVGNFVAi0WEMuCnI0ZkYIaFw.css
18 ms
css_JwGEzU0CJq6ht-c7fSbxyyQA0S989nB6CmEI_3xW7BA.css
23 ms
css_MnXiytJtb186Ydycnpwpw34cuUsHaKc80ey5LiQXhSY.css
18 ms
css_HIYQqosy_bI5BAlz9rR_AM6q1ojAYiuvXX7lafwxLS4.css
21 ms
css_VPjvQBFUP94DCFTTwix-ABCj_Ekb0IoCYyhN3-DrxAY.css
23 ms
modernizr.js
34 ms
list.php
411 ms
js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js
229 ms
js_KCd8rbJYUruV1tRJnh4um34UYvyhlrSVCPR1jNko2h8.js
230 ms
js_D4wZnDx7jxG6bbzXbCgtNJyKMxNktGWPQrevXWEPCuU.js
231 ms
addthis_widget.js
48 ms
js_NWbF2AfsCMV6EWT7Lfk3cigadXN9Tu-V9hlo3726pLs.js
36 ms
js_a_XWH2S1EQaU85ypMDyQGiUfzPFez1IOZKxHnhGkv3E.js
36 ms
js_VjoAdhZX6YJ-Qf2cZWdu-35UhFgs6CbbSNp7XyyhsmE.js
168 ms
mainfeature.js
44 ms
sprite_v2.svg
15 ms
uc_wordmark_hires.gif
11 ms
image_1%20%281%29.jpg
6 ms
HAND.png
63 ms
tribune%20feature.jpg
8 ms
ios_app.png
129 ms
play_store.png
129 ms
greybullet.svg
10 ms
1415F2_1.woff
78 ms
1415F2_3.woff
254 ms
ss-standard.woff
82 ms
css_ydBjF8-GsuajqUF3WYlVKd4MwMgWQCaHkgG_km0UnCQ.css
43 ms
ga.js
101 ms
300lo.json
99 ms
sh.8e5f85691f9aaa082472a194.html
105 ms
__utm.gif
69 ms
__utm.gif
47 ms
__utm.gif
48 ms
collect
127 ms
layers.e5ea973510bf60b3db41.js
20 ms
mobile.uchicago.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
Links do not have a discernible name
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.
mobile.uchicago.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
mobile.uchicago.edu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Mobile.uchicago.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 Mobile.uchicago.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.
mobile.uchicago.edu
Open Graph description is not detected on the main page of Mobile UChicago. 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: