3.5 sec in total
1.4 sec
1.9 sec
164 ms
Visit publichealth.uams.edu now to see the best up-to-date Public Health UAMS content for United States and also check out these interesting facts you probably never knew about publichealth.uams.edu
UAMS
Visit publichealth.uams.eduWe analyzed Publichealth.uams.edu page load time and found that the first response time was 1.4 sec and then it took 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.
publichealth.uams.edu performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value12.9 s
0/100
25%
Value10.6 s
7/100
10%
Value1,790 ms
10/100
30%
Value0.191
64/100
15%
Value20.7 s
2/100
10%
1429 ms
87 ms
86 ms
184 ms
81 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 70% of them (35 requests) were addressed to the original Publichealth.uams.edu, 10% (5 requests) were made to Dev.nursing.uamsonline.com and 6% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Publichealth.uams.edu.
Page size can be reduced by 304.7 kB (39%)
786.7 kB
482.0 kB
In fact, the total size of Publichealth.uams.edu main page is 786.7 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. 45% of websites need less resources to load. Images take 384.1 kB which makes up the majority of the site volume.
Potential reduce by 29.3 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 29.3 kB or 77% of the original size.
Potential reduce by 20.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. Public Health UAMS images are well optimized though.
Potential reduce by 152.2 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 152.2 kB or 63% of the original size.
Potential reduce by 102.5 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. Publichealth.uams.edu needs all CSS files to be minified and compressed as it can save up to 102.5 kB or 83% of the original size.
Number of requests can be reduced by 23 (52%)
44
21
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Public Health UAMS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
publichealth.uams.edu
1429 ms
style.css
87 ms
style.css
86 ms
jquery.js
184 ms
jquery-migrate.min.js
81 ms
modernizr.js
118 ms
domready.js
81 ms
selectnav.min.js
119 ms
general.js
118 ms
new.jquery.nivo.slider.pack.js
128 ms
plugin.css
125 ms
datatables.css
156 ms
css
27 ms
brand
14 ms
brand
22 ms
royalslider.css
79 ms
rs-default-inverted.css
82 ms
big-slider.css
125 ms
jquery.royalslider.min.js
156 ms
box-shortcodes.css
125 ms
font-awesome.min.css
5 ms
content-shortcodes.css
131 ms
other-shortcodes.css
134 ms
wp-embed.min.js
216 ms
wp-emoji-release.min.js
230 ms
easy-table.css
96 ms
ga.js
109 ms
body_bckgrnd.png
199 ms
topper_bckgrnd.png
87 ms
network_icon.png
85 ms
uams-logo_180x67.png
86 ms
Dec-2015-cover.jpg
203 ms
Dec-2015-cover-220x220.jpg
87 ms
Elders-exhibit-with-her-son.jpg
203 ms
Elders-exhibit-with-her-son-220x220.jpg
199 ms
Sep-2015-Cover1.jpg
226 ms
Sep-2015-Cover1-220x220.jpg
199 ms
COPH-Alumni-Luncheon-Cover21.jpg
222 ms
COPH-Alumni-Luncheon-Cover21-220x220.jpg
202 ms
ulbullet.png
201 ms
facebook-220x220.jpg
204 ms
linkedin.jpg
234 ms
Youtube.jpg
220 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
78 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
79 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
80 ms
preloader.gif
142 ms
rs-default-inverted.png
121 ms
fontawesome-webfont.woff
106 ms
__utm.gif
69 ms
publichealth.uams.edu accessibility score
publichealth.uams.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
Missing source maps for large first-party JavaScript
publichealth.uams.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
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 Publichealth.uams.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 Publichealth.uams.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.
publichealth.uams.edu
Open Graph description is not detected on the main page of Public Health UAMS. 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: