Tools & Wizards About Us
ieasycar.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

ieasycar.com

:: Easycar ::

Page Load Speed

7.6 sec in total

First Response

818 ms

Resources Loaded

6.5 sec

Page Rendered

307 ms

ieasycar.com screenshot

About Website

Welcome to ieasycar.com homepage info - get ready to check I Easycar best content for Vietnam right away, or after learning these important things about ieasycar.com

국내 텔레매틱스 선도기업을 꿈꾸며 설립한 지난 15년. 그 동안 축적된 기술과 경험을 바탕으로 최상의 제품을 제공하기 위해 끝없는 도전으로 제품 개발에 힘쓰고 있습니다.

Visit ieasycar.com

Key Findings

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

ieasycar.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value24.6 s

0/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.231

54/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

ieasycar.com

818 ms

style.css

469 ms

easy001.js

472 ms

back.png

5161 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that all of those requests were addressed to Ieasycar.com and no external sources were called. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Ieasycar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.7 kB (15%)

Content Size

346.6 kB

After Optimization

293.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ieasycar.com main page is 346.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 341.1 kB which makes up the majority of the site volume.

HTML Optimization

-47%

Potential reduce by 683 B

  • Original 1.4 kB
  • After minification 1.4 kB
  • After compression 756 B

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 683 B or 47% of the original size.

Image Optimization

-14%

Potential reduce by 48.7 kB

  • Original 341.1 kB
  • After minification 292.4 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, I Easycar needs image optimization as it can save up to 48.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-24%

Potential reduce by 67 B

  • Original 283 B
  • After minification 279 B
  • After compression 216 B

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 67 B or 24% of the original size.

CSS Optimization

-84%

Potential reduce by 3.2 kB

  • Original 3.8 kB
  • After minification 3.7 kB
  • After compression 611 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. Ieasycar.com needs all CSS files to be minified and compressed as it can save up to 3.2 kB or 84% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

  • Images
  • JavaScript
  • CSS

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I Easycar. According to our analytics all requests are already optimized.

Network Requests Diagram

ieasycar.com

ieasycar.com

818 ms

style.css

style.css

469 ms

easy001.js

easy001.js

472 ms

back.png

back.png

5161 ms

Accessibility Review

ieasycar.com accessibility score

53

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ieasycar.com SEO score

81

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

    KO

  • Language Claimed

    N/A

  • Encoding

    EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ieasycar.com can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 Ieasycar.com main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ieasycar.com

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