1.4 sec in total
113 ms
765 ms
559 ms
Welcome to postdoc.case.edu homepage info - get ready to check Postdoc Case best content for United States right away, or after learning these important things about postdoc.case.edu
Visit postdoc.case.eduWe analyzed Postdoc.case.edu page load time and found that the first response time was 113 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 30% of websites can load faster.
postdoc.case.edu performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value16.0 s
0/100
25%
Value6.7 s
37/100
10%
Value1,000 ms
27/100
30%
Value0
100/100
15%
Value14.3 s
9/100
10%
113 ms
62 ms
123 ms
21 ms
30 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Postdoc.case.edu, 81% (92 requests) were made to Case.edu and 13% (15 requests) were made to Dudbm6bcnmy8e.cloudfront.net. The less responsive or slowest element that took the longest time to load (213 ms) relates to the external source Webapps.case.edu.
Page size can be reduced by 160.6 kB (11%)
1.5 MB
1.3 MB
In fact, the total size of Postdoc.case.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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 59.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. This page needs HTML code to be minified as it can gain 11.5 kB, which is 16% 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 59.7 kB or 85% of the original size.
Potential reduce by 2.5 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. Postdoc Case images are well optimized though.
Potential reduce by 70.4 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 70.4 kB or 34% of the original size.
Potential reduce by 28.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. Postdoc.case.edu needs all CSS files to be minified and compressed as it can save up to 28.1 kB or 28% of the original size.
Number of requests can be reduced by 89 (87%)
102
13
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Postdoc Case. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
postdoc.case.edu
113 ms
62 ms
gtm.js
123 ms
slick.css
21 ms
node.module.css
30 ms
entity-form.css
22 ms
slick.module.css
29 ms
align.module.css
29 ms
fieldgroup.module.css
32 ms
container-inline.module.css
30 ms
clearfix.module.css
31 ms
details.module.css
36 ms
hidden.module.css
39 ms
item-list.module.css
38 ms
js.module.css
36 ms
nowrap.module.css
42 ms
position-container.module.css
44 ms
progress.module.css
49 ms
reset-appearance.module.css
45 ms
resize.module.css
46 ms
sticky-header.module.css
45 ms
system-status-counter.css
51 ms
system-status-report-counters.css
58 ms
system-status-report-general-info.css
53 ms
tablesort.module.css
54 ms
tree-child.module.css
55 ms
views.module.css
106 ms
blazy.css
58 ms
blazy.loading.css
62 ms
gin-custom.css
62 ms
paragraphs.unpublished.css
64 ms
style.css
79 ms
jsonp.pl
213 ms
jquery-2.2.4.min.js
26 ms
globalize.min.js
159 ms
jquery.gcal_flow.js
160 ms
blazy.polyfill.min.js
104 ms
jquery.min.js
71 ms
underscore-min.js
105 ms
blazy.classlist.min.js
108 ms
blazy.promise.min.js
103 ms
blazy.raf.min.js
91 ms
once.min.js
144 ms
drupalSettingsLoader.js
138 ms
drupal.js
138 ms
drupal.init.js
140 ms
debounce.js
150 ms
dblazy.min.js
148 ms
blazy.once.min.js
145 ms
blazy.sanitizer.min.js
160 ms
blazy.dom.min.js
141 ms
blazy.base.min.js
139 ms
blazy.dataset.min.js
147 ms
blazy.viewport.min.js
146 ms
blazy.xlazy.min.js
142 ms
blazy.observer.min.js
142 ms
blazy.loading.min.js
145 ms
blazy.webp.min.js
147 ms
blazy.min.js
146 ms
bio.min.js
145 ms
slick.min.js
142 ms
bio.media.min.js
145 ms
blazy.drupal.min.js
146 ms
blazy.load.min.js
143 ms
overrides.js
145 ms
app.js
141 ms
affix.js
144 ms
alert.js
143 ms
button.js
134 ms
arizona-sans.css
79 ms
arizona-text.css
82 ms
font-awesome.min.css
79 ms
carousel.js
104 ms
collapse.js
109 ms
dropdown.js
194 ms
modal.js
194 ms
tooltip.js
195 ms
popover.js
193 ms
scrollspy.js
193 ms
tab.js
143 ms
transition.js
143 ms
drupal.bootstrap.js
144 ms
attributes.js
145 ms
theme.js
142 ms
popover.js
144 ms
cwru_logo_primary_black_print.jpeg
7 ms
cwru_logo_primary_white.svg
4 ms
cwru_acronym_blue.svg
9 ms
pin-icon.svg
10 ms
tooltip.js
134 ms
entity-form.js
135 ms
form.js
135 ms
form.js
149 ms
vertical-tabs.js
135 ms
slick.load.min.js
129 ms
datalayer.js
126 ms
Tomlinson-banner.png
212 ms
Prospective%20Post-docs.jpg
124 ms
Current%20Post%20Docs.jpg
123 ms
Adminand%20Mentors.jpg
121 ms
professional-development_2.jpg
120 ms
Medical%20stock%20image_0.jpg
131 ms
366674588_6803929112971381_8781560233899161013_n.jpg
132 ms
ABCArizonaSans-BoldItalic.woff
77 ms
ABCArizonaSans-MediumItalic.woff
77 ms
ABCArizonaSans-RegularItalic.woff
78 ms
ABCArizonaSans-Bold.woff
77 ms
ABCArizonaSans-Medium.woff
77 ms
ABCArizonaSans-Regular.woff
78 ms
ABCArizonaText-Regular.woff
15 ms
ABCArizonaText-Medium.woff
133 ms
ABCArizonaText-Bold.woff
118 ms
fontawesome-webfont.woff
86 ms
events
182 ms
postdoc.case.edu accessibility score
postdoc.case.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
postdoc.case.edu SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Postdoc.case.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 Postdoc.case.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.
postdoc.case.edu
Open Graph description is not detected on the main page of Postdoc Case. 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: