Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 66

    SEO

    Google-friendlier than
    25% of websites

dcfever.com

DCFever.com 香港最受歡迎數碼產品資訊互動平台

Page Load Speed

17.1 sec in total

First Response

589 ms

Resources Loaded

15 sec

Page Rendered

1.5 sec

dcfever.com screenshot

About Website

Welcome to dcfever.com homepage info - get ready to check DCFever best content for Hong Kong right away, or after learning these important things about dcfever.com

提供第一手的數碼相機、鏡頭、手機、平板電腦、耳機音響、電動車等數碼產品資訊及評測,以及促進用家之間的交流,鼓勵用家善用科技提升生活質素及攝影生活之新體驗,享受數碼產品帶來的各種樂趣。品牌包括 Sony, Nikon, Canon, Fujifilm, Apple, Samsung, Huawei(華為), HONOR, 小米(Xaomi)及Asus之評測。

Visit dcfever.com

Key Findings

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

Performance Metrics

dcfever.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value30.1 s

0/100

10%

TBT (Total Blocking Time)

Value31,270 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value45.6 s

0/100

10%

Network Requests Diagram

dcfever.com

589 ms

www.dcfever.com

2337 ms

global_20150918.css

1868 ms

grid_20150811.css

1863 ms

index_20150811.css

1469 ms

Our browser made a total of 166 requests to load all elements on the main page. We found that 43% of them (71 requests) were addressed to the original Dcfever.com, 29% (48 requests) were made to Cdn01.dcfever.com and 4% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (9.4 sec) belongs to the original domain Dcfever.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 698.2 kB (20%)

Content Size

3.5 MB

After Optimization

2.8 MB

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

HTML Optimization

-80%

Potential reduce by 71.7 kB

  • Original 90.0 kB
  • After minification 83.4 kB
  • After compression 18.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 71.7 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 76.0 kB

  • Original 2.6 MB
  • After minification 2.5 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. DCFever images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 359.8 kB

  • Original 648.8 kB
  • After minification 598.1 kB
  • After compression 289.0 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 359.8 kB or 55% of the original size.

CSS Optimization

-87%

Potential reduce by 190.7 kB

  • Original 218.4 kB
  • After minification 188.4 kB
  • After compression 27.7 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. Dcfever.com needs all CSS files to be minified and compressed as it can save up to 190.7 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (29%)

Requests Now

119

After Optimization

84

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

Accessibility Review

dcfever.com accessibility score

61

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

High

[aria-hidden="true"] elements contain focusable descendents

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

dcfever.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

dcfever.com SEO score

66

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

    JA

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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

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