Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

jupai.net

聚拍网-买大企业闲置废旧物资上聚拍-网上拍卖会

Page Load Speed

66.7 sec in total

First Response

1.6 sec

Resources Loaded

64.4 sec

Page Rendered

778 ms

jupai.net screenshot

About Website

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

废旧物资拍卖网,是废旧物资网上拍卖信息网站,提供废旧物资设备拍卖、厂房设施拍卖、资产拍卖、机动车拍卖、房产拍卖等信息,拥有网上拍卖公司、拍卖公告、股权转让等的拍卖信息平台。

Visit jupai.net

Key Findings

We analyzed Jupai.net page load time and found that the first response time was 1.6 sec and then it took 65.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 14 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

jupai.net performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.305

39/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

jupai.net

1576 ms

www.jupai.net

4328 ms

jupai.css

7800 ms

fwslider.css

1065 ms

lrtk.css

19939 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 93% of them (98 requests) were addressed to the original Jupai.net, 1% (1 request) were made to S95.cnzz.com and 1% (1 request) were made to Push.zhanzhang.baidu.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Jupai.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 552.2 kB (43%)

Content Size

1.3 MB

After Optimization

720.9 kB

In fact, the total size of Jupai.net main page is 1.3 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. 30% of websites need less resources to load. Images take 607.3 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 104.4 kB

  • Original 118.0 kB
  • After minification 74.1 kB
  • After compression 13.6 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 43.9 kB, which is 37% 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 104.4 kB or 88% of the original size.

Image Optimization

-6%

Potential reduce by 36.4 kB

  • Original 607.3 kB
  • After minification 570.9 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. Jupai images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 285.8 kB

  • Original 403.0 kB
  • After minification 392.2 kB
  • After compression 117.2 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 285.8 kB or 71% of the original size.

CSS Optimization

-87%

Potential reduce by 125.7 kB

  • Original 144.9 kB
  • After minification 89.5 kB
  • After compression 19.2 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. Jupai.net needs all CSS files to be minified and compressed as it can save up to 125.7 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (49%)

Requests Now

87

After Optimization

44

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

Accessibility Review

jupai.net accessibility score

77

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

[id] attributes on active, focusable elements are not unique

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

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

Best Practices

jupai.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

jupai.net SEO score

83

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 Jupai.net 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 Jupai.net 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 Jupai. 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: