5.8 sec in total
403 ms
5.3 sec
145 ms
Welcome to wiihey.com homepage info - get ready to check Wii Hey best content right away, or after learning these important things about wiihey.com
WiiHey is dedicated in developing IoT (Internet of Things) monitoring sensors for smart city, smart traffic, and smart industry 4.0
Visit wiihey.comWe analyzed Wiihey.com page load time and found that the first response time was 403 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
wiihey.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value8.0 s
3/100
25%
Value11.6 s
4/100
10%
Value1,240 ms
19/100
30%
Value0.405
24/100
15%
Value18.9 s
3/100
10%
403 ms
482 ms
440 ms
37 ms
56 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Wiihey.com, 44% (27 requests) were made to G.alicdn.com and 16% (10 requests) were made to Img.alicdn.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Gm.mmstat.com.
Page size can be reduced by 848.6 kB (43%)
2.0 MB
1.1 MB
In fact, the total size of Wiihey.com main page is 2.0 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. 40% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 687.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. 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 687.6 kB or 88% of the original size.
Potential reduce by 701 B
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. Wii Hey images are well optimized though.
Potential reduce by 129.3 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 129.3 kB or 13% of the original size.
Potential reduce by 31.0 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. Wiihey.com needs all CSS files to be minified and compressed as it can save up to 31.0 kB or 20% of the original size.
Number of requests can be reduced by 37 (64%)
58
21
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wii Hey. 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 20 to 1 for CSS and as a result speed up the page load time.
wiihey.com
403 ms
ipvisit_stop
482 ms
g.alicdn.com
440 ms
font_1175572_77a2hn4ww6y.css
37 ms
font_276948_28ii451l5wi.css
56 ms
font_274588_tf6h927cvbl.css
61 ms
qihang.domain.css
1158 ms
g.alicdn.com
513 ms
g.alicdn.com
582 ms
qihang.webview-js
1165 ms
716 ms
website.js
131 ms
g.alicdn.com
907 ms
g.alicdn.com
710 ms
index.js
625 ms
g.alicdn.com
761 ms
g.alicdn.com
642 ms
O1CN01Y4zlbt1zQJc4eBTUq_!!6000000006708-2-tps-300-48.png
237 ms
O1CN01e6cLzB1R2JxLfeCCg_!!6000000002053-2-tps-84-34.png
246 ms
O1CN01CPTCiG1QLj7jCm0nB_!!6000000001960-0-tps-258-258.jpg
247 ms
O1CN01pNeNL61Xl6NPiR5on_!!6000000002963-0-tps-258-258.jpg
252 ms
TB1i3Hdjkcx_u4jSZFlXXXnUFXa-944-649.png
252 ms
bl.js
2024 ms
index.css
79 ms
155 ms
font_1175572_77a2hn4ww6y.woff
13 ms
fsp.1.1
2303 ms
fsp.1.1
2525 ms
delivery.service.engine
1682 ms
index.js
80 ms
g.alicdn.com
155 ms
font_1175572_77a2hn4ww6y.css
15 ms
font_276948_28ii451l5wi.css
35 ms
font_274588_tf6h927cvbl.css
37 ms
qihang.domain.css
227 ms
g.alicdn.com
81 ms
g.alicdn.com
68 ms
index.css
68 ms
Account.js
81 ms
index.css
78 ms
1437 ms
Account.css
1354 ms
queryUserBaseInfo
2312 ms
88 ms
O1CN01CPTCiG1QLj7jCm0nB_!!6000000001960-0-tps-258-258.jpg
21 ms
getTimestamp
1268 ms
govern
715 ms
delivery.config.customRules.leads-script
223 ms
O1CN01pNeNL61Xl6NPiR5on_!!6000000002963-0-tps-258-258.jpg
33 ms
index.css
67 ms
74 ms
index.css
67 ms
76 ms
TB1UdKEM6TpK1RjSZKPXXa3UpXa-256-256.png
17 ms
TB1GxwdSXXXXXa.aXXXXXXXXXXX-65-70.gif
503 ms
TB1AOdINW6qK1RjSZFmXXX0PFXa-258-258.jpg
7 ms
TB1..50QpXXXXX7XpXXXXXXXXXX-40-40.png
15 ms
Leads.js
79 ms
Delivery.js
93 ms
fsp.1.1
618 ms
aliyun-config.services.black_white
233 ms
wiihey.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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wiihey.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
wiihey.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wiihey.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that Wiihey.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.
wiihey.com
Open Graph description is not detected on the main page of Wii Hey. 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: