Report Summary

  • 2

    Performance

    Renders faster than
    19% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

imvely.com

IMVELY :: 임블리

Page Load Speed

19.9 sec in total

First Response

2.7 sec

Resources Loaded

11.3 sec

Page Rendered

5.9 sec

imvely.com screenshot

About Website

Click here to check amazing IMVELY content for South Korea. Otherwise, check out these important facts you probably never knew about imvely.com

임블리 임지현의 코스메틱&이너뷰티 BRAND |블리블리|리코어|고단고식|헬씨밀랩

Visit imvely.com

Key Findings

We analyzed Imvely.com page load time and found that the first response time was 2.7 sec and then it took 17.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

imvely.com performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value71.6 s

0/100

25%

SI (Speed Index)

Value40.0 s

0/100

10%

TBT (Total Blocking Time)

Value6,410 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.549

13/100

15%

TTI (Time to Interactive)

Value158.4 s

0/100

10%

Network Requests Diagram

imvely.com

2713 ms

common.js

394 ms

cid.generate.js

401 ms

wcslog.js

6 ms

optimizer.php

613 ms

Our browser made a total of 796 requests to load all elements on the main page. We found that 28% of them (223 requests) were addressed to the original Imvely.com, 29% (228 requests) were made to Amazon.poxo.com and 28% (224 requests) were made to Imgcdn.poxo.com. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Gundolle.com.

Page Optimization Overview & Recommendations

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

Content Size

11.8 MB

After Optimization

10.1 MB

In fact, the total size of Imvely.com main page is 11.8 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. 85% 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 10.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 235.9 kB

  • Original 276.1 kB
  • After minification 255.5 kB
  • After compression 40.3 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 235.9 kB or 85% of the original size.

Image Optimization

-6%

Potential reduce by 603.7 kB

  • Original 10.3 MB
  • After minification 9.7 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. IMVELY images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 643.7 kB

  • Original 978.5 kB
  • After minification 970.4 kB
  • After compression 334.8 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 643.7 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 237.4 kB

  • Original 277.7 kB
  • After minification 275.5 kB
  • After compression 40.3 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. Imvely.com needs all CSS files to be minified and compressed as it can save up to 237.4 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

345

After Optimization

295

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

Accessibility Review

imvely.com accessibility score

77

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

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

imvely.com best practices score

58

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

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

imvely.com SEO score

78

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    KO

  • Encoding

    UTF-8

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

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