Tools & Wizards About Us
qq620.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 40

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

qq620.com

6号车圈 车友之家

Page Load Speed

8 sec in total

First Response

656 ms

Resources Loaded

7.2 sec

Page Rendered

211 ms

qq620.com screenshot

About Website

Visit qq620.com now to see the best up-to-date Qq 620 content and also check out these interesting facts you probably never knew about qq620.com

首页

Visit qq620.com

Key Findings

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

qq620.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value6.8 s

34/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

qq620.com

656 ms

qq620.com

853 ms

www.qq620.com

1358 ms

style_13_common.css

244 ms

style_13_portal_index.css

486 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 97% of them (75 requests) were addressed to the original Qq620.com, 3% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Qq620.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 124.7 kB (11%)

Content Size

1.1 MB

After Optimization

997.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qq620.com main page is 1.1 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 919.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 42.5 kB

  • Original 54.1 kB
  • After minification 53.9 kB
  • After compression 11.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 42.5 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 62.7 kB

  • Original 919.0 kB
  • After minification 856.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. Qq 620 images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 14.1 kB

  • Original 120.5 kB
  • After minification 120.4 kB
  • After compression 106.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 14.1 kB or 12% of the original size.

CSS Optimization

-19%

Potential reduce by 5.4 kB

  • Original 28.6 kB
  • After minification 28.6 kB
  • After compression 23.1 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. Qq620.com needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 19% of the original size.

Requests Breakdown

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

Requests Now

69

After Optimization

49

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qq620.com

qq620.com

656 ms

qq620.com

qq620.com

853 ms

www.qq620.com

www.qq620.com

1358 ms

style_13_common.css

style_13_common.css

244 ms

style_13_portal_index.css

style_13_portal_index.css

486 ms

common.js

common.js

846 ms

portal.js

portal.js

636 ms

logging.js

logging.js

669 ms

jquery.min.js

jquery.min.js

905 ms

top.js

top.js

690 ms

comiis_pcflxx.css

comiis_pcflxx.css

725 ms

jquery.min.js

jquery.min.js

1062 ms

Slide.2.1.1.js

Slide.2.1.1.js

966 ms

sidebar.min.js

sidebar.min.js

1056 ms

wechat_login.png

wechat_login.png

300 ms

app_login.png

app_login.png

300 ms

sms_login.png

sms_login.png

321 ms

logo.png

logo.png

359 ms

a1.png

a1.png

419 ms

a2.png

a2.png

425 ms

a3.png

a3.png

507 ms

a4.png

a4.png

512 ms

a5.png

a5.png

551 ms

a6.png

a6.png

600 ms

a7.png

a7.png

631 ms

a8.png

a8.png

1271 ms

a9.png

a9.png

730 ms

a10.png

a10.png

737 ms

a11.png

a11.png

781 ms

a12.png

a12.png

840 ms

qrcode1.jpg

qrcode1.jpg

842 ms

cd9840125e1cea9ddf00a31ebfe9badc.jpg

cd9840125e1cea9ddf00a31ebfe9badc.jpg

1619 ms

77f1bc99d0caab0edadf5f129eb5a2fd.jpg

77f1bc99d0caab0edadf5f129eb5a2fd.jpg

1414 ms

428b1bba4869f8ea64aa9cf3a0d06c14.jpg

428b1bba4869f8ea64aa9cf3a0d06c14.jpg

1471 ms

3gg.jpg

3gg.jpg

1080 ms

hui_huifu.png

hui_huifu.png

1054 ms

hui_chakan.png

hui_chakan.png

1265 ms

hui_xiangshang.png

hui_xiangshang.png

1320 ms

hui_xiangxia.png

hui_xiangxia.png

1477 ms

699c9b8b09fc8535f9659d24e37019b8.jpg

699c9b8b09fc8535f9659d24e37019b8.jpg

1483 ms

0b2a2a21820615109bbc45dd87109d3d.jpg

0b2a2a21820615109bbc45dd87109d3d.jpg

1562 ms

1c523d8560d2108b7481e7e424d155a5.jpg

1c523d8560d2108b7481e7e424d155a5.jpg

1640 ms

b89162d221ec3258d1bf9cc8f9312f8b.jpg

b89162d221ec3258d1bf9cc8f9312f8b.jpg

1701 ms

399edcb2f9a8cdd062174dbb92fe20f4.jpg

399edcb2f9a8cdd062174dbb92fe20f4.jpg

1677 ms

44_avatar_middle.jpg

44_avatar_middle.jpg

1631 ms

08_avatar_middle.jpg

08_avatar_middle.jpg

1738 ms

01_avatar_middle.jpg

01_avatar_middle.jpg

1755 ms

17_avatar_middle.jpg

17_avatar_middle.jpg

1751 ms

35_avatar_middle.jpg

35_avatar_middle.jpg

1695 ms

common_extra.js

common_extra.js

1682 ms

hm.js

hm.js

960 ms

1gg.jpg

1gg.jpg

1635 ms

logo_wei.png

logo_wei.png

1746 ms

qrcode2.jpg

qrcode2.jpg

1748 ms

site_qq.jpg

site_qq.jpg

1736 ms

bai_dark.png

bai_dark.png

1694 ms

side_fatie.png

side_fatie.png

1697 ms

side_dingbu.png

side_dingbu.png

1658 ms

hui_daohang1.png

hui_daohang1.png

1776 ms

hui_fatie1.png

hui_fatie1.png

1740 ms

so.png

so.png

1721 ms

lanjiazai.gif

lanjiazai.gif

1692 ms

hm.gif

hm.gif

300 ms

side_sanjiao_y.png

side_sanjiao_y.png

1412 ms

22_150_100.jpg

22_150_100.jpg

675 ms

23_150_100.jpg

23_150_100.jpg

663 ms

18_150_100.jpg

18_150_100.jpg

578 ms

24_150_100.jpg

24_150_100.jpg

581 ms

21_150_100.jpg

21_150_100.jpg

570 ms

19_150_100.jpg

19_150_100.jpg

588 ms

07_150_100.jpg

07_150_100.jpg

660 ms

05_150_100.jpg

05_150_100.jpg

623 ms

96_150_100.jpg

96_150_100.jpg

519 ms

01_150_100.jpg

01_150_100.jpg

488 ms

99_150_100.jpg

99_150_100.jpg

470 ms

02_150_100.jpg

02_150_100.jpg

498 ms

00_150_100.jpg

00_150_100.jpg

545 ms

Accessibility Review

qq620.com accessibility score

40

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

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

qq620.com best practices score

67

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

SEO Factors

qq620.com SEO score

90

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

qq620.com

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