Tools & Wizards About Us
discuss.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

discuss.com

香港討論區 Discuss.com.hk - 香討．香港 No.1

Page Load Speed

7.6 sec in total

First Response

688 ms

Resources Loaded

6.7 sec

Page Rendered

285 ms

discuss.com screenshot

About Website

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

香港討論區（香討）為全港5大最高瀏覽率的網站之一，主要討論涵蓋新聞時事、娛樂、飲食、潮流、各行各業、地產、財經、股票、汽車、戀愛婚姻、電腦手機、運動體育、興趣、好去處、著數優惠等話題，隨時隨地分享您的生活話題討論及緊貼網民熱話！香港討論區（香討）每月單一訪客人數過千萬，擁有超過550萬位來自不同階層、背景的會員。 香港討論區

Visit discuss.com

Key Findings

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

discuss.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value6,810 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.076

95/100

15%

TTI (Time to Interactive)

Value26.6 s

0/100

10%

Network Requests Diagram

discuss.com

688 ms

www.discuss.com.hk

713 ms

index_rev1308.js

434 ms

common_rev09.js

439 ms

menu.js

439 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Discuss.com, 55% (88 requests) were made to N2.hk and 20% (33 requests) were made to Discuss.com.hk. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source N2.hk.

Page Optimization Overview & Recommendations

Page size can be reduced by 785.0 kB (32%)

Content Size

2.4 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Discuss.com main page is 2.4 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 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 80.4 kB

  • Original 101.8 kB
  • After minification 91.5 kB
  • After compression 21.4 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 80.4 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 101.9 kB

  • Original 1.5 MB
  • After minification 1.4 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. Discuss images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 564.4 kB

  • Original 774.3 kB
  • After minification 561.3 kB
  • After compression 209.9 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 564.4 kB or 73% of the original size.

CSS Optimization

-82%

Potential reduce by 38.3 kB

  • Original 46.9 kB
  • After minification 39.1 kB
  • After compression 8.6 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. Discuss.com needs all CSS files to be minified and compressed as it can save up to 38.3 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

157

After Optimization

82

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

discuss.com

discuss.com

688 ms

www.discuss.com.hk

www.discuss.com.hk

713 ms

index_rev1308.js

index_rev1308.js

434 ms

common_rev09.js

common_rev09.js

439 ms

menu.js

menu.js

439 ms

crystal.js

crystal.js

877 ms

nw_adserv.js

nw_adserv.js

657 ms

jquery-1.10.2.modified.js

jquery-1.10.2.modified.js

1109 ms

promo2013a.js

promo2013a.js

658 ms

jquery.fancybox.js

jquery.fancybox.js

440 ms

jquery.fancybox.css

jquery.fancybox.css

439 ms

idle_check.js

idle_check.js

650 ms

rev_style_revamp_1308a4.css

rev_style_revamp_1308a4.css

653 ms

searchbox_1308.css

searchbox_1308.css

655 ms

enlargefonts.css

enlargefonts.css

657 ms

lview

lview

906 ms

rev_style_revamp_1308b1.css

rev_style_revamp_1308b1.css

656 ms

adsbygoogle.js

adsbygoogle.js

6 ms

lview

lview

895 ms

show_ads.js

show_ads.js

3 ms

ping_ud.js

ping_ud.js

662 ms

discuss_map_obj.js

discuss_map_obj.js

662 ms

hotTopicCardv4.js

hotTopicCardv4.js

671 ms

hotTopicCard_d.css

hotTopicCard_d.css

670 ms

lview

lview

703 ms

conversion.js

conversion.js

13 ms

logo.png

logo.png

252 ms

icon_price.png

icon_price.png

433 ms

icon_jetso.png

icon_jetso.png

436 ms

icon_car.png

icon_car.png

439 ms

icon_mytour.png

icon_mytour.png

439 ms

icon_mammydaddy.png

icon_mammydaddy.png

439 ms

icon_adhere.png

icon_adhere.png

442 ms

search_arrow.png

search_arrow.png

644 ms

d_btn_search.png

d_btn_search.png

652 ms

83.gif

83.gif

654 ms

20160317_25631124jpg

20160317_25631124jpg

1088 ms

20160316_25628739jpg

20160316_25628739jpg

1540 ms

youtube_thumb.png

youtube_thumb.png

1072 ms

i_150.jpg

i_150.jpg

868 ms

i_838.jpg

i_838.jpg

869 ms

i_149.jpg

i_149.jpg

871 ms

i_478.jpg

i_478.jpg

1084 ms

i_482.jpg

i_482.jpg

1086 ms

i_483.jpg

i_483.jpg

1090 ms

i_72.jpg

i_72.jpg

1287 ms

i_1050.jpg

i_1050.jpg

1300 ms

i_484.jpg

i_484.jpg

1302 ms

i_481.jpg

i_481.jpg

1305 ms

i_154.jpg

i_154.jpg

1306 ms

i_157.jpg

i_157.jpg

1499 ms

gid-thumb-wp8.jpg

gid-thumb-wp8.jpg

1515 ms

i_78.jpg

i_78.jpg

1517 ms

i_153.jpg

i_153.jpg

1522 ms

i_73.jpg

i_73.jpg

1522 ms

i_873.jpg

i_873.jpg

1713 ms

i_480.jpg

i_480.jpg

1731 ms

i_116.jpg

i_116.jpg

1733 ms

i_103.jpg

i_103.jpg

1739 ms

i_76.jpg

i_76.jpg

1739 ms

i_479.jpg

i_479.jpg

1756 ms

discuss_media_award_236x66.png

discuss_media_award_236x66.png

247 ms

discuss_marketing_award_236x66.png

discuss_marketing_award_236x66.png

246 ms

discuss_spark_award_236x66.png

discuss_spark_award_236x66.png

247 ms

hk_top_service_brand_logo.png

hk_top_service_brand_logo.png

244 ms

caring_company_logo.png

caring_company_logo.png

244 ms

beacon.js

beacon.js

10 ms

atrk.js

atrk.js

72 ms

yna05_prod.html

yna05_prod.html

226 ms

live-box-title.png

live-box-title.png

410 ms

live-box-more-arrow.png

live-box-more-arrow.png

408 ms

grid_view_image_gid_103_wide.png

grid_view_image_gid_103_wide.png

410 ms

black-60.png

black-60.png

413 ms

grid_view_image_gid_482_wide.png

grid_view_image_gid_482_wide.png

411 ms

grid_view_image_gid_838_wide.png

grid_view_image_gid_838_wide.png

456 ms

grid_view_image_gid_150_wide.png

grid_view_image_gid_150_wide.png

623 ms

grid_view_image_gid_478_wide.png

grid_view_image_gid_478_wide.png

624 ms

grid_view_image_gid_1050_wide.png

grid_view_image_gid_1050_wide.png

626 ms

grid_view_image_gid_480_wide.png

grid_view_image_gid_480_wide.png

626 ms

like.php

like.php

74 ms

ca-pub-5281467099397116.js

ca-pub-5281467099397116.js

67 ms

zrt_lookup.html

zrt_lookup.html

65 ms

show_ads_impl.js

show_ads_impl.js

65 ms

atrk.gif

atrk.gif

134 ms

test.png

test.png

148 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

80 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

74 ms

ads

ads

231 ms

ads

ads

161 ms

osd.js

osd.js

11 ms

ga.js

ga.js

17 ms

__utm.gif

__utm.gif

20 ms

portalbox_bg.gif

portalbox_bg.gif

426 ms

section_group_row3.html

section_group_row3.html

1684 ms

gemini.js

gemini.js

86 ms

collect

collect

140 ms

g-d-min.js

g-d-min.js

5 ms

ssi

ssi

184 ms

54 ms

ga-audiences

ga-audiences

38 ms

13721620165487105979

13721620165487105979

46 ms

abg.js

abg.js

48 ms

m_js_controller.js

m_js_controller.js

57 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

35 ms

i_156.jpg

i_156.jpg

1522 ms

i_1101.jpg

i_1101.jpg

1520 ms

i_158.jpg

i_158.jpg

1524 ms

i_155.jpg

i_155.jpg

1524 ms

i_997.jpg

i_997.jpg

1544 ms

i_89.jpg

i_89.jpg

1705 ms

s

s

23 ms

x_button_blue2.png

x_button_blue2.png

25 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

4 ms

cb-1452672464681-3718.plain

cb-1452672464681-3718.plain

11 ms

1447351354850-3003.jpg

1447351354850-3003.jpg

7 ms

syndication.png

syndication.png

6 ms

i_151.jpg

i_151.jpg

1524 ms

i_152.jpg

i_152.jpg

1518 ms

slogan.png

slogan.png

1525 ms

1cd04e6450db3063b60803027a689c9f_200

1cd04e6450db3063b60803027a689c9f_200

1526 ms

footer_app.png

footer_app.png

1334 ms

spacer.gif

spacer.gif

1491 ms

spacer.gif

spacer.gif

1514 ms

mycircle_icon.png

mycircle_icon.png

1315 ms

service_icon.png

service_icon.png

1311 ms

top_nav_icons.png

top_nav_icons.png

1309 ms

fbcirclebtn.png

fbcirclebtn.png

1332 ms

160317_e93d485c16d2f5929de22b7349d46fc1

160317_e93d485c16d2f5929de22b7349d46fc1

1912 ms

reply.png

reply.png

1315 ms

view.png

view.png

1302 ms

20160317_25628671jpg

20160317_25628671jpg

1962 ms

160317_dab1fa4a6790b0cd38426442f4f493bf

160317_dab1fa4a6790b0cd38426442f4f493bf

1744 ms

20160317_25630614jpg

20160317_25630614jpg

1554 ms

160127_d682caef8a5b459a7f708485008020e7

160127_d682caef8a5b459a7f708485008020e7

2221 ms

160317_2fa46e2d91f32339e3602f1f3ce92640

160317_2fa46e2d91f32339e3602f1f3ce92640

2167 ms

tab_on.gif

tab_on.gif

1563 ms

tab_off.gif

tab_off.gif

1693 ms

star_d.png

star_d.png

1743 ms

shortcut_icon.png

shortcut_icon.png

1763 ms

qmark_icon.png

qmark_icon.png

1716 ms

d_news.png

d_news.png

1749 ms

gid_dots_news.png

gid_dots_news.png

1751 ms

d_ladies.png

d_ladies.png

1781 ms

gid_dots_ladies.png

gid_dots_ladies.png

1904 ms

d_sports.png

d_sports.png

1940 ms

gid_dots_sports.png

gid_dots_sports.png

1773 ms

d_entertainment.png

d_entertainment.png

1793 ms

gid_dots_entertainment.png

gid_dots_entertainment.png

1908 ms

d_digital.png

d_digital.png

1941 ms

gid_dots_digital.png

gid_dots_digital.png

1958 ms

d_leisure.png

d_leisure.png

1942 ms

gid_dots_leisure.png

gid_dots_leisure.png

1794 ms

d_life.png

d_life.png

1796 ms

gid_dots_life.png

gid_dots_life.png

1906 ms

d_culture.png

d_culture.png

1941 ms

gid_dots_culture.png

gid_dots_culture.png

1956 ms

d_others.png

d_others.png

1938 ms

gid_dots_others.png

gid_dots_others.png

1796 ms

d_restricted.png

d_restricted.png

1799 ms

footer_bg.png

footer_bg.png

1904 ms

banner_price.png

banner_price.png

1941 ms

Accessibility Review

discuss.com accessibility score

80

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

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

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

discuss.com best practices score

67

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

discuss.com SEO score

92

Search Engine Optimization Advices

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    BIG5

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discuss.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Discuss.com main page’s claimed encoding is big5. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

discuss.com

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