Tools & Wizards About Us
28car.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

28car.com

易發車網 28car.com

Page Load Speed

10.5 sec in total

First Response

495 ms

Resources Loaded

9.8 sec

Page Rendered

278 ms

28car.com screenshot

About Website

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

Visit 28car.com

Key Findings

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

28car.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

28car.com

495 ms

lib.css

436 ms

lib.js

450 ms

srh.js

437 ms

new.js

440 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that all of those requests were addressed to 28car.com and no external sources were called. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain 28car.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 434.4 kB (61%)

Content Size

709.7 kB

After Optimization

275.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 28car.com main page is 709.7 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. 25% of websites need less resources to load. HTML takes 246.2 kB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 231.7 kB

  • Original 246.2 kB
  • After minification 170.2 kB
  • After compression 14.5 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 76.0 kB, which is 31% 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 231.7 kB or 94% of the original size.

Image Optimization

-6%

Potential reduce by 12.9 kB

  • Original 230.9 kB
  • After minification 218.1 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. 28 Car images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 182.2 kB

  • Original 223.0 kB
  • After minification 178.4 kB
  • After compression 40.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 182.2 kB or 82% of the original size.

CSS Optimization

-79%

Potential reduce by 7.6 kB

  • Original 9.6 kB
  • After minification 8.4 kB
  • After compression 2.0 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. 28car.com needs all CSS files to be minified and compressed as it can save up to 7.6 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (40%)

Requests Now

99

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

28car.com

28car.com

495 ms

lib.css

lib.css

436 ms

lib.js

lib.js

450 ms

srh.js

srh.js

437 ms

new.js

new.js

440 ms

col.js

col.js

440 ms

cmt.js

cmt.js

437 ms

adv_idl.js

adv_idl.js

865 ms

adv_idx.js

adv_idx.js

872 ms

adv_idx_prg.js

adv_idx_prg.js

869 ms

adv_idb.js

adv_idb.js

867 ms

adv_idb_prg.js

adv_idb_prg.js

919 ms

fr8_logo.gif

fr8_logo.gif

504 ms

fr_id_bn.gif

fr_id_bn.gif

842 ms

fr_ba.gif

fr_ba.gif

1334 ms

fr_ba_ha.gif

fr_ba_ha.gif

1340 ms

fr_ba_rg.gif

fr_ba_rg.gif

1445 ms

fr2_mu_ma.gif

fr2_mu_ma.gif

850 ms

fr_mu_ma_s.gif

fr_mu_ma_s.gif

852 ms

fr_mu_ma_c.gif

fr_mu_ma_c.gif

1269 ms

fr_mu_ma_b.gif

fr_mu_ma_b.gif

1279 ms

fr_mu_ma_n.gif

fr_mu_ma_n.gif

1285 ms

fr_mu_ma_p.gif

fr_mu_ma_p.gif

1703 ms

fr_mu_ma_o.gif

fr_mu_ma_o.gif

1710 ms

fr_mu_ma_a.gif

fr_mu_ma_a.gif

1718 ms

fr_mu_ma_e.gif

fr_mu_ma_e.gif

1766 ms

fr_mu_ad.gif

fr_mu_ad.gif

1774 ms

fr_mu_dt.gif

fr_mu_dt.gif

1878 ms

fr_mu_nw.gif

fr_mu_nw.gif

2135 ms

fr_mu_co.gif

fr_mu_co.gif

2144 ms

5040.frt.jpg

5040.frt.jpg

2153 ms

fr_mu_rg.gif

fr_mu_rg.gif

2200 ms

fr_mu_cm.gif

fr_mu_cm.gif

2207 ms

fr_mu_dn.gif

fr_mu_dn.gif

2962 ms

fr_mu_ct.gif

fr_mu_ct.gif

2566 ms

fr2_ct_h_s.gif

fr2_ct_h_s.gif

2579 ms

fr2_ct_hb_s.gif

fr2_ct_hb_s.gif

2589 ms

fr_ct_h_mr.gif

fr_ct_h_mr.gif

2635 ms

fr_ct_h_sh.gif

fr_ct_h_sh.gif

2641 ms

fr_ct_c_tl.gif

fr_ct_c_tl.gif

3004 ms

fr_ct_c_tr.gif

fr_ct_c_tr.gif

3014 ms

fr_ct_c_bl.gif

fr_ct_c_bl.gif

3022 ms

fr_ct_c_br.gif

fr_ct_c_br.gif

3065 ms

fr_ct_b_tl.gif

fr_ct_b_tl.gif

2671 ms

fr_ct_b_tf.gif

fr_ct_b_tf.gif

2992 ms

fr_ct_b_tr.gif

fr_ct_b_tr.gif

3031 ms

index.html

index.html

3800 ms

pic_yes.gif

pic_yes.gif

2964 ms

fr_ct_b_tn.gif

fr_ct_b_tn.gif

2985 ms

1163242_m.jpg

1163242_m.jpg

2665 ms

1155718_m.jpg

1155718_m.jpg

2983 ms

1155710_m.jpg

1155710_m.jpg

3021 ms

1153389_m.jpg

1153389_m.jpg

2629 ms

1155754_m.jpg

1155754_m.jpg

2664 ms

directasia_mini.gif

directasia_mini.gif

2884 ms

fr2_ct_h_c.gif

fr2_ct_h_c.gif

2936 ms

fr2_ct_hb_c.gif

fr2_ct_hb_c.gif

2971 ms

135052_m.jpg

135052_m.jpg

3841 ms

148316_m.jpg

148316_m.jpg

3627 ms

148809_m.jpg

148809_m.jpg

4034 ms

147904_m.jpg

147904_m.jpg

2965 ms

148547_m.jpg

148547_m.jpg

3890 ms

145722_m.jpg

145722_m.jpg

3884 ms

136097_m.jpg

136097_m.jpg

6237 ms

136386_m.jpg

136386_m.jpg

3582 ms

134235_m.jpg

134235_m.jpg

3620 ms

144389_m.jpg

144389_m.jpg

3936 ms

fr2_ct_h_b.gif

fr2_ct_h_b.gif

3890 ms

fr2_ct_hb_b.gif

fr2_ct_hb_b.gif

3957 ms

fr2_ct_h_n.gif

fr2_ct_h_n.gif

3611 ms

fr2_ct_hb_n.gif

fr2_ct_hb_n.gif

3618 ms

fr2_ct_h_o.gif

fr2_ct_h_o.gif

3936 ms

fr2_ct_hb_o.gif

fr2_ct_hb_o.gif

3891 ms

pic_no.gif

pic_no.gif

3958 ms

ses_cnt.php

ses_cnt.php

3666 ms

fr2_mb_em.gif

fr2_mb_em.gif

3628 ms

fr2_mb_ps.gif

fr2_mb_ps.gif

3944 ms

fr2_mb_li.gif

fr2_mb_li.gif

3937 ms

fr2_mb_sp.gif

fr2_mb_sp.gif

3958 ms

fr2_mb_rg.gif

fr2_mb_rg.gif

3986 ms

fr2_mb_gp.gif

fr2_mb_gp.gif

3671 ms

fr2_mb_us.gif

fr2_mb_us.gif

3955 ms

pingan_logo.gif

pingan_logo.gif

3933 ms

fr_adv_idx_bg.gif

fr_adv_idx_bg.gif

3957 ms

fr_mu_ma_bg.gif

fr_mu_ma_bg.gif

3987 ms

fr_mu_bg.gif

fr_mu_bg.gif

3672 ms

fr_ct_h.gif

fr_ct_h.gif

3959 ms

fr_ct_c_tc.gif

fr_ct_c_tc.gif

3937 ms

fr_ct_c_ml.gif

fr_ct_c_ml.gif

3955 ms

fr_ct_c_mr.gif

fr_ct_c_mr.gif

3761 ms

fr_ct_c_bc.gif

fr_ct_c_bc.gif

3671 ms

817_d.gif

817_d.gif

4533 ms

fr_ct_c_mc.gif

fr_ct_c_mc.gif

3960 ms

confused__1_.PNG

confused__1_.PNG

3663 ms

s4__1_.png

s4__1_.png

3080 ms

surprise__1_.PNG

surprise__1_.PNG

3045 ms

s3__1_.png

s3__1_.png

3139 ms

startle__1_.PNG

startle__1_.PNG

3046 ms

s2__2_.png

s2__2_.png

3062 ms

shout__1_.PNG

shout__1_.PNG

3054 ms

Accessibility Review

28car.com accessibility score

52

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.

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

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

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

28car.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

28car.com SEO score

85

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

Image elements do not have [alt] attributes

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    BIG5

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 28car.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 28car.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

28car.com

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