Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 34

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

xmjr.com

小马金融—一融俱荣,马到成功

Page Load Speed

15.2 sec in total

First Response

887 ms

Resources Loaded

13.7 sec

Page Rendered

623 ms

xmjr.com screenshot

About Website

Click here to check amazing Xmjr content. Otherwise, check out these important facts you probably never knew about xmjr.com

小马金融理财平台由互联网行业精英、顶级小微信贷技术团队和多年银行经验高层组成,注册资本金高达一亿元,采用目前国际公认德国IPC风控技术,在保障您资产安全根本的基础上更为您放大价值

Visit xmjr.com

Key Findings

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

xmjr.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.841

4/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

xmjr.com

887 ms

www.xmjr.com

1855 ms

bootstrap.min.css

238 ms

util.css

713 ms

main.css

703 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 95% of them (82 requests) were addressed to the original Xmjr.com, 1% (1 request) were made to W.cnzz.com and 1% (1 request) were made to Oq.cnzz.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Cnzz.mmstat.com.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

815.5 kB

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

HTML Optimization

-76%

Potential reduce by 70.3 kB

  • Original 92.5 kB
  • After minification 88.6 kB
  • After compression 22.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. 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 70.3 kB or 76% of the original size.

Image Optimization

-13%

Potential reduce by 98.4 kB

  • Original 768.9 kB
  • After minification 670.6 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. Obviously, Xmjr needs image optimization as it can save up to 98.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 144.5 kB

  • Original 208.0 kB
  • After minification 183.2 kB
  • After compression 63.4 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 144.5 kB or 70% of the original size.

CSS Optimization

-85%

Potential reduce by 325.4 kB

  • Original 384.6 kB
  • After minification 367.8 kB
  • After compression 59.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. Xmjr.com needs all CSS files to be minified and compressed as it can save up to 325.4 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

80

After Optimization

64

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

Accessibility Review

xmjr.com accessibility score

34

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

xmjr.com best practices score

75

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

Page has valid source maps

SEO Factors

xmjr.com SEO score

92

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

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

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