Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

feelway.com

필웨이 (FEELWAY) - 국내 최대 명품 사이트, 쉽고 빠른 필웨이

Page Load Speed

9.4 sec in total

First Response

572 ms

Resources Loaded

8.5 sec

Page Rendered

339 ms

feelway.com screenshot

About Website

Welcome to feelway.com homepage info - get ready to check FEELWAY best content for South Korea right away, or after learning these important things about feelway.com

당신이 찾는 모든 명품, 필웨이(FEELWAY). 22년 노하우 쉽고 빠른 명품 거래 - 필웨이(FEELWAY)

Visit feelway.com

Key Findings

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

Performance Metrics

feelway.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value17.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value40.3 s

0/100

25%

SI (Speed Index)

Value28.2 s

0/100

10%

TBT (Total Blocking Time)

Value9,840 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.153

75/100

15%

TTI (Time to Interactive)

Value72.8 s

0/100

10%

Network Requests Diagram

feelway.com

572 ms

www.feelway.com

2099 ms

elastic-apm-rum.umd.min.js

1856 ms

gtm.js

81 ms

style1.5_common.css

1480 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 21% of them (23 requests) were addressed to the original Feelway.com, 41% (45 requests) were made to Css.feelway.com and 11% (12 requests) were made to Icon.feelway.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Css.feelway.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 949.8 kB (37%)

Content Size

2.6 MB

After Optimization

1.6 MB

In fact, the total size of Feelway.com main page is 2.6 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. 75% 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 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 832.2 kB

  • Original 997.7 kB
  • After minification 972.5 kB
  • After compression 165.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. 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 832.2 kB or 83% of the original size.

Image Optimization

-9%

Potential reduce by 114.4 kB

  • Original 1.3 MB
  • After minification 1.2 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. FEELWAY images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.3 kB

  • Original 274.1 kB
  • After minification 274.1 kB
  • After compression 270.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 68 (65%)

Requests Now

105

After Optimization

37

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

Accessibility Review

feelway.com accessibility score

63

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-*] attributes do not have valid values

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

feelway.com best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

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

High

Page is blocked from indexing

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

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 Feelway.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 Feelway.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 data is detected on the main page of FEELWAY. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: