Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

tomstory.co.kr

톰스토리 Tomstory 모던 캐주얼 유니섹스

Page Load Speed

5.9 sec in total

First Response

657 ms

Resources Loaded

5 sec

Page Rendered

194 ms

tomstory.co.kr screenshot

About Website

Click here to check amazing Tomstory content. Otherwise, check out these important facts you probably never knew about tomstory.co.kr

Tomstory 는 심플함과 모던함을 베이스로 한 컨템포러리 캐주얼입니다. 베이직과 트렌드의 절묘한 균형을 지향하며 합리적인 Price로 새로운 Look을 제안합니다.

Visit tomstory.co.kr

Key Findings

We analyzed Tomstory.co.kr page load time and found that the first response time was 657 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

tomstory.co.kr performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.83

4/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

tomstory.co.kr

657 ms

common.js

455 ms

style.css

469 ms

base.css

469 ms

main.css

519 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 542.7 kB (49%)

Content Size

1.1 MB

After Optimization

561.7 kB

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

HTML Optimization

-67%

Potential reduce by 4.5 kB

  • Original 6.6 kB
  • After minification 5.5 kB
  • After compression 2.2 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 1.1 kB, which is 16% 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 4.5 kB or 67% of the original size.

Image Optimization

-49%

Potential reduce by 532.7 kB

  • Original 1.1 MB
  • After minification 557.7 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, Tomstory needs image optimization as it can save up to 532.7 kB or 49% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-80%

Potential reduce by 4.0 kB

  • Original 5.0 kB
  • After minification 2.5 kB
  • After compression 996 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 4.0 kB or 80% of the original size.

CSS Optimization

-64%

Potential reduce by 1.5 kB

  • Original 2.4 kB
  • After minification 2.1 kB
  • After compression 857 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. Tomstory.co.kr needs all CSS files to be minified and compressed as it can save up to 1.5 kB or 64% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

24

After Optimization

24

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

Accessibility Review

tomstory.co.kr accessibility score

46

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

tomstory.co.kr best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

tomstory.co.kr SEO score

77

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

    EN

  • Language Claimed

    KO

  • Encoding

    EUC-KR

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

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