3.7 sec in total
60 ms
1.5 sec
2.1 sec
Click here to check amazing WEMO That content for United States. Otherwise, check out these important facts you probably never knew about wemothat.com
WEMO is a growing family of innovative, easy-to-use products that use mobile internet to control your home electronics, power, water, and WiFi right from your smartphone or tablet. WEMO also works wit...
Visit wemothat.comWe analyzed Wemothat.com page load time and found that the first response time was 60 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.
wemothat.com performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value12.2 s
0/100
25%
Value10.4 s
8/100
10%
Value2,440 ms
5/100
30%
Value0.019
100/100
15%
Value13.5 s
11/100
10%
60 ms
8 ms
11 ms
13 ms
18 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wemothat.com, 7% (4 requests) were made to Google-analytics.com and 5% (3 requests) were made to Fast.wistia.net. The less responsive or slowest element that took the longest time to load (472 ms) relates to the external source Fast.wistia.net.
Page size can be reduced by 381.6 kB (20%)
1.9 MB
1.5 MB
In fact, the total size of Wemothat.com main page is 1.9 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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 21.8 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 3.9 kB, which is 13% 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 21.8 kB or 75% of the original size.
Potential reduce by 13.5 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. WEMO That images are well optimized though.
Potential reduce by 235.8 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 235.8 kB or 43% of the original size.
Potential reduce by 110.4 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. Wemothat.com needs all CSS files to be minified and compressed as it can save up to 110.4 kB or 85% of the original size.
Number of requests can be reduced by 31 (57%)
54
23
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WEMO That. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.wemo.com
60 ms
normalize.css
8 ms
slick.css
11 ms
jquery.mmenu.css
13 ms
magpop.css
18 ms
main.css
41 ms
modernizr-2.6.2.min.js
36 ms
media.match.min.js
28 ms
jquery-1.9.1.min.js
36 ms
jquery.mmenu.min.js
113 ms
jquery.mmenu.fixedelements.min.js
31 ms
jquery.magnific-popup.js
110 ms
waypoints.min.js
112 ms
custom_skrollr-min.js
109 ms
jquery.touchSwipe.min.js
107 ms
slick.min.js
110 ms
popover-v1.js
35 ms
main-min.js
137 ms
j.php
146 ms
gtm.js
153 ms
menuburger.svg
125 ms
wemo_logo.svg
130 ms
scrolldots.png
127 ms
photo_lighting_xl.jpg
132 ms
WeMO_THAT_4.svg
213 ms
product_lighting_sm.png
130 ms
photo_maker2_xl.jpg
236 ms
AND_THIS.svg
213 ms
product_maker_sm.png
164 ms
photo_insight_xl.jpg
165 ms
product_insight_sm.png
131 ms
photo_netcam_hd_xl.jpg
162 ms
product_netcam_hd_sm.png
239 ms
photo_rig_xl.jpg
261 ms
bigrig.svg
293 ms
threedeviceslg.png
331 ms
video_thumb_temp.png
418 ms
tempsprite@1x.png
237 ms
jquery.fancybox.css
98 ms
MetricWeb-Semibold.woff
211 ms
MetricWeb-Bold.woff
190 ms
v.gif
36 ms
24cdb03c7fb1531ba90818c0803d6002.js
16 ms
analytics.js
26 ms
embed_shepherd-v1.js
184 ms
bat.js
22 ms
fbevents.js
8 ms
112 ms
linkid.js
28 ms
iui3
31 ms
collect
12 ms
collect
56 ms
collect
32 ms
collect
31 ms
28060fda6ce72fa886eecb5b378f2736.js
68 ms
ga-audiences
130 ms
a04be9eaa6f1c17869518459f5d1e2cd.js
63 ms
iframe_shim
13 ms
E-v1.js
472 ms
wemothat.com 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
wemothat.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
wemothat.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
Image elements do not have [alt] attributes
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 Wemothat.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 Wemothat.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.
wemothat.com
Open Graph description is not detected on the main page of WEMO That. 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: