Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

amante.co.kr

아망떼 ㅣ평범한 일상, 특별한 당신 아망떼

Page Load Speed

120.7 sec in total

First Response

1.7 sec

Resources Loaded

118.2 sec

Page Rendered

764 ms

amante.co.kr screenshot

About Website

Welcome to amante.co.kr homepage info - get ready to check Amante best content for South Korea right away, or after learning these important things about amante.co.kr

홈데코부터 다양한 침구류까지 홈스타일링의 시작 아망떼

Visit amante.co.kr

Key Findings

We analyzed Amante.co.kr page load time and found that the first response time was 1.7 sec and then it took 119 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 65 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

amante.co.kr performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value74.2 s

0/100

25%

SI (Speed Index)

Value16.2 s

0/100

10%

TBT (Total Blocking Time)

Value6,280 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.811

4/100

15%

TTI (Time to Interactive)

Value45.6 s

0/100

10%

Network Requests Diagram

www.amante.co.kr

1701 ms

jquery-1.9.1.min.js

1229 ms

init.js

507 ms

common.js

505 ms

common.css

513 ms

Our browser made a total of 242 requests to load all elements on the main page. We found that 50% of them (122 requests) were addressed to the original Amante.co.kr, 44% (107 requests) were made to Img.amante.co.kr and 1% (2 requests) were made to Adlog.adinsight.co.kr. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Img.amante.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (10%)

Content Size

16.1 MB

After Optimization

14.4 MB

In fact, the total size of Amante.co.kr main page is 16.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. 65% of websites need less resources to load. Images take 15.4 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 160.0 kB

  • Original 183.9 kB
  • After minification 164.9 kB
  • After compression 23.9 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 160.0 kB or 87% of the original size.

Image Optimization

-7%

Potential reduce by 1.1 MB

  • Original 15.4 MB
  • After minification 14.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. Amante images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 351.8 kB

  • Original 461.2 kB
  • After minification 327.1 kB
  • After compression 109.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 351.8 kB or 76% of the original size.

CSS Optimization

-84%

Potential reduce by 22.3 kB

  • Original 26.6 kB
  • After minification 20.9 kB
  • After compression 4.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. Amante.co.kr needs all CSS files to be minified and compressed as it can save up to 22.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (14%)

Requests Now

174

After Optimization

149

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

Accessibility Review

amante.co.kr accessibility score

67

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

amante.co.kr best practices score

75

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

Missing source maps for large first-party JavaScript

SEO Factors

amante.co.kr SEO score

76

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

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amante.co.kr 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 Amante.co.kr 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 Amante. 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: