Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

saintpain.co.kr

Saintpain

Page Load Speed

12.7 sec in total

First Response

781 ms

Resources Loaded

11.6 sec

Page Rendered

315 ms

saintpain.co.kr screenshot

About Website

Visit saintpain.co.kr now to see the best up-to-date Saintpain content for Japan and also check out these interesting facts you probably never knew about saintpain.co.kr

SAINTPAIN. The official online store of SAINTPAIN. 세인트페인 공식 온라인 스토어. 룩북. 매장정보 제공

Visit saintpain.co.kr

Key Findings

We analyzed Saintpain.co.kr page load time and found that the first response time was 781 ms and then it took 12 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

saintpain.co.kr performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value760 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

saintpain.co.kr

781 ms

saintpain.co.kr

1485 ms

jet.js

27 ms

jquery-latest.min.js

27 ms

jquery.min.js

18 ms

Our browser made a total of 291 requests to load all elements on the main page. We found that 89% of them (259 requests) were addressed to the original Saintpain.co.kr, 3% (10 requests) were made to Cdn.jsdelivr.net and 2% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Saintpain.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (3%)

Content Size

41.7 MB

After Optimization

40.4 MB

In fact, the total size of Saintpain.co.kr main page is 41.7 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. Only a small number of websites need less resources to load. Images take 39.9 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 490.3 kB

  • Original 536.8 kB
  • After minification 443.9 kB
  • After compression 46.5 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 92.9 kB, which is 17% 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 490.3 kB or 91% of the original size.

Image Optimization

-1%

Potential reduce by 575.3 kB

  • Original 39.9 MB
  • After minification 39.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. Saintpain images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 223.9 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 907.2 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 223.9 kB or 20% of the original size.

CSS Optimization

-0%

Potential reduce by 94 B

  • Original 72.3 kB
  • After minification 72.3 kB
  • After compression 72.2 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. Saintpain.co.kr has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (8%)

Requests Now

277

After Optimization

255

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

Accessibility Review

saintpain.co.kr accessibility score

71

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 input fields do not have accessible names

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

<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

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.

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

saintpain.co.kr 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

saintpain.co.kr SEO score

86

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

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 Saintpain.co.kr 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 Saintpain.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 Saintpain. 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: