Tools & Wizards About Us
fcar.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

fcar.com

Shenzhen FCAR Technology Co., Ltd.

Page Load Speed

12.1 sec in total

First Response

351 ms

Resources Loaded

10.7 sec

Page Rendered

1.1 sec

fcar.com screenshot

About Website

Click here to check amazing FCAR content for Pakistan. Otherwise, check out these important facts you probably never knew about fcar.com

Founded in 2007, Shenzhen FCAR Technology Co., Ltd. is one of the leaders in the automotive diagnostic industry. We are dedicated to automotive and truck diagnosis. We built strong in-house R&D team, ...

Visit fcar.com

Key Findings

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

fcar.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value33.3 s

0/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.789

5/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

fcar.com

351 ms

www.fcar.com

994 ms

www.fcar.com

1169 ms

respond.measure-2.min.css

1648 ms

animate.min.css

1782 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 15% of them (11 requests) were addressed to the original Fcar.com, 67% (49 requests) were made to 0.rc.xiniu.com and 8% (6 requests) were made to 1.rc.xiniu.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Fcar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.8 MB (56%)

Content Size

19.3 MB

After Optimization

8.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fcar.com main page is 19.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. 60% of websites need less resources to load. Images take 18.8 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 130.8 kB

  • Original 149.9 kB
  • After minification 92.6 kB
  • After compression 19.1 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 57.4 kB, which is 38% 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 130.8 kB or 87% of the original size.

Image Optimization

-55%

Potential reduce by 10.4 MB

  • Original 18.8 MB
  • After minification 8.4 MB

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, FCAR needs image optimization as it can save up to 10.4 MB or 55% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 116.0 kB

  • Original 175.4 kB
  • After minification 175.4 kB
  • After compression 59.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 116.0 kB or 66% of the original size.

CSS Optimization

-87%

Potential reduce by 114.5 kB

  • Original 131.0 kB
  • After minification 121.9 kB
  • After compression 16.4 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. Fcar.com needs all CSS files to be minified and compressed as it can save up to 114.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (15%)

Requests Now

65

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fcar.com

fcar.com

351 ms

www.fcar.com

www.fcar.com

994 ms

www.fcar.com

www.fcar.com

1169 ms

respond.measure-2.min.css

respond.measure-2.min.css

1648 ms

animate.min.css

animate.min.css

1782 ms

CgAH6F4S2EyANW9cAAACGcY8buo418.css

CgAH6F4S2EyANW9cAAACGcY8buo418.css

1600 ms

CgAG0mHEQxiADSucAAC78PkIrW8150.css

CgAG0mHEQxiADSucAAC78PkIrW8150.css

1961 ms

jqueryV173.js

jqueryV173.js

1975 ms

Public.js

Public.js

1715 ms

plugins.respond.min.js

plugins.respond.min.js

1773 ms

swiper.min.css

swiper.min.css

436 ms

swiper.min.js

swiper.min.js

1299 ms

index.js

index.js

440 ms

sdk.js

sdk.js

31 ms

CgAG0mFKE7mAaHVOAAAIYKKZKrU415.png

CgAG0mFKE7mAaHVOAAAIYKKZKrU415.png

266 ms

xn_mn_3_menu.png

xn_mn_3_menu.png

262 ms

CgAG0mFKE8eAPuACAAAISP0h_jE131.png

CgAG0mFKE8eAPuACAAAISP0h_jE131.png

263 ms

CgAG0mFKE9aADcFXAAAJgMjpZ7c922.png

CgAG0mFKE9aADcFXAAAJgMjpZ7c922.png

554 ms

CgAG0mFKE96AAbUWAAAKb5mUpok248.png

CgAG0mFKE96AAbUWAAAKb5mUpok248.png

554 ms

CgAG0mFKE-SAALC7AAAIOiQch-g801.png

CgAG0mFKE-SAALC7AAAIOiQch-g801.png

786 ms

CgAG0mFER2qAenjVAAAFc8STEp0635.png

CgAG0mFER2qAenjVAAAFc8STEp0635.png

802 ms

CgAG0mFESI6AIniBAAADpBYdqts235.png

CgAG0mFESI6AIniBAAADpBYdqts235.png

785 ms

CgAG0mFER2aAKRWYAAAE6LO0H2M877.png

CgAG0mFER2aAKRWYAAAE6LO0H2M877.png

786 ms

CgAG0mFvs32AEqgAAAAWqgn-ItA940.png

CgAG0mFvs32AEqgAAAAWqgn-ItA940.png

817 ms

CgAG0mFEVaqAQpruAAAEs4p3s9c924.png

CgAG0mFEVaqAQpruAAAEs4p3s9c924.png

784 ms

CgAG0mFFSIyALBs4AAAF7WCJhYs254.jpg

CgAG0mFFSIyALBs4AAAF7WCJhYs254.jpg

1045 ms

CgAG0mFKhFKAPLZnAAAFiGmNgEw010.jpg

CgAG0mFKhFKAPLZnAAAFiGmNgEw010.jpg

1029 ms

CgAG0mFmaLaAIHMhAAAKd2AITNM749.jpg

CgAG0mFmaLaAIHMhAAAKd2AITNM749.jpg

1029 ms

CgAG0mP10rmAUrX6ABcFHYi7uwI173.png

CgAG0mP10rmAUrX6ABcFHYi7uwI173.png

2829 ms

CgAG0mP10yiARAu-ABWAJYWXkPc439.png

CgAG0mP10yiARAu-ABWAJYWXkPc439.png

2845 ms

CgAG0mMhhnaAcq7wABjlurhnIrw475.png

CgAG0mMhhnaAcq7wABjlurhnIrw475.png

2862 ms

CgAG0mHU-mSAcpTNAALk0H_EILQ204.jpg

CgAG0mHU-mSAcpTNAALk0H_EILQ204.jpg

2253 ms

CgAG0mHU-biASoJfAAPIkYnPCfE917.jpg

CgAG0mHU-biASoJfAAPIkYnPCfE917.jpg

2349 ms

CgAG0mFJyamAO8rEAAAMXMnawHQ576.png

CgAG0mFJyamAO8rEAAAMXMnawHQ576.png

1277 ms

CgAG0mFJ1TKAYaCmAAAH2ZCqOgg942.png

CgAG0mFJ1TKAYaCmAAAH2ZCqOgg942.png

1517 ms

CgAG0mFEVTKAA2oFAAAE108hAaw249.png

CgAG0mFEVTKAA2oFAAAE108hAaw249.png

1739 ms

CgAG0mFEVNyAQVFqAAAEp7quP54996.png

CgAG0mFEVNyAQVFqAAAEp7quP54996.png

1978 ms

CgAG0mFFSXiALlPOAAAEaio1pAA002.jpg

CgAG0mFFSXiALlPOAAAEaio1pAA002.jpg

2218 ms

CgAG0mFFSeqAbKnlAAAElO6GzJw058.jpg

CgAG0mFFSeqAbKnlAAAElO6GzJw058.jpg

2458 ms

CgAG0mFJ3PmANLpHAAAFuypntZ4344.png

CgAG0mFJ3PmANLpHAAAFuypntZ4344.png

2468 ms

CgAG0mFJ3PmAcjlmAAAFtT6GOek738.png

CgAG0mFJ3PmAcjlmAAAFtT6GOek738.png

2565 ms

sdk.js

sdk.js

11 ms

CgAG0mFJtfGAL8vLAAB0RziKKco998.png

CgAG0mFJtfGAL8vLAAB0RziKKco998.png

2751 ms

CgAG0mFJuF2AbK2_AAAGnt5FCbY551.png

CgAG0mFJuF2AbK2_AAAGnt5FCbY551.png

2685 ms

CgAG0mFJ2cKAHlyQAAAGvUgnKUA272.png

CgAG0mFJ2cKAHlyQAAAGvUgnKUA272.png

2785 ms

img_loading.png

img_loading.png

226 ms

Common.ashx

Common.ashx

492 ms

Common.ashx

Common.ashx

550 ms

182 ms

181 ms

228 ms

180 ms

161 ms

CgAG0mGMdqeAKigmAAHDaQmoaBY367.jpg

CgAG0mGMdqeAKigmAAHDaQmoaBY367.jpg

2909 ms

CgAG0mGUpKiAZ6zjAAKzJrBgzsQ806.jpg

CgAG0mGUpKiAZ6zjAAKzJrBgzsQ806.jpg

3394 ms

CgAG0mGU5iqABcfSAAMxqhX2GIo795.jpg

CgAG0mGU5iqABcfSAAMxqhX2GIo795.jpg

2861 ms

CgAGbGXB39iAftQDAATkZRPSGl4737.png

CgAGbGXB39iAftQDAATkZRPSGl4737.png

3181 ms

CgAG0mQJjxqASuDgABelO6z1LiI289.png

CgAG0mQJjxqASuDgABelO6z1LiI289.png

3117 ms

CgAG0mQVRWuARMKgACu3tq6I9fI959.png

CgAG0mQVRWuARMKgACu3tq6I9fI959.png

3245 ms

CgAG0mQ6FbaAcuHdADQKNxVdjmc003.png

CgAG0mQ6FbaAcuHdADQKNxVdjmc003.png

3580 ms

638340189504567365730441714.png

638340189504567365730441714.png

6172 ms

CgAG0mGu-oSAZlhdAAEIrZ9Jm_g847.jpg

CgAG0mGu-oSAZlhdAAEIrZ9Jm_g847.jpg

3192 ms

CgAG0mGvG-iAHN5ZAAEBzZ00fUE320.jpg

CgAG0mGvG-iAHN5ZAAEBzZ00fUE320.jpg

3324 ms

CgAG0mGvGw-AYxHBAAC2H91r-8s261.jpg

CgAG0mGvGw-AYxHBAAC2H91r-8s261.jpg

3112 ms

CgAG0mP-vqeAOsQ8ACkRqS8iYYk219.png

CgAG0mP-vqeAOsQ8ACkRqS8iYYk219.png

4165 ms

CgAGbGVJ9d2AZunnAAmQjnj8a7I979.png

CgAGbGVJ9d2AZunnAAmQjnj8a7I979.png

2973 ms

CgAGbGXAlv-ATMBrAAHB6-tk78Q248.jpg

CgAGbGXAlv-ATMBrAAHB6-tk78Q248.jpg

3069 ms

CgAG0mP8bgWAIGbuAAkBMAGZfSs591.png

CgAG0mP8bgWAIGbuAAkBMAGZfSs591.png

3564 ms

CgAG0mIHXhGAIiKLAAN0No7kvfE718.jpg

CgAG0mIHXhGAIiKLAAN0No7kvfE718.jpg

3181 ms

CgAG0mIHWYiAUHebAAGy22_a1xk555.jpg

CgAG0mIHWYiAUHebAAGy22_a1xk555.jpg

3181 ms

CgAG0mGuzkSARPh-AAReGj3bdv8637.jpg

CgAG0mGuzkSARPh-AAReGj3bdv8637.jpg

3230 ms

CgAG0mGuxgaAeCogAARlNwwuwU8243.jpg

CgAG0mGuxgaAeCogAARlNwwuwU8243.jpg

3086 ms

Load.ashx

Load.ashx

270 ms

Accessibility Review

fcar.com accessibility score

46

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.

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

<frame> or <iframe> elements do not have a title

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fcar.com SEO score

68

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fcar.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fcar.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

fcar.com

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