Tools & Wizards About Us
cn.engadget.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

cn.engadget.com

科技 - Yahoo新聞

Page Load Speed

1.8 sec in total

First Response

41 ms

Resources Loaded

1.2 sec

Page Rendered

544 ms

cn.engadget.com screenshot

About Website

Click here to check amazing Cn Engadget content for United States. Otherwise, check out these important facts you probably never knew about cn.engadget.com

最新科技新聞、產品評測，消費性電子產品消息不斷更新，豐富分析及評論，盡在Yahoo香港新聞

Visit cn.engadget.com

Key Findings

We analyzed Cn.engadget.com page load time and found that the first response time was 41 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

cn.engadget.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

cn.engadget.com

41 ms

cn.engadget.com

75 ms

tech

916 ms

custom.9ab971ba.css

17 ms

bundle.24a8225d.css

25 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Cn.engadget.com, 86% (42 requests) were made to S.yimg.com and 4% (2 requests) were made to Consent.cmp.oath.com. The less responsive or slowest element that took the longest time to load (916 ms) relates to the external source Hk.news.yahoo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 848.9 kB (40%)

Content Size

2.1 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cn.engadget.com main page is 2.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. 70% of websites need less resources to load. HTML takes 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 839.3 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 485.3 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 839.3 kB or 63% of the original size.

Image Optimization

-3%

Potential reduce by 4.7 kB

  • Original 146.7 kB
  • After minification 142.0 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. Cn Engadget images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.8 kB

  • Original 623.6 kB
  • After minification 623.6 kB
  • After compression 619.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 1.1 kB

  • Original 48.3 kB
  • After minification 48.3 kB
  • After compression 47.2 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. Cn.engadget.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (53%)

Requests Now

43

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cn.engadget.com

cn.engadget.com

41 ms

cn.engadget.com

cn.engadget.com

75 ms

tech

tech

916 ms

custom.9ab971ba.css

custom.9ab971ba.css

17 ms

bundle.24a8225d.css

bundle.24a8225d.css

25 ms

atomic-desktop-ltr.65027848.css

atomic-desktop-ltr.65027848.css

27 ms

atomic-context.7fb77b06.css

atomic-context.7fb77b06.css

36 ms

patch.b1028fb0.css

patch.b1028fb0.css

38 ms

theme.2f876e26.css

theme.2f876e26.css

37 ms

fuji-rollup.min.901f71a2.css

fuji-rollup.min.901f71a2.css

38 ms

content-canvas.e7f4dd4b.css

content-canvas.e7f4dd4b.css

38 ms

slick.50a987e9.css

slick.50a987e9.css

39 ms

zh.js

zh.js

43 ms

rapid3.js

rapid3.js

45 ms

consent.js

consent.js

46 ms

benji-2.1.29.js

benji-2.1.29.js

50 ms

cmpStub.min.js

cmpStub.min.js

61 ms

cmp.js

cmp.js

134 ms

cerebro_min.js

cerebro_min.js

99 ms

yahoo_news_zh-Hant-HK_h_p_newsv2.png

yahoo_news_zh-Hant-HK_h_p_newsv2.png

68 ms

yahoo_news_zh-Hant-HK_h_w_newsv2.png

yahoo_news_zh-Hant-HK_h_w_newsv2.png

27 ms

header_1x-1479864976616.min.png

header_1x-1479864976616.min.png

29 ms

60fc8400-0c85-11ef-96ff-4ab17fea01d4

60fc8400-0c85-11ef-96ff-4ab17fea01d4

29 ms

07183d80-05fc-11ed-a2a7-aa099db79729

07183d80-05fc-11ed-a2a7-aa099db79729

32 ms

7b1a1970-0d1f-11ef-bf13-7d5964ef6e35

7b1a1970-0d1f-11ef-bf13-7d5964ef6e35

30 ms

747757a0-0d14-11ef-bffe-dfcefcb57d74

747757a0-0d14-11ef-bffe-dfcefcb57d74

35 ms

07183d80-05fc-11ed-a2a7-aa099db79729.cf.jpg

07183d80-05fc-11ed-a2a7-aa099db79729.cf.jpg

32 ms

http%3A%2F%2Fcdn.taboola.com%2Flibtrc%2Fstatic%2Fthumbnails%2Fb89a85439fddca316f8dd1f7a9200fc2.jpg.cf.jpg

http%3A%2F%2Fcdn.taboola.com%2Flibtrc%2Fstatic%2Fthumbnails%2Fb89a85439fddca316f8dd1f7a9200fc2.jpg.cf.jpg

34 ms

7b1a1970-0d1f-11ef-bf13-7d5964ef6e35.cf.jpg

7b1a1970-0d1f-11ef-bf13-7d5964ef6e35.cf.jpg

34 ms

spaceball.gif

spaceball.gif

32 ms

Yahoo_Sans-Regular.woff

Yahoo_Sans-Regular.woff

33 ms

Yahoo_Sans-Semibold.woff

Yahoo_Sans-Semibold.woff

33 ms

Yahoo_Sans-Bold.woff

Yahoo_Sans-Bold.woff

34 ms

https%3A%2F%2Fcdn.taboola.com%2Flibtrc%2Fstatic%2Fthumbnails%2Fa7c4bac3431d5026f04bcbaf8398f24d.gif

https%3A%2F%2Fcdn.taboola.com%2Flibtrc%2Fstatic%2Fthumbnails%2Fa7c4bac3431d5026f04bcbaf8398f24d.gif

114 ms

47dd68e0-0b3c-11ee-afdd-aae806570dd5

47dd68e0-0b3c-11ee-afdd-aae806570dd5

14 ms

215eca20-efb6-11ed-ae75-4df81593dd06

215eca20-efb6-11ed-ae75-4df81593dd06

17 ms

9fd51471-e58b-11ed-b7bf-8a0edd46901b

9fd51471-e58b-11ed-b7bf-8a0edd46901b

17 ms

e2f258c0-d82b-11ed-bb3b-e046f5d4f1b9

e2f258c0-d82b-11ed-bb3b-e046f5d4f1b9

15 ms

010411d0-cdfc-11ed-be77-1fddc6a2c201

010411d0-cdfc-11ed-be77-1fddc6a2c201

15 ms

privacy-choice-control.png

privacy-choice-control.png

13 ms

yaft-0.3.10.min.js

yaft-0.3.10.min.js

120 ms

yaft-plugin-aftnoad-0.1.3.min.js

yaft-plugin-aftnoad-0.1.3.min.js

122 ms

lodash.cc533c0b072c78f9b0b2.min.js

lodash.cc533c0b072c78f9b0b2.min.js

123 ms

react.ecef153bbb3f02aeccc9.min.js

react.ecef153bbb3f02aeccc9.min.js

128 ms

core.cf98e53bc3eef9dcbdb2.min.js

core.cf98e53bc3eef9dcbdb2.min.js

127 ms

vendor.6c4a63ca02abbb31795a.min.js

vendor.6c4a63ca02abbb31795a.min.js

134 ms

common.1967dbdfc82b60dabd57.min.js

common.1967dbdfc82b60dabd57.min.js

134 ms

main.f224eb560612e6047bbd.min.js

main.f224eb560612e6047bbd.min.js

146 ms

perf-vitals_3.2.0.js

perf-vitals_3.2.0.js

5 ms

Accessibility Review

cn.engadget.com accessibility score

82

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

cn.engadget.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

cn.engadget.com 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

    JA

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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

cn.engadget.com

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