Tools & Wizards About Us
lanjinger.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

lanjinger.com

蓝鲸财经-财经信息服务平台

Page Load Speed

8.4 sec in total

First Response

788 ms

Resources Loaded

7.2 sec

Page Rendered

445 ms

lanjinger.com screenshot

About Website

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

有国内多名资深媒体主编担纲，力推独家快速深度财经资讯。行业涉及传媒、TMT、基金、银行、汽车、互联网金融、教育、健康等最为活跃的领域。

Visit lanjinger.com

Key Findings

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

Performance Metrics

lanjinger.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

lanjinger.com

788 ms

lanjinger.com

1514 ms

nc.js

605 ms

app.8dcd1ff.css

1402 ms

app.3a7f830.css

1823 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 10% of them (4 requests) were addressed to the original Lanjinger.com, 45% (18 requests) were made to Img.lanjinger.com and 35% (14 requests) were made to Static.lanjinger.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Img.lanjinger.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 213.1 kB (8%)

Content Size

2.7 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-82%

Potential reduce by 122.9 kB

  • Original 150.7 kB
  • After minification 149.3 kB
  • After compression 27.8 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 122.9 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 90.2 kB

  • Original 2.1 MB
  • After minification 2.0 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. Lanjinger images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 66 B

  • Original 488.2 kB
  • After minification 488.2 kB
  • After compression 488.1 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.

Requests Breakdown

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

Requests Now

37

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lanjinger. 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

lanjinger.com

lanjinger.com

788 ms

lanjinger.com

lanjinger.com

1514 ms

nc.js

nc.js

605 ms

app.8dcd1ff.css

app.8dcd1ff.css

1402 ms

app.3a7f830.css

app.3a7f830.css

1823 ms

index.5d3d64b.css

index.5d3d64b.css

2207 ms

41121f5.js

41121f5.js

2158 ms

5e1c14b.js

5e1c14b.js

2156 ms

6e7544f.js

6e7544f.js

2159 ms

dcb424a.js

dcb424a.js

2710 ms

07f94a8.js

07f94a8.js

2194 ms

hm.js

hm.js

1072 ms

1719538218409_fynzncpxtiinj.jpeg@!thumb800

1719538218409_fynzncpxtiinj.jpeg@!thumb800

1282 ms

1719538191345_njaxsvqpittes.jpeg@!thumb800

1719538191345_njaxsvqpittes.jpeg@!thumb800

2207 ms

092900_ztztlgufhxjlc.jpeg@!thumb800

092900_ztztlgufhxjlc.jpeg@!thumb800

2091 ms

1719538077330_wtfmfqqwuzmlq.jpeg@!thumb800

1719538077330_wtfmfqqwuzmlq.jpeg@!thumb800

1676 ms

1719538053065_npajeellnwbtk.jpeg@!thumb800

1719538053065_npajeellnwbtk.jpeg@!thumb800

1675 ms

1719565521491_tamcmqqpwzugm.jpeg@!thumb800

1719565521491_tamcmqqpwzugm.jpeg@!thumb800

1905 ms

1719388599061_gdxcxpfyvrkrb.jpeg@!thumb800

1719388599061_gdxcxpfyvrkrb.jpeg@!thumb800

2031 ms

163841_xgyguruahoscy.png@!thumb700

163841_xgyguruahoscy.png@!thumb700

2745 ms

144748_lwjizhhqpfbtm.png@!thumb700

144748_lwjizhhqpfbtm.png@!thumb700

2128 ms

135110_mtqckasmnefsg.png@!thumb700

135110_mtqckasmnefsg.png@!thumb700

2607 ms

120255_loywhvszanykg.jpeg@!thumb700

120255_loywhvszanykg.jpeg@!thumb700

2338 ms

1718703714986_zxqsuspbszrgt.jpeg@!thumb700

1718703714986_zxqsuspbszrgt.jpeg@!thumb700

2344 ms

lj-logo-2021.524fe32.png

lj-logo-2021.524fe32.png

227 ms

icon-lj-small.2571d81.png

icon-lj-small.2571d81.png

214 ms

report-cn.8718731.png

report-cn.8718731.png

280 ms

report-sh.3c07ecd.png

report-sh.3c07ecd.png

337 ms

iconfont.b061570.woff

iconfont.b061570.woff

462 ms

channels

channels

300 ms

list

list

589 ms

img-placeholder.bbba133.png

img-placeholder.bbba133.png

267 ms

1719563703098_ittkngnryjdbd.jpeg

1719563703098_ittkngnryjdbd.jpeg

1372 ms

hm.gif

hm.gif

325 ms

17195956448456500_a430xH.jpg

17195956448456500_a430xH.jpg

999 ms

194006_lxokbptvhxcgw.jpeg@!thumb430

194006_lxokbptvhxcgw.jpeg@!thumb430

1380 ms

120300_dtjvzrhjrcxnz.jpeg@!thumb430

120300_dtjvzrhjrcxnz.jpeg@!thumb430

1390 ms

212035_khxinxxcuhtic.jpeg@!thumb430

212035_khxinxxcuhtic.jpeg@!thumb430

1337 ms

162333_hbxihpcplekpo.jpeg@!thumb700

162333_hbxihpcplekpo.jpeg@!thumb700

1409 ms

200051_xpbnfwunxugkj.jpeg@!thumb700

200051_xpbnfwunxugkj.jpeg@!thumb700

1646 ms

Accessibility Review

lanjinger.com accessibility score

71

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

lanjinger.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

lanjinger.com SEO score

89

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

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

lanjinger.com

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