Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

incar.tw

癮車報

Page Load Speed

6.4 sec in total

First Response

277 ms

Resources Loaded

5.7 sec

Page Rendered

474 ms

incar.tw screenshot

About Website

Visit incar.tw now to see the best up-to-date Incar content for Taiwan and also check out these interesting facts you probably never knew about incar.tw

Visit incar.tw

Key Findings

We analyzed Incar.tw page load time and found that the first response time was 277 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

incar.tw performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value15.9 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value2,180 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value21.6 s

1/100

10%

Network Requests Diagram

incar.tw

277 ms

css_pbm0lsQQJ7A7WCCIMgxLho6mI_kBNgznNUWmTWcnfoE.css

131 ms

css_Gbim_QqMO8DRIDPMHllcqnNem8Wi9WvxVsTKhMuSQvI.css

136 ms

css_zin0d731I8v2co1H9EJj3oP3OIjPDAmC2RXdcE7FqNE.css

138 ms

css_pJE8VWQ2vBlDZM1VF2QOTHfKtjNF4hkyBH8lqPVIypQ.css

138 ms

Our browser made a total of 165 requests to load all elements on the main page. We found that 19% of them (31 requests) were addressed to the original Incar.tw, 13% (22 requests) were made to Static.xx.fbcdn.net and 12% (19 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Tw.buy.yahoo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 768.4 kB (33%)

Content Size

2.4 MB

After Optimization

1.6 MB

In fact, the total size of Incar.tw main page is 2.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 97.4 kB

  • Original 119.0 kB
  • After minification 114.4 kB
  • After compression 21.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. 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 97.4 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 59.7 kB

  • Original 1.4 MB
  • After minification 1.3 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. Incar images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 385.5 kB

  • Original 606.1 kB
  • After minification 591.0 kB
  • After compression 220.6 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 385.5 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 225.8 kB

  • Original 275.7 kB
  • After minification 274.9 kB
  • After compression 49.9 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. Incar.tw needs all CSS files to be minified and compressed as it can save up to 225.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (41%)

Requests Now

157

After Optimization

92

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

Accessibility Review

incar.tw accessibility score

97

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.

Best Practices

incar.tw best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

incar.tw SEO score

100

Search Engine Optimization Advices

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

    JA

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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