3 sec in total
111 ms
2.7 sec
177 ms
Click here to check amazing Healthyflorida content for United States. Otherwise, check out these important facts you probably never knew about healthyflorida.com
Florida Health Insurance. Instant quote, compare and apply for Cigna, AARP, Aetna, United, Humana, Blue Cross. (561) 214-4600 Help Line.
Visit healthyflorida.comWe analyzed Healthyflorida.com page load time and found that the first response time was 111 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
healthyflorida.com performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value7.4 s
4/100
25%
Value11.8 s
4/100
10%
Value1,470 ms
14/100
30%
Value0.161
73/100
15%
Value13.1 s
12/100
10%
111 ms
96 ms
82 ms
47 ms
50 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Healthyflorida.com, 37% (38 requests) were made to Static.parastorage.com and 23% (24 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 3.0 MB (65%)
4.6 MB
1.6 MB
In fact, the total size of Healthyflorida.com main page is 4.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 135.7 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 135.7 kB or 84% of the original size.
Potential reduce by 82.3 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. Healthyflorida images are well optimized though.
Potential reduce by 2.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 2.7 MB or 76% of the original size.
Potential reduce by 104.1 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. Healthyflorida.com needs all CSS files to be minified and compressed as it can save up to 104.1 kB or 85% of the original size.
Number of requests can be reduced by 62 (69%)
90
28
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Healthyflorida. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
healthyflorida.com
111 ms
www.healthyflorida.com
96 ms
bt
82 ms
require.min.js
47 ms
main-r.min.js
50 ms
viewer.css
46 ms
dynamicmodel
10 ms
38c128_6fb2988ff8a19d865487f0f1f5c9747b_1467.json.z
523 ms
38c128_78c38a2d4a454b1415a3ce14cf95c00e_1466.json.z
576 ms
ugc-viewer
92 ms
bt
92 ms
skins.min.js
150 ms
components.min.js
29 ms
utils.min.js
148 ms
core.min.js
62 ms
react-with-addons.min.js
85 ms
lodash.min.js
162 ms
TweenMax.min.js
85 ms
layout.min.js
146 ms
tpa.min.js
149 ms
fonts.min.js
148 ms
animations.min.js
147 ms
swfobject.min.js
146 ms
mousetrap.min.js
145 ms
tweenEngine.min.js
152 ms
DrawSVGPlugin.min.js
152 ms
react-dom.min.js
147 ms
ScrollToPlugin.min.js
149 ms
widgets.min.js
150 ms
experiment.js
151 ms
render.min.js
151 ms
wixappsCore.min.js
157 ms
wixappsClassics.min.js
418 ms
wixappsBuilder.min.js
153 ms
zepto.min.js
150 ms
color.min.js
153 ms
react-dom-server.min.js
103 ms
bt
75 ms
dc.js
614 ms
bt
598 ms
shadowbottom.png
245 ms
css
241 ms
latin.css
238 ms
twitter.html
252 ms
widget
257 ms
38c128_be52f677f596473f9ff197218a43a014.png
359 ms
38c128_317f386f2fd146f7a980d8707c0d5b0e.png
360 ms
38c128_21a997c569694df3bc86aceb6f7407d8.png
396 ms
38c128_87045470ddf345d1920ab7d5493652ff.png
435 ms
38c128_34099a984cf34c0fa51256d21b8947b1.png
502 ms
38c128_f9bd4318de5f475eadfff8439a830bc9.png
359 ms
38c128_6755424290014105a344cb552f0906cb.png
563 ms
38c128_b89bf5ab724040b0913539659bf10cbf.png
831 ms
38c128_a9d474690b09458ab61b085c280b2cd6.png
659 ms
38c128_c4d0ddb896de4eb39fb775cf76a555c1.png
583 ms
38c128_7ba0dc3948664dd38197c215de27d8b7.png
727 ms
38c128_c26b0942f4114650bc7eede883ff51cd.png
617 ms
38c128_276da7b915be4e85a0e9893bc70bd961.png
964 ms
38c128_ca2e35950fc44784860e2be2f5b36315.png
796 ms
38c128_3ffeb18714fe4e9d9c7cc522d141a8de.png
971 ms
38c128_c0331527e0244718854a517af4afe038.png
963 ms
38c128_dad2384c24b6402599466b8b9594dcc9.png
909 ms
38c128_43c6fad254684b7287a63fe31945f2d6.png
1157 ms
38c128_a60c3f5280984139b88cb671a58b0230.png
1063 ms
38c128_3d1f12f8c09a4864a708785d4e5e8920.png
1160 ms
38c128_d50ebfaea0f040829daf15d76d6adbbb.png
1146 ms
38c128_f64a9956f9924fc7b7ab492b49ec0230.png
1224 ms
bt
117 ms
bt
117 ms
bt
302 ms
bg_fbshare.png
120 ms
facebooklogo.png
117 ms
__utm.gif
84 ms
Wix.js
240 ms
css
52 ms
widgets.css
52 ms
widget.js
284 ms
tweet_button.html
321 ms
bc176270-17fa-4c78-a343-9fe52824e501.woff
185 ms
kYZt1bJ8UsGAPRGnkXPeFZ0EAVxt0G0biEntp43Qt6E.ttf
164 ms
c5749443-93da-4592-b794-42f28d62ef72.woff
160 ms
ugc-viewer
100 ms
ga.js
71 ms
jot
135 ms
__utm.gif
41 ms
__utm.gif
64 ms
__utm.gif
65 ms
__utm.gif
65 ms
__utm.gif
64 ms
__utm.gif
66 ms
livesite.js
87 ms
__utm.gif
39 ms
livesite.css
27 ms
css
15 ms
configuration
43 ms
normal_opc9l23vwxhutqif3fk28kebcgrso6vj.jpg
236 ms
active_engage_gate
39 ms
i
49 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
31 ms
opensans-regular-webfont.woff
59 ms
opensans-bold-webfont.woff
66 ms
icomoon.woff
66 ms
active_engage_gate
113 ms
healthyflorida.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
healthyflorida.com 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
Page has valid source maps
healthyflorida.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Healthyflorida.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 Healthyflorida.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.
healthyflorida.com
Open Graph data is detected on the main page of Healthyflorida. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: