Tools & Wizards About Us
leju.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

leju.com

乐居_连接美好生活，创造美好未来

Page Load Speed

35.3 sec in total

First Response

5.7 sec

Resources Loaded

28.7 sec

Page Rendered

853 ms

leju.com screenshot

About Website

Welcome to leju.com homepage info - get ready to check Leju best content for China right away, or after learning these important things about leju.com

乐居目前已覆盖全国超过380+个城市，与全国主流媒体平台、媒介机构展开全面深度合作。乐居把握移动互联网和大数据的时代脉搏，协同融合为合作伙伴赋能；成为全国开发商、经纪公司及家居企业，品牌传播和市场营销的重要合作伙伴。

Visit leju.com

Key Findings

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

Performance Metrics

leju.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.206

60/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

www.leju.com

5745 ms

base.css

2656 ms

widget.css

2659 ms

fsqgz.shtml

6066 ms

1362bf8ced9c01eb0cdd7d463f8_p24_mk24.jpg

1972 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Leju.com, 58% (14 requests) were made to Cdn.leju.com and 8% (2 requests) were made to Src.house.sina.com.cn. The less responsive or slowest element that took the longest time to load (10.5 sec) relates to the external source Cdn.leju.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 333.7 kB (44%)

Content Size

756.3 kB

After Optimization

422.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Leju.com main page is 756.3 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. 35% of websites need less resources to load. Images take 358.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 174.8 kB

  • Original 215.5 kB
  • After minification 191.6 kB
  • After compression 40.7 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 23.9 kB, which is 11% 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 174.8 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 2.4 kB

  • Original 358.9 kB
  • After minification 356.5 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. Leju images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 6.4 kB

  • Original 9.2 kB
  • After minification 9.2 kB
  • After compression 2.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 6.4 kB or 70% of the original size.

CSS Optimization

-87%

Potential reduce by 150.1 kB

  • Original 172.7 kB
  • After minification 172.2 kB
  • After compression 22.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. Leju.com needs all CSS files to be minified and compressed as it can save up to 150.1 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (27%)

Requests Now

22

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.leju.com

www.leju.com

5745 ms

base.css

base.css

2656 ms

widget.css

widget.css

2659 ms

fsqgz.shtml

fsqgz.shtml

6066 ms

1362bf8ced9c01eb0cdd7d463f8_p24_mk24.jpg

1362bf8ced9c01eb0cdd7d463f8_p24_mk24.jpg

1972 ms

54ea08d304c564ac7b359cd9ef76b425_cm262X57.png

54ea08d304c564ac7b359cd9ef76b425_cm262X57.png

6476 ms

LAB.js

LAB.js

894 ms

gather.pc.source.js

gather.pc.source.js

2181 ms

helper.loader.js

helper.loader.js

947 ms

widget1452567977953.png

widget1452567977953.png

211 ms

logo.png

logo.png

209 ms

dicon_09.png

dicon_09.png

792 ms

repeat.png

repeat.png

610 ms

y_tab_i.png

y_tab_i.png

468 ms

newsBg.jpg

newsBg.jpg

790 ms

LET_page.js

LET_page.js

10529 ms

PG_5088E3656E1259

PG_5088E3656E1259

2697 ms

index.js

index.js

6 ms

tongji.leju.com

tongji.leju.com

2498 ms

push.js

push.js

1823 ms

5047cec99a11b6d57a2ee6acd7a_p24_mk24.png

5047cec99a11b6d57a2ee6acd7a_p24_mk24.png

3113 ms

jQuery1.8.2.js

jQuery1.8.2.js

5 ms

a00616425baa042e4fe2363de0f_p24_mk24.png

a00616425baa042e4fe2363de0f_p24_mk24.png

2856 ms

sAdv02.png

sAdv02.png

625 ms

Accessibility Review

leju.com accessibility score

57

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

leju.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

leju.com SEO score

82

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

leju.com

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