Tools & Wizards About Us
jpm.cn screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

jpm.cn

金评媒 - 互联网有温度的媒体

Page Load Speed

6 sec in total

First Response

864 ms

Resources Loaded

4.9 sec

Page Rendered

267 ms

jpm.cn screenshot

About Website

Welcome to jpm.cn homepage info - get ready to check Jpm best content for China right away, or after learning these important things about jpm.cn

JPM.cn（金评媒）是专注于互联网金融的媒体网站，致力于打造中国该领域最具影响力媒体，成为中国互联网金融第一价值资讯平台。

Visit jpm.cn

Key Findings

We analyzed Jpm.cn page load time and found that the first response time was 864 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

jpm.cn performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.225

55/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

www.jpm.cn

864 ms

base.css

941 ms

jpmcommon.css

935 ms

jpmstyle.css

942 ms

Login_Page.css

952 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 11% of them (7 requests) were addressed to the original Jpm.cn, 68% (43 requests) were made to Static.jpm.cn and 11% (7 requests) were made to Img.jpm.cn. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Img.jpm.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 168.6 kB (14%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jpm.cn main page is 1.2 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 81.4 kB

  • Original 93.6 kB
  • After minification 44.5 kB
  • After compression 12.2 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 49.0 kB, which is 52% 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 81.4 kB or 87% of the original size.

Image Optimization

-7%

Potential reduce by 74.5 kB

  • Original 1.1 MB
  • After minification 986.3 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. Jpm images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 7.9 kB

  • Original 67.7 kB
  • After minification 67.7 kB
  • After compression 59.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 7.9 kB or 12% of the original size.

CSS Optimization

-24%

Potential reduce by 4.8 kB

  • Original 20.2 kB
  • After minification 20.2 kB
  • After compression 15.3 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. Jpm.cn needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (38%)

Requests Now

56

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.jpm.cn

www.jpm.cn

864 ms

base.css

base.css

941 ms

jpmcommon.css

jpmcommon.css

935 ms

jpmstyle.css

jpmstyle.css

942 ms

Login_Page.css

Login_Page.css

952 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

1189 ms

jpmIndex.js

jpmIndex.js

971 ms

tools.js

tools.js

1203 ms

new2_box.js

new2_box.js

1202 ms

Login_Page.js

Login_Page.js

1250 ms

popWin2.js

popWin2.js

1219 ms

SuperSlide.2.1.js

SuperSlide.2.1.js

1250 ms

jpm.js

jpm.js

1464 ms

zzsc.js

zzsc.js

1459 ms

koala.min.1.5.js

koala.min.1.5.js

1465 ms

hm.js

hm.js

973 ms

m_656d95daa2d5b.jpg

m_656d95daa2d5b.jpg

851 ms

25_avatar_middle.jpg

25_avatar_middle.jpg

612 ms

84_avatar_middle.jpg

84_avatar_middle.jpg

613 ms

68_avatar_middle.jpg

68_avatar_middle.jpg

622 ms

jpm_03.png

jpm_03.png

231 ms

futurecar.png

futurecar.png

226 ms

cw_logo.png

cw_logo.png

224 ms

fm.jpg

fm.jpg

229 ms

yibi.jpg

yibi.jpg

498 ms

app3x.png

app3x.png

214 ms

icon_03.png

icon_03.png

437 ms

icon_01.png

icon_01.png

448 ms

pc_weixin.jpg

pc_weixin.jpg

450 ms

jpmlogo.png

jpmlogo.png

475 ms

index_07.png

index_07.png

464 ms

jpm_search.png

jpm_search.png

650 ms

activelist_wxcode.png

activelist_wxcode.png

1043 ms

p2p_t.jpg

p2p_t.jpg

800 ms

supply_chain_finance_t.jpg

supply_chain_finance_t.jpg

804 ms

consumer_finance2018_t.jpg

consumer_finance2018_t.jpg

784 ms

zhifu_t.jpg

zhifu_t.jpg

803 ms

bitebi_t.jpg

bitebi_t.jpg

939 ms

unicorn_t.jpg

unicorn_t.jpg

1116 ms

zhongchou_t.jpg

zhongchou_t.jpg

1143 ms

zhuanti_icon.png

zhuanti_icon.png

1037 ms

blockchain.jpg

blockchain.jpg

1066 ms

record_icon.png

record_icon.png

1186 ms

left.png

left.png

1270 ms

m_66ab3e73ca386.jpg

m_66ab3e73ca386.jpg

855 ms

m_66ab5a0e69bb4.png

m_66ab5a0e69bb4.png

1288 ms

l_6615fb6ab5958.png

l_6615fb6ab5958.png

1923 ms

l_664313e858cf0.jpg

l_664313e858cf0.jpg

1289 ms

icon.png

icon.png

1188 ms

m_660cf767cfee7.jpg

m_660cf767cfee7.jpg

767 ms

m_6604d01db19ac.jpg

m_6604d01db19ac.jpg

950 ms

adpageview

adpageview

220 ms

adpageview

adpageview

422 ms

icon_1.png

icon_1.png

1190 ms

fold.png

fold.png

1227 ms

Login_Page_BG.png

Login_Page_BG.png

1253 ms

goTop.png

goTop.png

1259 ms

404.htm

404.htm

213 ms

404.htm

404.htm

379 ms

404.htm

404.htm

415 ms

noavatar_middle.gif

noavatar_middle.gif

211 ms

hm.gif

hm.gif

312 ms

404.htm

404.htm

209 ms

Accessibility Review

jpm.cn accessibility score

47

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

jpm.cn best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

jpm.cn SEO score

99

Search Engine Optimization Advices

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 Jpm.cn 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 Jpm.cn 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

jpm.cn

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