Tools & Wizards About Us
thomsonreuters.cn screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

thomsonreuters.cn

China | 中国 | 汤森路透

Page Load Speed

8.9 sec in total

First Response

91 ms

Resources Loaded

6.3 sec

Page Rendered

2.5 sec

thomsonreuters.cn screenshot

About Website

Visit thomsonreuters.cn now to see the best up-to-date Thomsonreuters content for China and also check out these interesting facts you probably never knew about thomsonreuters.cn

信息•科技•专业，我们助您运筹决策。

Visit thomsonreuters.cn

Key Findings

We analyzed Thomsonreuters.cn page load time and found that the first response time was 91 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

thomsonreuters.cn performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value1,870 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

www.thomsonreuters.cn

91 ms

www.thomsonreuters.cn

41 ms

zh.html

29 ms

datadog-rum.js

54 ms

clientlib-bayberry.min.css

12 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 23% of them (19 requests) were addressed to the original Thomsonreuters.cn, 12% (10 requests) were made to App-data.gcs.trstatic.net and 11% (9 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Thomsonreuters.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 416.6 kB (7%)

Content Size

6.2 MB

After Optimization

5.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thomsonreuters.cn main page is 6.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 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 210.9 kB

  • Original 241.6 kB
  • After minification 190.1 kB
  • After compression 30.7 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 51.5 kB, which is 21% 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 210.9 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 157.5 kB

  • Original 4.7 MB
  • After minification 4.6 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. Thomsonreuters images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 48.2 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 1.2 MB

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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 4.1 kB
  • After minification 4.1 kB
  • After compression 4.1 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. Thomsonreuters.cn has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (76%)

Requests Now

63

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.thomsonreuters.cn

www.thomsonreuters.cn

91 ms

www.thomsonreuters.cn

www.thomsonreuters.cn

41 ms

zh.html

zh.html

29 ms

datadog-rum.js

datadog-rum.js

54 ms

clientlib-bayberry.min.css

clientlib-bayberry.min.css

12 ms

clientlib-bayberry.min.js

clientlib-bayberry.min.js

36 ms

clientlib-dcl_components.min.css

clientlib-dcl_components.min.css

36 ms

clientlib-dcl_components.min.js

clientlib-dcl_components.min.js

48 ms

head.js

head.js

89 ms

adrum-21.4.0.3405.js

adrum-21.4.0.3405.js

70 ms

launch-b8c933003680.min.js

launch-b8c933003680.min.js

71 ms

otSDKStub.js

otSDKStub.js

71 ms

jquery.min.js

jquery.min.js

43 ms

utils.min.js

utils.min.js

49 ms

granite.min.js

granite.min.js

50 ms

clientlibs-gated-content.min.js

clientlibs-gated-content.min.js

50 ms

clientlibs-smartcrop.min.js

clientlibs-smartcrop.min.js

48 ms

tracking-clientlibs.min.js

tracking-clientlibs.min.js

65 ms

main.js

main.js

91 ms

pagestyle-clientlibs.min.css

pagestyle-clientlibs.min.css

66 ms

css2

css2

40 ms

css2

css2

22 ms

eac591d9-9ccb-481b-b0df-23ae7f36d46c.json

eac591d9-9ccb-481b-b0df-23ae7f36d46c.json

225 ms

token.json

token.json

211 ms

decoding-determination-2880x710:Hero-s

decoding-determination-2880x710:Hero-s

278 ms

5.js

5.js

125 ms

0.js

0.js

133 ms

1.js

1.js

132 ms

4.js

4.js

166 ms

6.js

6.js

141 ms

29.js

29.js

137 ms

14.js

14.js

141 ms

28.js

28.js

149 ms

decoding-determination-2880x710.jpg

decoding-determination-2880x710.jpg

66 ms

fta_head7.jpg

fta_head7.jpg

5505 ms

trade-chat-back.png

trade-chat-back.png

379 ms

tr-techfuture-image.jpg

tr-techfuture-image.jpg

106 ms

fta_head7:Hero-xs

fta_head7:Hero-xs

450 ms

trade-chat-back:Hero-s

trade-chat-back:Hero-s

176 ms

tr-techfuture-image:Hero-m

tr-techfuture-image:Hero-m

351 ms

location

location

95 ms

otBannerSdk.js

otBannerSdk.js

17 ms

en.json

en.json

24 ms

otFlat.json

otFlat.json

16 ms

otPcCenter.json

otPcCenter.json

18 ms

otCommonStyles.css

otCommonStyles.css

19 ms

launch-b8c933003680.min.js

launch-b8c933003680.min.js

63 ms

ot_close.svg

ot_close.svg

59 ms

TR.png

TR.png

42 ms

id

id

42 ms

EX3ec994a14f3c4a849c5b38afa1440a3b-libraryCode_source.min.js

EX3ec994a14f3c4a849c5b38afa1440a3b-libraryCode_source.min.js

24 ms

AppMeasurement_Module_AudienceManagement.min.js

AppMeasurement_Module_AudienceManagement.min.js

48 ms

elqCfg.min.js

elqCfg.min.js

76 ms

up_loader.1.1.0.js

up_loader.1.1.0.js

71 ms

js

js

80 ms

RC356086e8a2b443e5b0e01a9dc83936b7-source.min.js

RC356086e8a2b443e5b0e01a9dc83936b7-source.min.js

34 ms

dest5.html

dest5.html

53 ms

id

id

53 ms

hm.js

hm.js

1239 ms

svrGP

svrGP

99 ms

svrGP

svrGP

98 ms

ibs:dpid=411&dpuuid=Zq6TbQAAAE2sqANw

ibs:dpid=411&dpuuid=Zq6TbQAAAE2sqANw

6 ms

pixel

pixel

38 ms

pixel

pixel

19 ms

tap.php

tap.php

21 ms

rum

rum

24 ms

bounce

bounce

13 ms

sd

sd

10 ms

Pug

Pug

16 ms

partner

partner

3 ms

b.php

b.php

53 ms

partner.mediawallahscript.com

partner.mediawallahscript.com

19 ms

partner.mediawallahscript.com

partner.mediawallahscript.com

6 ms

partner.mediawallahscript.com

partner.mediawallahscript.com

5 ms

partner.mediawallahscript.com

partner.mediawallahscript.com

10 ms

generic

generic

16 ms

generic

generic

4 ms

partner.mediawallahscript.com

partner.mediawallahscript.com

6 ms

hm.gif

hm.gif

322 ms

RC3ec4f82b2e4f433181cffc6f02a0608a-source.min.js

RC3ec4f82b2e4f433181cffc6f02a0608a-source.min.js

8 ms

adrum-ext.281eccdb0a28fe3b4dbfbf942f8b88ed.js

adrum-ext.281eccdb0a28fe3b4dbfbf942f8b88ed.js

6 ms

Accessibility Review

thomsonreuters.cn accessibility score

89

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

thomsonreuters.cn 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

thomsonreuters.cn SEO score

79

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

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thomsonreuters.cn can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Thomsonreuters.cn 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

thomsonreuters.cn

Open Graph data is detected on the main page of Thomsonreuters. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: