Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

rowky.com

로우키샵-ROWKY

Page Load Speed

28.3 sec in total

First Response

1.6 sec

Resources Loaded

13.1 sec

Page Rendered

13.5 sec

rowky.com screenshot

About Website

Visit rowky.com now to see the best up-to-date ROWKY content for South Korea and also check out these interesting facts you probably never knew about rowky.com

여성의류 쇼핑몰 ,나만 갖고 싶은 귀엽고 유니크한 특별한 쥬얼리와 유니크한 소품

Visit rowky.com

Key Findings

We analyzed Rowky.com page load time and found that the first response time was 1.6 sec and then it took 26.6 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

rowky.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.649

9/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

rowky.com

1617 ms

css

24 ms

common.js

455 ms

cid.generate.js

456 ms

optimizer.php

494 ms

Our browser made a total of 170 requests to load all elements on the main page. We found that 96% of them (164 requests) were addressed to the original Rowky.com, 1% (2 requests) were made to Img.cafe24.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Rowky.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 317.0 kB (4%)

Content Size

9.0 MB

After Optimization

8.7 MB

In fact, the total size of Rowky.com main page is 9.0 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 8.7 MB which makes up the majority of the site volume.

HTML Optimization

-95%

Potential reduce by 311.4 kB

  • Original 326.8 kB
  • After minification 311.2 kB
  • After compression 15.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 311.4 kB or 95% of the original size.

Image Optimization

-0%

Potential reduce by 347 B

  • Original 8.7 MB
  • After minification 8.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. ROWKY images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 5.3 kB

  • Original 7.0 kB
  • After minification 4.7 kB
  • After compression 1.7 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 5.3 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (2%)

Requests Now

168

After Optimization

165

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

Accessibility Review

rowky.com accessibility score

56

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

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

rowky.com 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

rowky.com SEO score

70

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

    EUC-KR

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