4.3 sec in total
237 ms
3.5 sec
482 ms
Welcome to regence.com homepage info - get ready to check Regence best content for United States right away, or after learning these important things about regence.com
Regence health coverage opens doors to quality, local care paired with a national network powered by Blue®. Get medical insurance for your life and budget.
Visit regence.comWe analyzed Regence.com page load time and found that the first response time was 237 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
regence.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value5.0 s
26/100
25%
Value14.4 s
1/100
10%
Value4,650 ms
0/100
30%
Value0.211
59/100
15%
Value18.6 s
3/100
10%
237 ms
1138 ms
140 ms
175 ms
518 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 72% of them (62 requests) were addressed to the original Regence.com, 14% (12 requests) were made to Use.typekit.net and 2% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Regence.com.
Page size can be reduced by 2.9 MB (60%)
4.8 MB
1.9 MB
In fact, the total size of Regence.com main page is 4.8 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 210.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. This page needs HTML code to be minified as it can gain 38.2 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 210.3 kB or 86% of the original size.
Potential reduce by 20.2 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. Regence images are well optimized though.
Potential reduce by 1.7 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.7 MB or 76% of the original size.
Potential reduce by 926.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. Regence.com needs all CSS files to be minified and compressed as it can save up to 926.2 kB or 86% of the original size.
Number of requests can be reduced by 33 (48%)
69
36
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Regence. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
regence.com
237 ms
www.regence.com
1138 ms
main.css
140 ms
main.css
175 ms
barebone.jsp
518 ms
font-awesome.min.css
30 ms
vhs6hik.js
201 ms
bootstrap.css
316 ms
regence-legacy-sunflower.css
297 ms
regence-legacy-blessed1-sunflower.css
229 ms
regence-sunflower.css
380 ms
addthis_widget.js
48 ms
modernizr.js
291 ms
jquery.js
396 ms
jquery.scrollTo.min.js
354 ms
waypoints.js
360 ms
sunflower-theme.js
374 ms
webtrends.load.js
378 ms
plugins.js
698 ms
main.js
573 ms
regence-theme.js
399 ms
sign-in-portlet.css
417 ms
set-view-location.js
572 ms
sign-in-portlet.js
589 ms
main.js
454 ms
www.regence.com
50 ms
regence-legacy-blessed1-sunflower.css
285 ms
regence-sun-cs.svg
74 ms
regence-sun-s.svg
73 ms
lock.svg
71 ms
regence-cs.svg
76 ms
regence-s.svg
78 ms
regence_bcbs.png
70 ms
8d48bbe9-867c-4dd0-9a52-24984ad0f396
751 ms
67c424b0-c318-40ec-bada-dfe8c0e59f3d
752 ms
131979ce-45fa-459d-9a26-d29e28966818
305 ms
c78b55bd-0556-4861-a935-306cefafa6cb
248 ms
tumPsPlS4Iopq2_bR5K1r06cPhLW0zoHMStG6cDHgvMffFcUgsMZeMJ6Mk6f5Mw.woff
47 ms
hO7hIHFy5n0aNsklFakZJayMPLmg2LzC5fVYOptgzZCffFpUgsMZeMJ6Mk6f5Mb.woff
74 ms
-8ITIdDY3v55qYcFh7lrROCUXp25sBiBsJWBsH4r-VGffFAUgsMZeMJ6Mk6f5Mj.woff
95 ms
07X1gTYxvreQh-Wpb9QAfWXulc4bOJzDFvfeAicppGMffwrUgsMZeMJ6Mk6f5MS.woff
139 ms
sunflower-icon-set.ttf
117 ms
icomoon.svg
137 ms
icomoon.svg
225 ms
6992ca1a-35f5-4eeb-8f3e-69c526747c4f
226 ms
d5855715-8578-422d-8815-c6c5e62d81a7
237 ms
8bc192ae-9568-4110-8844-a04b57a55703
238 ms
dbc60dde-e832-4727-aaef-ef860a5df967
275 ms
83cd8c1e-4a22-431c-ad96-f5d1af52bd06
310 ms
49452ef5-2d7b-4d26-8714-eba0dd83c492
312 ms
119e53de-fb79-4e06-ba6d-2b42fa7c43dd
326 ms
58c97a53-6fac-461b-996f-57e811bab292
350 ms
4008d0ec-1ec1-4bf1-95b0-9137aeff605d
393 ms
623765ad-e49b-4f01-9da8-728dd75e0359
397 ms
623853fc-8057-4d0b-87c3-794ec4dd97f9
400 ms
0637de4b-9476-4145-bb7c-443fd774b4fe
418 ms
b6b81100-ba45-4fd5-b835-7ec05ff34e2c
465 ms
fadb2b3c-2081-4392-a077-66d33aeb42db
470 ms
8eda4825-b2c3-4309-af52-ebd185f46f3d
474 ms
49ea431d-5a67-41d5-9a71-a3a84c955026
488 ms
666cd2fc-3976-4adc-be86-6dbfbb31c616
695 ms
fontawesome-webfont.woff
15 ms
ActivityServer.bs
69 ms
ActivityServer.bs
19 ms
b00948cda98d0fb3
112 ms
webtrends.min.js
547 ms
314 ms
475 ms
icomoon.woff
475 ms
300lo.json
150 ms
0HlORLazyRC2V5UG3EihBmUjr3Snt5MIYUBGDhekt8tffFz6gsMZeMJ6Mk6f5MX.woff
109 ms
THk1A4-WXrjszFYEm3YNaQ0Wu-oyoMFW2hgWhaIX699ffFKUgsMZeMJ6Mk6f5Mt.woff
111 ms
6x5uM89ap_eoUjKtfHmWPe8hh6J2mFoP3YfOxug5vMvffF-UgsMZeMJ6Mk6f5gM.woff
109 ms
iMPrjI5NuOA9lYExznw9jrVpaTvmaVfNYIYG_XbUfk9ffFfUgsMZeMJ6Mk6f5gI.woff
109 ms
jLwUxBvqff--reKT-fydyGQX4deQysb_NbsMVTd0bAwffFnxMUMZeMJ6Mk6f5Mb.woff
110 ms
KjNQFVHhCPt8_UBnkQIVAaBw4Ypa4LZif3zF-OneP4JffFDxMUMZeMJ6Mk6f5Mj.woff
138 ms
sh.7c7179124ea24ac6ba46caac.html
103 ms
webtrends.plt.js
104 ms
webtrends.regence.js
104 ms
webtrends.id_receiver.js
103 ms
webtrends.utm.js
104 ms
webtrends.yt.js
132 ms
wtid.js
102 ms
icomoon.ttf
65 ms
p.gif
121 ms
dcs.gif
7 ms
regence.com accessibility score
regence.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
regence.com 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Regence.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Regence.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.
regence.com
Open Graph description is not detected on the main page of Regence. 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: