8.5 sec in total
73 ms
8 sec
385 ms
Click here to check amazing Geoaccess content for United States. Otherwise, check out these important facts you probably never knew about geoaccess.com
Quest Analytics leverages better data, to help health plans build better networks, and create a better member experience.
Visit geoaccess.comWe analyzed Geoaccess.com page load time and found that the first response time was 73 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
geoaccess.com performance score
73 ms
126 ms
196 ms
320 ms
130 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Geoaccess.com, 88% (53 requests) were made to Optum.com and 8% (5 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Optum.com.
Page size can be reduced by 1.7 MB (57%)
2.9 MB
1.3 MB
In fact, the total size of Geoaccess.com main page is 2.9 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. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 118.1 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 38.4 kB, which is 29% 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 118.1 kB or 89% of the original size.
Potential reduce by 17.9 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. Geoaccess images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 71% of the original size.
Potential reduce by 263.9 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. Geoaccess.com needs all CSS files to be minified and compressed as it can save up to 263.9 kB or 82% of the original size.
Number of requests can be reduced by 38 (68%)
56
18
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geoaccess. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
geoaccess.com
73 ms
126 ms
www.optum.com
196 ms
www.optum.com
320 ms
clientlibs-global.min.css
130 ms
jquery-ui.min.css
176 ms
clientlibs.min.css
264 ms
jquery.min.js
357 ms
utils.min.js
344 ms
granite.min.js
343 ms
jquery.min.js
459 ms
jquery-ui.min.js
353 ms
jquery-ui.min.js
344 ms
clientlibs.underscore.min.js
347 ms
clientlibs.min.js
548 ms
elqCfg.js
350 ms
elqImg.js
404 ms
elqScr.js
404 ms
shared.min.js
402 ms
modern.min.js
401 ms
kernel.min.js
441 ms
js
158 ms
jwplayer.js
517 ms
token.json
127 ms
USA.png
68 ms
optum_2x.png
67 ms
disclaimerClose.png
65 ms
xprnt.png
65 ms
WF90327_FEB_Home-page-updates_MI_feature.jpg
66 ms
WF90327_FEB_Home-page-updates_AC_feature.jpg
66 ms
WF90327_FEB_Home-page-updates_EC_feature.jpg
99 ms
ICD10_Truman-banner_icd10_update.jpg
100 ms
WF87463_CHD_660x371.jpg
260 ms
arrow-square-left.png
95 ms
arrow-square-right.png
88 ms
blog-icon25x25.png
94 ms
header-top-background.png
41 ms
magnify-icon.png
63 ms
menu_black_down_arrow.png
58 ms
menu_white_right_arrow.png
57 ms
main-menu-background.png
43 ms
header-menu-gradient.png
145 ms
main-content-background.png
145 ms
left-arrow-orange.png
146 ms
right-arrow-orange.png
146 ms
Ribbon_Bottom_Border.png
134 ms
www.optum.com
111 ms
8112_HP_Modern_banner2.jpg
1058 ms
foresee-trigger.js
883 ms
fetchLandingNews
5103 ms
elqCfg.min.js
128 ms
8112_HP_Future_banner2.jpg
192 ms
8112_optum.com_HP_Healthier_banner.jpg
109 ms
top-gradient.png
107 ms
foresee-surveydef.js
43 ms
foresee-dhtml.css
46 ms
common.js
19 ms
util.js
36 ms
stats.js
47 ms
AuthenticationService.Authenticate
95 ms
geoaccess.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geoaccess.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 Geoaccess.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.
geoaccess.com
Open Graph description is not detected on the main page of Geoaccess. 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: