Tools & Wizards About Us
qcr.cc screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

qcr.cc

汽车人招聘网,汽车人才网,专注汽车行业招聘,4s店招聘,汽车维修美容招聘,求职,找工作

Page Load Speed

48.3 sec in total

First Response

1.2 sec

Resources Loaded

46.5 sec

Page Rendered

552 ms

qcr.cc screenshot

About Website

Click here to check amazing Qcr content for China. Otherwise, check out these important facts you probably never knew about qcr.cc

汽车人招聘网是专业的汽车人才招聘网站。招聘企业包括：汽贸集团4S店招聘,汽车维修美容招聘,汽车销售零部件销售、二手车汽车租赁、汽车研发设计生产制造厂、新能源汽车招聘。专业，有效！

Visit qcr.cc

Key Findings

We analyzed Qcr.cc page load time and found that the first response time was 1.2 sec and then it took 47.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 5 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

qcr.cc performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

qcr.cc

1235 ms

www.qcr.cc

11963 ms

gg.css

20222 ms

Normalize.css

14450 ms

jsgg.js

19832 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 48% of them (20 requests) were addressed to the original Qcr.cc, 33% (14 requests) were made to Bdimg.share.baidu.com and 5% (2 requests) were made to Static.anquan.org. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain Qcr.cc.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.4 kB (52%)

Content Size

255.1 kB

After Optimization

123.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qcr.cc main page is 255.1 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. Only 10% of websites need less resources to load. Javascripts take 134.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 50.5 kB

  • Original 65.2 kB
  • After minification 60.5 kB
  • After compression 14.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. 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 50.5 kB or 77% of the original size.

Image Optimization

-22%

Potential reduce by 12.3 kB

  • Original 55.1 kB
  • After minification 42.7 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, Qcr needs image optimization as it can save up to 12.3 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-51%

Potential reduce by 68.6 kB

  • Original 134.0 kB
  • After minification 109.3 kB
  • After compression 65.5 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 68.6 kB or 51% of the original size.

CSS Optimization

-1%

Potential reduce by 11 B

  • Original 831 B
  • After minification 831 B
  • After compression 820 B

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. Qcr.cc has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (82%)

Requests Now

34

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qcr.cc

qcr.cc

1235 ms

www.qcr.cc

www.qcr.cc

11963 ms

gg.css

gg.css

20222 ms

Normalize.css

Normalize.css

14450 ms

jsgg.js

jsgg.js

19832 ms

qcr.js

qcr.js

10090 ms

qcr_default.js

qcr_default.js

1804 ms

aq_auth.js

aq_auth.js

11913 ms

fastclick.js

fastclick.js

19547 ms

logo_80_f_70.png

logo_80_f_70.png

1656 ms

logo166.png

logo166.png

1993 ms

qcrlogoT.gif

qcrlogoT.gif

1351 ms

df_ad_bg.png

df_ad_bg.png

5080 ms

1439802897.png

1439802897.png

5076 ms

null5.png

null5.png

11103 ms

null2.png

null2.png

5759 ms

201603291327074406278.jpg

201603291327074406278.jpg

13863 ms

201603211450339744398.jpg

201603211450339744398.jpg

19983 ms

201603211448236747328.jpg

201603211448236747328.jpg

16506 ms

Default.gif

Default.gif

12393 ms

logo_w_70.png

logo_w_70.png

19911 ms

share.js

share.js

667 ms

stat.php

stat.php

2468 ms

stat.htm

stat.htm

166 ms

core.php

core.php

2058 ms

9.gif

9.gif

10063 ms

3337 ms

share_api.js

share_api.js

228 ms

share_view.js

share_view.js

454 ms

select_api.js

select_api.js

453 ms

select_view.js

select_view.js

462 ms

image_api.js

image_api.js

455 ms

image_view.js

image_view.js

502 ms

tangram.js

tangram.js

1577 ms

api_base.js

api_base.js

512 ms

view_base.js

view_base.js

269 ms

partners.js

partners.js

776 ms

share_style0_32.css

share_style0_32.css

245 ms

icons_0_32.png

icons_0_32.png

1463 ms

logger.js

logger.js

282 ms

hy_124x47.png

hy_124x47.png

3138 ms

app.gif

app.gif

843 ms

Accessibility Review

qcr.cc accessibility score

50

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

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

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

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

qcr.cc best practices score

83

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

SEO Factors

qcr.cc SEO score

86

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

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 Qcr.cc 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 Qcr.cc 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

qcr.cc

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