8.2 sec in total
117 ms
7.5 sec
567 ms
Welcome to prime.haysmed.com homepage info - get ready to check Prime Hays Med best content for United States right away, or after learning these important things about prime.haysmed.com
Visit prime.haysmed.comWe analyzed Prime.haysmed.com page load time and found that the first response time was 117 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
prime.haysmed.com performance score
117 ms
4210 ms
89 ms
131 ms
143 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Prime.haysmed.com, 43% (59 requests) were made to Haysmed.com and 12% (16 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Haysmed.com.
Page size can be reduced by 2.4 MB (59%)
4.0 MB
1.6 MB
In fact, the total size of Prime.haysmed.com main page is 4.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. CSS take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 99.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 99.3 kB or 81% of the original size.
Potential reduce by 99.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. Prime Hays Med images are well optimized though.
Potential reduce by 928.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 928.3 kB or 70% of the original size.
Potential reduce by 1.2 MB
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. Prime.haysmed.com needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 90% of the original size.
Number of requests can be reduced by 84 (63%)
133
49
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prime Hays Med. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
prime.haysmed.com
117 ms
www.haysmed.com
4210 ms
wp-emoji-release.min.js
89 ms
styles.css
131 ms
settings.css
143 ms
wpProQuiz_front.min.css
150 ms
tribe-events-full.css
146 ms
tribe-events-theme.css
148 ms
style.css
188 ms
shortcodes.css
175 ms
font-awesome.css
203 ms
animate.css
211 ms
prettyPhoto.css
206 ms
responsive.css
214 ms
datepicker.css
217 ms
css
69 ms
owl.carousel.css
229 ms
owl.theme.css
230 ms
flexslider.css
230 ms
js_composer_front_custom.css
365 ms
jetpack.css
247 ms
jquery.js
340 ms
jquery-migrate.min.js
267 ms
jquery.themepunch.tools.min.js
434 ms
jquery.themepunch.revolution.min.js
432 ms
jquery.form.min.js
291 ms
scripts.js
309 ms
qppr_frontend_script.min.js
336 ms
devicepx-jetpack.js
43 ms
core.min.js
356 ms
datepicker.min.js
431 ms
jquery.easing.1.3.js
428 ms
hoverIntent.js
429 ms
superfish.js
429 ms
jquery.preloadify.min.js
449 ms
jquery.prettyPhoto.js
448 ms
Modernizr.js
510 ms
isotope.js
510 ms
jquery.fitvids.js
511 ms
e-201611.js
42 ms
sys_custom.js
512 ms
wow.js
434 ms
jquery.countTo.js
395 ms
jquery.simpleWeather.min.js
482 ms
comment-reply.min.js
478 ms
jquery.flexslider-min.js
480 ms
theme-love.js
478 ms
wp-embed.min.js
449 ms
js_composer_front.min.js
425 ms
css
24 ms
analytics.js
101 ms
HMClogotrans2.png
195 ms
dummy.png
173 ms
image_gallery-300x92.jpg
176 ms
chi-icon2.png
175 ms
comm-support.png
174 ms
foundation-icon.png
194 ms
sdk.js
382 ms
collect
34 ms
fontawesome-webfont.woff
190 ms
embed
1094 ms
search-icon.png
52 ms
top_arrow.png
49 ms
tribe-events-full-mobile.css
87 ms
tribe-events-theme-mobile.css
724 ms
small_left.png
102 ms
small_right.png
102 ms
js
107 ms
init_embed.js
156 ms
276 ms
g.gif
162 ms
Slider1.jpg
757 ms
xd_arbiter.php
417 ms
page.php
423 ms
common.js
93 ms
map.js
92 ms
google4.png
154 ms
overlay.js
148 ms
util.js
145 ms
onion.js
142 ms
search_impl.js
143 ms
StaticMapService.GetMapImage
135 ms
stats.js
57 ms
openhand_8_8.cur
81 ms
kh
97 ms
transparent.png
44 ms
ViewportInfoService.GetViewportInfo
109 ms
ViewportInfoService.GetViewportInfo
105 ms
controls.js
27 ms
Z7dsddbCfhx.css
209 ms
Ksen2kZF4GW.css
254 ms
m3UplzJmRpp.css
366 ms
q68gy-v_YMF.js
442 ms
YvxwM8R7ol8.js
473 ms
ihptErjAmMX.js
468 ms
3So47A9WcrL.js
405 ms
cUsKAwzqrQw.js
498 ms
css
57 ms
entity11.png
51 ms
mapcnt6.png
55 ms
sv5.png
33 ms
tmapctrl.png
25 ms
vt
94 ms
vt
166 ms
vt
109 ms
vt
107 ms
vt
110 ms
vt
106 ms
vt
108 ms
vt
171 ms
vt
169 ms
vt
170 ms
AuthenticationService.Authenticate
21 ms
1604888_1007558085921288_7117606385540298953_n.jpg
188 ms
1456523_698462106830889_457001500_n.jpg
213 ms
1554485_1162698900407205_5591815772395405462_n.jpg
254 ms
1915453_1162699193740509_8931001415777393938_n.jpg
291 ms
10417647_1162699280407167_2918314101060734473_n.jpg
293 ms
1914254_1162699393740489_3830381409583510339_n.jpg
294 ms
995392_1160963780580717_7125968574101583734_n.jpg
293 ms
1377343_1160963827247379_3575994551738029470_n.jpg
296 ms
10432491_1160205287323233_6520063879446133433_n.jpg
294 ms
1914655_1160205387323223_4587296343582221358_n.jpg
332 ms
10264961_1160205533989875_4894623337370843989_n.jpg
333 ms
1176377_1160205680656527_4236370339871828373_n.jpg
333 ms
12801607_1156351897708572_9179730388583674457_n.jpg
336 ms
12794536_1156351954375233_4809174688460941002_n.jpg
340 ms
12803159_1156352017708560_8626325309791742763_n.jpg
336 ms
wL6VQj7Ab77.png
116 ms
s7jcwEQH7Sx.png
118 ms
GtIpNnEyqq_.png
117 ms
lRyN50VcaFW.js
42 ms
R9a_DtVRZgv.js
41 ms
cUDgRFxaoIk.js
44 ms
0JBr1QHp8Gi.js
43 ms
kDOzhTr2W91.js
46 ms
prime.haysmed.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prime.haysmed.com 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 Prime.haysmed.com 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.
prime.haysmed.com
Open Graph description is not detected on the main page of Prime Hays Med. 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: