Tools & Wizards About Us
tws.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

tws.com

TWS Group

Page Load Speed

6.8 sec in total

First Response

585 ms

Resources Loaded

6.1 sec

Page Rendered

161 ms

tws.com screenshot

About Website

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

广州明美新能源有限公司

Visit tws.com

Key Findings

We analyzed Tws.com page load time and found that the first response time was 585 ms and then it took 6.2 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

tws.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.699

7/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

www.tws.com

585 ms

swiper.min.css

284 ms

jquery.fullPage.css

287 ms

font_1393039_elnf0mq9kbd.css

26 ms

css.css

294 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 96% of them (54 requests) were addressed to the original Tws.com, 2% (1 request) were made to At.alicdn.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Tws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 286.9 kB (4%)

Content Size

7.1 MB

After Optimization

6.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 37.8 kB

  • Original 43.3 kB
  • After minification 27.8 kB
  • After compression 5.5 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 15.5 kB, which is 36% 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 37.8 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 222.9 kB

  • Original 6.9 MB
  • After minification 6.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. TWS images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 24.3 kB

  • Original 91.8 kB
  • After minification 76.9 kB
  • After compression 67.5 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 24.3 kB or 26% of the original size.

CSS Optimization

-8%

Potential reduce by 1.9 kB

  • Original 25.4 kB
  • After minification 25.4 kB
  • After compression 23.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. Tws.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (19%)

Requests Now

54

After Optimization

44

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.tws.com

www.tws.com

585 ms

swiper.min.css

swiper.min.css

284 ms

jquery.fullPage.css

jquery.fullPage.css

287 ms

font_1393039_elnf0mq9kbd.css

font_1393039_elnf0mq9kbd.css

26 ms

css.css

css.css

294 ms

js

js

61 ms

jquery.js

jquery.js

392 ms

jquery.fullPage.min.js

jquery.fullPage.min.js

391 ms

ifie8.js

ifie8.js

391 ms

fastclick.js

fastclick.js

571 ms

swiper-3.4.1.min.js

swiper-3.4.1.min.js

671 ms

js.js

js.js

581 ms

ellipsis.js

ellipsis.js

580 ms

a8144b3f33ee9466def92ec225a7f67.jpg

a8144b3f33ee9466def92ec225a7f67.jpg

387 ms

earth.png

earth.png

368 ms

earth2.png

earth2.png

557 ms

xg.png

xg.png

563 ms

menu2.png

menu2.png

572 ms

menu.png

menu.png

648 ms

Banner-green-1-2.jpg

Banner-green-1-2.jpg

1233 ms

Banner-green-2-2.jpg

Banner-green-2-2.jpg

1326 ms

ll.png

ll.png

846 ms

rr.png

rr.png

851 ms

about%20tws-certifications.png

about%20tws-certifications.png

1166 ms

315848242.jpg

315848242.jpg

1306 ms

eBus-4.jpg

eBus-4.jpg

1749 ms

325303410%201920%20870.jpg

325303410%201920%20870.jpg

1944 ms

shutterstock_2139683951.jpg

shutterstock_2139683951.jpg

2033 ms

350572307_1920%20870.jpg

350572307_1920%20870.jpg

2193 ms

1%20(2).jpg

1%20(2).jpg

1963 ms

202002251804542401.jpg

202002251804542401.jpg

2173 ms

Solar%20Panels%20-homepage.jpg

Solar%20Panels%20-homepage.jpg

2639 ms

202002251807217013.png

202002251807217013.png

2505 ms

309834776_1.jpg

309834776_1.jpg

2736 ms

lb.png

lb.png

2323 ms

lbh.png

lbh.png

2463 ms

rb.png

rb.png

2474 ms

rbh.png

rbh.png

2605 ms

Competitive%20edge-3.jpg

Competitive%20edge-3.jpg

3027 ms

ESS%20-%20790%20444.jpg

ESS%20-%20790%20444.jpg

2852 ms

x1.png

x1.png

2794 ms

group%20photo-SH%20790%20444.jpg

group%20photo-SH%20790%20444.jpg

3093 ms

AEO-790%20440.png

AEO-790%20440.png

3329 ms

IBS-790%20444.png

IBS-790%20444.png

3506 ms

Lato-Regular.ttf

Lato-Regular.ttf

3099 ms

Connect%20to%20the%20Grid_2_790%20444.jpg

Connect%20to%20the%20Grid_2_790%20444.jpg

3194 ms

SD%20group%20photo-2.jpg

SD%20group%20photo-2.jpg

3335 ms

in.png

in.png

3190 ms

inh.png

inh.png

3109 ms

F1.png

F1.png

3336 ms

F2.png

F2.png

3354 ms

T.png

T.png

3196 ms

T2.png

T2.png

3193 ms

wx.png

wx.png

3302 ms

202005191558375309.jpg

202005191558375309.jpg

3337 ms

wxh.png

wxh.png

3156 ms

Accessibility Review

tws.com accessibility score

63

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

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

tws.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tws.com SEO score

89

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tws.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 Tws.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

tws.com

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