Tools & Wizards About Us
wontex.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

wontex.com

Best CAT6a Cable Suppliers, CAT 8 Cable Manufacturer, CAT 6 Cable Manufacturer - Wonderful HI-TECH

Page Load Speed

6.5 sec in total

First Response

657 ms

Resources Loaded

5.5 sec

Page Rendered

416 ms

wontex.com screenshot

About Website

Visit wontex.com now to see the best up-to-date Wontex content and also check out these interesting facts you probably never knew about wontex.com

Wonderful HI-TECH is the leading cable manufacturer & supplier in Taiwan. Best cat6/cat6a/cat8 cable manufacturer. We provide high quality cat6a cable, cat6 cable and cat8 cable for network and ethern...

Visit wontex.com

Key Findings

We analyzed Wontex.com page load time and found that the first response time was 657 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

wontex.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value14.3 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

wontex.com

657 ms

wontex.com

1641 ms

main.css

434 ms

js

74 ms

js

119 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 79% of them (50 requests) were addressed to the original Wontex.com, 11% (7 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Wontex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 341.2 kB (11%)

Content Size

3.2 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wontex.com main page is 3.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. 60% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 24.5 kB

  • Original 29.4 kB
  • After minification 16.4 kB
  • After compression 4.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 13.0 kB, which is 44% 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 24.5 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 79.9 kB

  • Original 2.8 MB
  • After minification 2.7 MB

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. Wontex images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 170.0 kB

  • Original 243.9 kB
  • After minification 242.4 kB
  • After compression 73.9 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 170.0 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 66.8 kB

  • Original 80.2 kB
  • After minification 70.7 kB
  • After compression 13.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. Wontex.com needs all CSS files to be minified and compressed as it can save up to 66.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (28%)

Requests Now

54

After Optimization

39

  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wontex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wontex.com

wontex.com

657 ms

wontex.com

wontex.com

1641 ms

main.css

main.css

434 ms

js

js

74 ms

js

js

119 ms

js

js

143 ms

index.css

index.css

870 ms

function.js

function.js

881 ms

index.js

index.js

1114 ms

function.js

function.js

589 ms

css2

css2

33 ms

css2

css2

49 ms

gtm.js

gtm.js

65 ms

logo.png

logo.png

472 ms

logo_wdftech_en.png

logo_wdftech_en.png

527 ms

2023_09_13_1619392.jpeg

2023_09_13_1619392.jpeg

1261 ms

2023_09_13_1619394.jpeg

2023_09_13_1619394.jpeg

1260 ms

2023_09_13_1620052.jpeg

2023_09_13_1620052.jpeg

1798 ms

2023_09_13_1620054.jpeg

2023_09_13_1620054.jpeg

1507 ms

2023_09_01_1429162.jpeg

2023_09_01_1429162.jpeg

1485 ms

2023_08_23_1630244.jpeg

2023_08_23_1630244.jpeg

1504 ms

2023_09_13_1620372.jpeg

2023_09_13_1620372.jpeg

1913 ms

2023_09_13_1620374.jpeg

2023_09_13_1620374.jpeg

1482 ms

p_icon1.png

p_icon1.png

1700 ms

p_icon2.png

p_icon2.png

1703 ms

p_icon3.png

p_icon3.png

1724 ms

index_circle.jpg

index_circle.jpg

1704 ms

index_circle_mo.jpg

index_circle_mo.jpg

1919 ms

menu_sec.jpg

menu_sec.jpg

1531 ms

icon1.png

icon1.png

1509 ms

icon1_w.png

icon1_w.png

1553 ms

icon2.png

icon2.png

1625 ms

icon2_w.png

icon2_w.png

1705 ms

icon3.png

icon3.png

1739 ms

icon3_w.png

icon3_w.png

1746 ms

icon4.png

icon4.png

1749 ms

icon4_w.png

icon4_w.png

1774 ms

icon5.png

icon5.png

1845 ms

icon5_w.png

icon5_w.png

1900 ms

icon6.png

icon6.png

1957 ms

icon6_w.png

icon6_w.png

1964 ms

icon7.png

icon7.png

1966 ms

icon7_w.png

icon7_w.png

1994 ms

icon8.png

icon8.png

2065 ms

icon8_w.png

icon8_w.png

2096 ms

a_img1.png

a_img1.png

2175 ms

a_img2.png

a_img2.png

2106 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

23 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

41 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

63 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

58 ms

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz75Ky_Co.ttf

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz75Ky_Co.ttf

269 ms

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz76Cy_Co.ttf

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz76Cy_Co.ttf

274 ms

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz70e1_Co.ttf

-nFuOG829Oofr2wohFbTp9ifNAn722rq0MXz70e1_Co.ttf

275 ms

news_arrow.png

news_arrow.png

2107 ms

b_img1.png

b_img1.png

2083 ms

b_img2.png

b_img2.png

2068 ms

contactBg.jpg

contactBg.jpg

2044 ms

phone_b.png

phone_b.png

1530 ms

phone_w.png

phone_w.png

1535 ms

mg_b.png

mg_b.png

1315 ms

mg_w.png

mg_w.png

1344 ms

gotop.png

gotop.png

1398 ms

Accessibility Review

wontex.com accessibility score

77

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.

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

High

Links do not have a discernible name

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

wontex.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wontex.com SEO score

76

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    TW

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wontex.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 Twi language. Our system also found out that Wontex.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

wontex.com

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