Access runningup.co.kr. 라인이 살아있는 요가복 ! 러닝업

runningup.co.kr screenshot

22

Performance

Renders faster than
40% of other websites
59

Accessibility

Visual factors better than
that of 26% of websites
67

Best Practices

More advanced features
available than in
24% of websites
77

SEO

Google-friendlier than
36% of websites

First Response

1.5 sec

Resources Loaded

7.5 sec

Page Rendered

732 ms

runningup.co.kr screenshot

About Website

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

꿈꿔왔던 라인을 만들다! 완벽한 핏감 러닝업

Visit runningup.co.kr

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value1.216

1/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

runningup.co.kr

1496 ms

common.js

396 ms

cid.generate.js

406 ms

wcslog.js

5 ms

optimizer.php

613 ms

Our browser made a total of 156 requests to load all elements on the main page. We found that 90% of them (141 requests) were addressed to the original Runningup.co.kr, 6% (9 requests) were made to Img.echosting.cafe24.com and 1% (1 request) were made to Wcs.naver.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Runningup.co.kr.

Content Size

1.7 MB

After Optimization

1.6 MB

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

HTML Optimization

-92%

Potential reduce by 93.9 kB

Original 102.3 kB
After minification 92.0 kB
After compression 8.4 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 93.9 kB or 92% of the original size.

Image Optimization

-1%

Potential reduce by 17.3 kB

Original 1.6 MB
After minification 1.6 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. Runningup images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 34.3 kB

Original 45.4 kB
After minification 36.7 kB
After compression 11.0 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 34.3 kB or 76% of the original size.

Requests Now

155

After Optimization

140

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

Accessibility Issues

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.

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

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

EUC-KR

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

runningup.co.kr

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