Tools & Wizards About Us
wtau.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wtau.com

「微特」起重机安全监控管理系统,力矩限制器,超载限制器,起重量限制器,闸门开度荷重仪,风速仪等起重安全监控产品研发生产销售一体 - 微特技术有限公司 - 「微特」起重机安全监控管理系统,力矩限制器,超载限制器,起重量限制器,闸门开度荷重仪,风速仪等起重安全监控产品研发生产销售一体 - 微特技术有限公...

Page Load Speed

52 sec in total

First Response

10.5 sec

Resources Loaded

41.3 sec

Page Rendered

215 ms

wtau.com screenshot

About Website

Click here to check amazing Wtau content. Otherwise, check out these important facts you probably never knew about wtau.com

微特技术有限公司（服务热线：400-008-2600 15507209355 付工）自主研制的产品:起重机安全监控管理系统(桥式起重机安全监控管理系统、门式起重机安全监控管理系统、架桥机安全监控管理系统等),超载限制器,力矩限制器,闸门开度荷重仪,风速风向仪(塔机/塔吊风速仪),行程限位器(起升高度限制器),声波吹灰器等起重安全监控产品,广泛应用于电力、化工、钢铁、冶金、施工、建筑、港口、海工等行...

Visit wtau.com

Key Findings

We analyzed Wtau.com page load time and found that the first response time was 10.5 sec and then it took 41.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 20 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

wtau.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value2,640 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.104

89/100

15%

TTI (Time to Interactive)

Value13.7 s

10/100

10%

Network Requests Diagram

wtau.com

10450 ms

style.css

9420 ms

common.css

859 ms

index.css

2066 ms

jquery-1.11.1.min.js

9699 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 65% of them (62 requests) were addressed to the original Wtau.com, 14% (13 requests) were made to Qiao.baidu.com and 6% (6 requests) were made to P6.qiao.baidu.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Wtau.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 219.4 kB (28%)

Content Size

789.6 kB

After Optimization

570.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wtau.com main page is 789.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 525.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 42.0 kB

  • Original 54.0 kB
  • After minification 49.0 kB
  • After compression 12.1 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 42.0 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 25.6 kB

  • Original 525.9 kB
  • After minification 500.4 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. Wtau images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 76.7 kB

  • Original 118.2 kB
  • After minification 117.6 kB
  • After compression 41.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 76.7 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 75.1 kB

  • Original 91.4 kB
  • After minification 76.1 kB
  • After compression 16.3 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. Wtau.com needs all CSS files to be minified and compressed as it can save up to 75.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (55%)

Requests Now

73

After Optimization

33

  • Images
  • JavaScript
  • CSS

The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wtau. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wtau.com

wtau.com

10450 ms

style.css

style.css

9420 ms

common.css

common.css

859 ms

index.css

index.css

2066 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

9699 ms

huhu.js

huhu.js

882 ms

xixi.js

xixi.js

7947 ms

index.js

index.js

1700 ms

top1.jpg

top1.jpg

679 ms

top2.jpg

top2.jpg

677 ms

top3.jpg

top3.jpg

682 ms

top4.jpg

top4.jpg

679 ms

top5.jpg

top5.jpg

679 ms

logo.jpg

logo.jpg

1698 ms

search-bt.gif

search-bt.gif

1367 ms

dao_bg1.jpg

dao_bg1.jpg

1401 ms

js_t1.jpg

js_t1.jpg

2692 ms

1-160322095229404-lp.jpg

1-160322095229404-lp.jpg

2014 ms

1-160315154SIR-lp.jpg

1-160315154SIR-lp.jpg

2049 ms

gc4.jpg

gc4.jpg

8860 ms

gc2.jpg

gc2.jpg

15993 ms

gc3.jpg

gc3.jpg

14284 ms

gc1.jpg

gc1.jpg

8171 ms

olli1.jpg

olli1.jpg

3327 ms

olli2.jpg

olli2.jpg

3985 ms

olli3.jpg

olli3.jpg

4400 ms

olli4.jpg

olli4.jpg

6219 ms

olli5.jpg

olli5.jpg

5599 ms

no5lii.jpg

no5lii.jpg

13517 ms

1-16040QAA1215.jpg

1-16040QAA1215.jpg

20399 ms

1-160330094IM29.jpg

1-160330094IM29.jpg

20399 ms

lx_r1_c1.jpg

lx_r1_c1.jpg

14363 ms

tel.jpg

tel.jpg

15034 ms

banner.jpg

banner.jpg

20398 ms

banner_2.jpg

banner_2.jpg

20397 ms

banner_3.jpg

banner_3.jpg

20397 ms

banner_ctrl.png

banner_ctrl.png

16828 ms

sj.jpg

sj.jpg

20040 ms

qqon.png

qqon.png

20396 ms

ww.png

ww.png

20396 ms

02.png

02.png

20395 ms

03.png

03.png

20395 ms

04.png

04.png

20395 ms

05.png

05.png

20376 ms

h.js

h.js

1431 ms

06.png

06.png

19734 ms

07.png

07.png

19734 ms

1504291552569244.png

1504291552569244.png

19732 ms

1504290957027796.png

1504290957027796.png

19731 ms

1504290957273990.png

1504290957273990.png

19731 ms

1504290957551693.png

1504290957551693.png

20038 ms

1504291420554307.png

1504291420554307.png

19795 ms

s.js

s.js

3810 ms

lxb.js

lxb.js

2405 ms

b.js

b.js

870 ms

hm.gif

hm.gif

502 ms

1504291421511151.png

1504291421511151.png

19707 ms

1504291425071864.png

1504291425071864.png

19206 ms

1504291531466612.png

1504291531466612.png

19212 ms

bsl.js

bsl.js

944 ms

1504291532232653.png

1504291532232653.png

19294 ms

Enter.php

Enter.php

761 ms

main_icon_invite_mess_api.js

main_icon_invite_mess_api.js

1710 ms

main.css

main.css

627 ms

fix.css

fix.css

764 ms

1504291533064177.png

1504291533064177.png

18718 ms

version.js

version.js

783 ms

log.gif

log.gif

304 ms

_l.js

_l.js

712 ms

1504291534007824.png

1504291534007824.png

18071 ms

1504291534297101.png

1504291534297101.png

17824 ms

log.gif

log.gif

365 ms

09.jpg

09.jpg

2826 ms

m-webim-lite.css

m-webim-lite.css

1964 ms

m-webim-lite.js

m-webim-lite.js

1306 ms

Refresh.php

Refresh.php

398 ms

stat.gif

stat.gif

750 ms

mess-text.png

mess-text.png

680 ms

messbtn.png

messbtn.png

677 ms

mess.gif

mess.gif

4993 ms

btn.png

btn.png

1026 ms

footer_logo.jpg

footer_logo.jpg

18674 ms

gsname.jpg

gsname.jpg

17080 ms

invitehead.jpg

invitehead.jpg

7088 ms

btn.png

btn.png

20338 ms

foot_nav.jpg

foot_nav.jpg

20230 ms

sbtn.png

sbtn.png

17606 ms

Refresh.php

Refresh.php

437 ms

Refresh.php

Refresh.php

485 ms

Refresh.php

Refresh.php

394 ms

Refresh.php

Refresh.php

416 ms

api

api

588 ms

hm.gif

hm.gif

883 ms

bigMapIcon.jpg

bigMapIcon.jpg

607 ms

hm.gif

hm.gif

894 ms

Accessibility Review

wtau.com accessibility score

76

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Image elements do not have [alt] attributes

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

wtau.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wtau.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wtau.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Wtau.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.

Social Sharing Optimization

wtau.com

Open Graph description is not detected on the main page of Wtau. 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: