2.7 sec in total
458 ms
1.7 sec
572 ms
Welcome to weewelcome.ca homepage info - get ready to check Wee Welcome best content right away, or after learning these important things about weewelcome.ca
Visit weewelcome.caWe analyzed Weewelcome.ca page load time and found that the first response time was 458 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.
weewelcome.ca performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value24.0 s
0/100
25%
Value11.2 s
5/100
10%
Value210 ms
89/100
30%
Value0
100/100
15%
Value21.8 s
1/100
10%
458 ms
68 ms
33 ms
60 ms
61 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 90% of them (47 requests) were addressed to the original Weewelcome.ca, 6% (3 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (458 ms) belongs to the original domain Weewelcome.ca.
Page size can be reduced by 2.2 MB (49%)
4.5 MB
2.3 MB
In fact, the total size of Weewelcome.ca main page is 4.5 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. Javascripts take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 60.6 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 8.8 kB, which is 12% 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 60.6 kB or 82% of the original size.
Potential reduce by 42.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. Wee Welcome images are well optimized though.
Potential reduce by 1.4 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.4 MB or 65% of the original size.
Potential reduce by 707.5 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. Weewelcome.ca needs all CSS files to be minified and compressed as it can save up to 707.5 kB or 88% of the original size.
Number of requests can be reduced by 31 (65%)
48
17
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wee Welcome. 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 14 to 1 for CSS and as a result speed up the page load time.
www.weewelcome.ca
458 ms
style.min.css
68 ms
blossomthemes-email-newsletter-public.min.css
33 ms
blossomthemes-toolkit-public.min.css
60 ms
8ea4227de436b97db4f5898c80f8b252.css
61 ms
bootstrap.css
103 ms
bootstrap.css
109 ms
style.css
89 ms
style.css
71 ms
css
32 ms
css2
48 ms
css
51 ms
font-awesome.min.css
72 ms
slick.css
74 ms
jquery.min.js
84 ms
jquery-migrate.min.js
87 ms
slick.js
131 ms
wpforms-full.min.css
89 ms
script.js
119 ms
isotope.pkgd.min.js
118 ms
imagesloaded.min.js
119 ms
masonry.min.js
119 ms
blossomthemes-toolkit-public.min.js
119 ms
all.min.js
188 ms
v4-shims.min.js
155 ms
navigation.js
155 ms
script.js
155 ms
custom.js
156 ms
skip-link-focus-fix.js
156 ms
jquery.validate.min.js
157 ms
mailcheck.min.js
157 ms
punycode.min.js
156 ms
utils.min.js
157 ms
wpforms.min.js
157 ms
www.weewelcome.ca
329 ms
cropped-logo.png
29 ms
family-smoking.jpg
16 ms
children-social-media_custom-c66defa40e13aaa177a9b8d2c220f1892646e1b1-e1659860526714.jpg
16 ms
playing-fun-child-modern-mother-home-daughter-together-mom-parenting_t20_GgVVm0-1440x960-1-e1659860866795.jpg
17 ms
Baby-eating-formula--800x500.jpg
32 ms
05-30-19-bond-with-your-child-e1659860725232.jpg
32 ms
GettyImages-620920609-2400x1440-1-e1659860399451.jpg
32 ms
Baby-eating-formula-.jpg
158 ms
ezgif.com-gif-maker-2022-08-07T103517.009.jpg
159 ms
online-grocery-shopping-e1659861178621.jpg
158 ms
b25lY21zOjhhMjA2NWQyLTI4N2YtNGE0Ni1hMDBjLWQ4OWYxZWZlYzY5MTplYjkxYzQ0ZS00N2UxLTQxMzYtOGY1ZS0zMThmY2ZhMTEyMzY.jpg
159 ms
GettyImages-1001722430-6562830a8156455da04b458a38a0492f-e1659859199694.jpg
160 ms
2e06a4a9630170ee1400b65b709f7b55.jpg
160 ms
submit-spin.svg
161 ms
S6uyw4BMUTPHjx4wWw.ttf
54 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
55 ms
fontawesome-webfont.woff
54 ms
weewelcome.ca accessibility score
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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
No form fields have multiple labels
Links do not have a discernible name
weewelcome.ca 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
Missing source maps for large first-party JavaScript
weewelcome.ca 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weewelcome.ca 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 Weewelcome.ca 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.
weewelcome.ca
Open Graph description is not detected on the main page of Wee Welcome. 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: