2.5 sec in total
243 ms
1.8 sec
452 ms
Welcome to hub.uhg.com homepage info - get ready to check Hub Uhg best content for United States right away, or after learning these important things about hub.uhg.com
Visit hub.uhg.comWe analyzed Hub.uhg.com page load time and found that the first response time was 243 ms and then it took 2.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.
hub.uhg.com performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value12.7 s
0/100
25%
Value7.7 s
25/100
10%
Value2,600 ms
4/100
30%
Value0.47
18/100
15%
Value19.3 s
2/100
10%
243 ms
70 ms
61 ms
53 ms
393 ms
Our browser made a total of 9 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Hub.uhg.com, 44% (4 requests) were made to Hub.unitedhealthgroup.com. The less responsive or slowest element that took the longest time to load (393 ms) relates to the external source Authgateway3.entiam.uhg.com.
Page size can be reduced by 121.3 kB (83%)
145.4 kB
24.1 kB
In fact, the total size of Hub.uhg.com main page is 145.4 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. Only 5% of websites need less resources to load. CSS take 131.8 kB which makes up the majority of the site volume.
Potential reduce by 11.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. 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 11.1 kB or 81% of the original size.
Potential reduce by 110.2 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. Hub.uhg.com needs all CSS files to be minified and compressed as it can save up to 110.2 kB or 84% of the original size.
We found no issues to fix!
4
4
The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hub Uhg. According to our analytics all requests are already optimized.
hub.unitedhealthgroup.com
243 ms
Authenticate.aspx
70 ms
default.aspx
61 ms
default.aspx
53 ms
prp.wsf
393 ms
bootstrap.min.css
205 ms
common.css
196 ms
UHG_Header_Logo.png
185 ms
central_line.png
37 ms
hub.uhg.com accessibility score
hub.uhg.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
hub.uhg.com SEO score
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 Hub.uhg.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 Hub.uhg.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.
hub.uhg.com
Open Graph description is not detected on the main page of Hub Uhg. 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: