Tools & Wizards About Us
cdict.net screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

cdict.net

English-Chinese Dictionary (英漢字典)

Page Load Speed

6.4 sec in total

First Response

365 ms

Resources Loaded

5.9 sec

Page Rendered

129 ms

cdict.net screenshot

About Website

Visit cdict.net now to see the best up-to-date Cdict content for Taiwan and also check out these interesting facts you probably never knew about cdict.net

英漢/漢英/英英字典、拼音轉換、計算機(Online Chinese/English Dictionary)

Visit cdict.net

Key Findings

We analyzed Cdict.net page load time and found that the first response time was 365 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

cdict.net performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value2,880 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

cdict.net

365 ms

css

62 ms

style-1449758895.css

23 ms

jquery.min.js

42 ms

utils-1450800553.js

25 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cdict.net, 12% (11 requests) were made to Pagead2.googlesyndication.com and 8% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Ssl.sitemaji.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 117.6 kB (36%)

Content Size

331.2 kB

After Optimization

213.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cdict.net main page is 331.2 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. 60% of websites need less resources to load. Javascripts take 198.0 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 16.3 kB

  • Original 23.1 kB
  • After minification 23.0 kB
  • After compression 6.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. 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 16.3 kB or 71% of the original size.

Image Optimization

-19%

Potential reduce by 18.6 kB

  • Original 97.2 kB
  • After minification 78.6 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. Obviously, Cdict needs image optimization as it can save up to 18.6 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-37%

Potential reduce by 73.3 kB

  • Original 198.0 kB
  • After minification 197.8 kB
  • After compression 124.7 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 73.3 kB or 37% of the original size.

CSS Optimization

-73%

Potential reduce by 9.4 kB

  • Original 13.0 kB
  • After minification 12.8 kB
  • After compression 3.5 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. Cdict.net needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (61%)

Requests Now

83

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cdict.net

cdict.net

365 ms

css

css

62 ms

style-1449758895.css

style-1449758895.css

23 ms

jquery.min.js

jquery.min.js

42 ms

utils-1450800553.js

utils-1450800553.js

25 ms

adsbygoogle.js

adsbygoogle.js

4 ms

ad.js

ad.js

444 ms

show_ads.js

show_ads.js

6 ms

ysm_cdict.js

ysm_cdict.js

1022 ms

async-ads.js

async-ads.js

49 ms

analytics.js

analytics.js

48 ms

ca-pub-3077657785379479.js

ca-pub-3077657785379479.js

72 ms

zrt_lookup.html

zrt_lookup.html

123 ms

show_ads_impl.js

show_ads_impl.js

77 ms

all.js

all.js

304 ms

plusone.js

plusone.js

168 ms

collect

collect

81 ms

collect

collect

131 ms

ads

ads

140 ms

collect

collect

58 ms

ads

ads

134 ms

osd.js

osd.js

20 ms

pla

pla

29 ms

ads

ads

240 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

21 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

60 ms

fastbutton

fastbutton

120 ms

async-ads.js

async-ads.js

50 ms

abg.js

abg.js

34 ms

postmessageRelay

postmessageRelay

113 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

40 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

42 ms

167 ms

xd_arbiter.php

xd_arbiter.php

233 ms

xd_arbiter.php

xd_arbiter.php

442 ms

ad.html

ad.html

428 ms

p2

p2

18 ms

5171746271700867932

5171746271700867932

9 ms

s

s

4 ms

m_js_controller.js

m_js_controller.js

11 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

66 ms

x_button_blue2.png

x_button_blue2.png

28 ms

api.js

api.js

43 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

106 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

66 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

2 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

85 ms

jquery.min.js

jquery.min.js

15 ms

swfobject.js

swfobject.js

29 ms

RBlogo-sh2.png

RBlogo-sh2.png

384 ms

adcall.aspx

adcall.aspx

659 ms

sdk

sdk

464 ms

ucfad_min_0cb8265439c40d132a1a85ce8931b3f6e56ea649.js

ucfad_min_0cb8265439c40d132a1a85ce8931b3f6e56ea649.js

17 ms

ad_request

ad_request

829 ms

tp.html

tp.html

206 ms

pixel

pixel

16 ms

index.html

index.html

201 ms

rta.js

rta.js

16 ms

beacon.js

beacon.js

5 ms

439 ms

activeview

activeview

13 ms

rta3.aspx

rta3.aspx

422 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

10 ms

jquery.cookie.min.js

jquery.cookie.min.js

18 ms

ec.js

ec.js

226 ms

adsbygoogle.js

adsbygoogle.js

15 ms

ca-pub-4866695676912380.js

ca-pub-4866695676912380.js

26 ms

ads

ads

414 ms

etag

etag

634 ms

css

css

39 ms

nessie_icon_thin_arrow_short_white.png

nessie_icon_thin_arrow_short_white.png

25 ms

push

push

31 ms

d2s.html

d2s.html

630 ms

pixel

pixel

18 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

30 ms

activeview

activeview

16 ms

d2s_unify_v2.js

d2s_unify_v2.js

641 ms

etag

etag

419 ms

d2s4.css

d2s4.css

595 ms

yc.json

yc.json

639 ms

d2s_adlabel.png

d2s_adlabel.png

604 ms

wedding01.jpg

wedding01.jpg

47 ms

wedding02.jpg

wedding02.jpg

53 ms

wedding03.jpg

wedding03.jpg

65 ms

ui

ui

13 ms

xd_arbiter.php

xd_arbiter.php

137 ms

like.php

like.php

91 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

484 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

547 ms

Accessibility Review

cdict.net accessibility score

74

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

Best Practices

cdict.net best practices score

83

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

SEO Factors

cdict.net SEO score

100

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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

cdict.net

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