4.7 sec in total
876 ms
3 sec
846 ms
Click here to check amazing Wehealth content for United States. Otherwise, check out these important facts you probably never knew about wehealth.org
Stay informed and safe with the Wehealth Notify App, providing real-time alerts and resources for health and safety risks across communities. Download now for free.
Visit wehealth.orgWe analyzed Wehealth.org page load time and found that the first response time was 876 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
wehealth.org performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value7.6 s
4/100
25%
Value7.1 s
31/100
10%
Value900 ms
31/100
30%
Value0.122
84/100
15%
Value14.1 s
9/100
10%
876 ms
282 ms
424 ms
241 ms
341 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 81% of them (44 requests) were addressed to the original Wehealth.org, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to Js.hubspot.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Wehealth.org.
Page size can be reduced by 320.6 kB (15%)
2.2 MB
1.8 MB
In fact, the total size of Wehealth.org main page is 2.2 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. 45% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 175.9 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 34.8 kB, which is 18% 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 175.9 kB or 89% of the original size.
Potential reduce by 129.6 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. Wehealth images are well optimized though.
Potential reduce by 7.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 7.7 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. Wehealth.org needs all CSS files to be minified and compressed as it can save up to 7.7 kB or 22% of the original size.
Number of requests can be reduced by 25 (48%)
52
27
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wehealth. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.wehealth.org
876 ms
main-head.min.css
282 ms
global-header-v2.min.css
424 ms
global-footer.min.css
241 ms
hero-banner.min.css
341 ms
slick-slider.min.css
264 ms
module_155136583751_CLEAN_Pro_-_Count_Up.min.css
249 ms
clean-foundation.min.css
457 ms
module_155135312500_CLEAN_Pro_-_Content_Slider.css
443 ms
js
94 ms
jquery-1.7.1.js
307 ms
embed.js
340 ms
clean-pro.min.js
554 ms
jquery-modal-min.min.js
565 ms
project.js
388 ms
mega-menu.min.js
623 ms
module_155135312504_Global_Footer.min.js
643 ms
web-interactives-embed.js
71 ms
slick-slider-min.min.js
663 ms
number-count-up.min.js
626 ms
loader.js
51 ms
7663287.js
657 ms
index.js
614 ms
interactive-162864868369.png
190 ms
lazy-img-800x500.png
107 ms
Logo_Wehealth_Web.png
379 ms
Logo_UofA.png
424 ms
Logo_ADHS.png
415 ms
Logo_Bermuda.png
462 ms
Logo_StartupHealth.png
443 ms
Logo_LFPH.png
504 ms
WH_Hero.png
454 ms
Feature_App_01.png
792 ms
Logo-WRN-NOAA.png
729 ms
Logo-UofA.png
1115 ms
Logo-ADHS.png
763 ms
Logo-Bermuda.png
717 ms
Feature_App_01.png
848 ms
Feature_App_02.png
1040 ms
Feature_App_03.png
1055 ms
Feature_App_04.png
1048 ms
Feature_App_05.png
987 ms
Feature_App_06.png
1287 ms
Feature_App_07.png
1391 ms
Wehealth_Portal.png
1365 ms
Feature_QA_01.png
1373 ms
Feature_API_01.png
1341 ms
Logo_Wehealth_Web_Dk.png
1152 ms
Europa.15528.otf
1142 ms
banner.js
121 ms
fb.js
54 ms
collectedforms.js
95 ms
leadflows.js
71 ms
7663287.js
138 ms
wehealth.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
wehealth.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
wehealth.org 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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wehealth.org 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 Wehealth.org 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.
wehealth.org
Open Graph data is detected on the main page of Wehealth. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: