3.8 sec in total
205 ms
2.5 sec
1.1 sec
Click here to check amazing Wellfra content. Otherwise, check out these important facts you probably never knew about wellfra.me
Wellframe partners with health plans to provide digital health solutions for Digital Care Management, Clinical Advocacy, and Member Advocacy.
Visit wellfra.meWe analyzed Wellfra.me page load time and found that the first response time was 205 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
wellfra.me performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value4.6 s
35/100
25%
Value6.0 s
46/100
10%
Value3,380 ms
2/100
30%
Value0.639
9/100
15%
Value14.3 s
9/100
10%
205 ms
461 ms
138 ms
200 ms
267 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wellfra.me, 54% (51 requests) were made to Wellframe.com and 20% (19 requests) were made to Code.cdn.mozilla.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Wellframe.com.
Page size can be reduced by 1.2 MB (32%)
3.7 MB
2.5 MB
In fact, the total size of Wellfra.me main page is 3.7 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. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 18.5 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 4.9 kB, which is 20% 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 18.5 kB or 78% of the original size.
Potential reduce by 505.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. Obviously, Wellfra needs image optimization as it can save up to 505.2 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 332.0 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 332.0 kB or 69% of the original size.
Potential reduce by 305.8 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. Wellfra.me needs all CSS files to be minified and compressed as it can save up to 305.8 kB or 87% of the original size.
Number of requests can be reduced by 34 (49%)
70
36
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wellfra. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
wellfra.me
205 ms
www.wellframe.com
461 ms
bootstrap.min.css
138 ms
fonts.css
200 ms
default.css
267 ms
fira.css
68 ms
css
35 ms
styles.css
208 ms
styles.css
200 ms
styles.css
202 ms
styles.css
200 ms
styles.css
268 ms
css
72 ms
jquery.js
63 ms
bootstrap.min.js
291 ms
modernizr.custom.js
291 ms
jquery.visible.js
300 ms
jquery.tap.min.js
300 ms
wellframe.js
324 ms
videocontrol.js
322 ms
iframe_api
153 ms
mobile-logo.png
153 ms
WFLogotypeWhite.png
154 ms
LogoWellframeWhite.png
153 ms
how-we-work.png
151 ms
close.png
151 ms
video-request-a-demo.png
149 ms
hex_1.png
171 ms
hex_2.png
171 ms
hex_3.png
171 ms
hex_4.png
170 ms
white_iphone_1.png
825 ms
MonitorImage.png
968 ms
chat.png
959 ms
library_and_graph.png
1132 ms
trials_1.jpg
361 ms
trials_2.jpg
360 ms
LogoRockHealth.png
459 ms
footer-logo.png
456 ms
133688566
261 ms
HeaderOrange.png
795 ms
header_image_home.jpg
909 ms
line.png
804 ms
gradient.png
866 ms
webinar_text_photo.png
1069 ms
whitepaper_text_photo.png
1316 ms
case_study_text_photo.png
1171 ms
bg_value_props.jpg
1004 ms
bg.jpg
1002 ms
gradient_2.png
1137 ms
vinfen.jpg
1138 ms
IconName.png
1132 ms
IconCompany.png
1158 ms
IconEmail.png
1199 ms
FiraSans-Regular.woff
25 ms
FiraSans-Medium.woff
156 ms
FiraSans-Light.woff
167 ms
FiraSans-UltraLight.woff
153 ms
FiraSans-Hair.woff
203 ms
FiraSans-SemiBold.woff
207 ms
FiraSans-Bold.woff
207 ms
FiraSans-ExtraBold.woff
300 ms
FiraSans-Heavy.woff
300 ms
FiraSans-BoldItalic.woff
300 ms
FiraSans-ExtraBoldItalic.woff
300 ms
FiraSans-HeavyItalic.woff
367 ms
FiraSans-SemiBoldItalic.woff
372 ms
FiraSans-MediumItalic.woff
421 ms
FiraSans-Italic.woff
431 ms
FiraSans-LightItalic.woff
421 ms
FiraSans-UltraLightItalic.woff
419 ms
FiraSans-HairItalic.woff
550 ms
BrandonGrotesque-Bold.otf
1086 ms
XpaepWHcooQHSRnzoohUng.woff
266 ms
hvd_fonts_-_brandontext-bold-webfont.woff
1085 ms
hvd_fonts_-_brandontext-regular-webfont.woff
1102 ms
brandon_med-webfont.woff
1108 ms
www-widgetapi.js
237 ms
munchkin.js
393 ms
sf14g.js
720 ms
ga.js
388 ms
21d8e9cf-ea7c-41d2-9d23-2fca8181021c.js
518 ms
player.js
447 ms
player.css
424 ms
vuid.min.js
445 ms
munchkin.js
78 ms
__utm.gif
64 ms
visitWebPage
156 ms
__utm.gif
136 ms
proxy.html
72 ms
collect
73 ms
tl813.js
430 ms
tl813.asp
81 ms
dot.gif
78 ms
wellfra.me 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
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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
wellfra.me 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
Browser errors were logged to the console
wellfra.me 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
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 Wellfra.me 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 Wellfra.me 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.
wellfra.me
Open Graph description is not detected on the main page of Wellfra. 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: