Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

fitflop.net

핏플랍 공식 웹사이트 | 핏플랍 | FITFLOP

Page Load Speed

10.7 sec in total

First Response

1.2 sec

Resources Loaded

7.6 sec

Page Rendered

1.9 sec

About Website

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

FitFlop에서 하루 종일 여러분의 편안함을 고려하여 생체역학 기술이 적용된 다양하고 스타일리시한 신발을 확인하세요. 운동화, 부츠, 샌들, 슬리퍼 등을 만나보세요.

Visit fitflop.net

Key Findings

We analyzed Fitflop.net page load time and found that the first response time was 1.2 sec and then it took 9.4 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

fitflop.net performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.7 s

0/100

25%

SI (Speed Index)

Value19.0 s

0/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.917

3/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

www.fitflop.co.kr

1241 ms

reset.css

350 ms

common.css

357 ms

layer.css

359 ms

layout.css

368 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fitflop.net, 37% (30 requests) were made to Cdn-pro-web-212-222.cdn-nhncommerce.com and 9% (7 requests) were made to Rlix6mlbu.toastcdn.net. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Scontent-ssn1-1.cdninstagram.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 522.1 kB (7%)

Content Size

7.7 MB

After Optimization

7.1 MB

In fact, the total size of Fitflop.net main page is 7.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. 65% of websites need less resources to load. Images take 7.3 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 135.1 kB

  • Original 149.9 kB
  • After minification 109.0 kB
  • After compression 14.8 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 40.9 kB, which is 27% 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 135.1 kB or 90% of the original size.

Image Optimization

-5%

Potential reduce by 350.4 kB

  • Original 7.3 MB
  • After minification 6.9 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. FITFLOP images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 26.3 kB

  • Original 152.2 kB
  • After minification 152.2 kB
  • After compression 125.9 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 26.3 kB or 17% of the original size.

CSS Optimization

-21%

Potential reduce by 10.3 kB

  • Original 50.0 kB
  • After minification 50.0 kB
  • After compression 39.6 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. Fitflop.net needs all CSS files to be minified and compressed as it can save up to 10.3 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (44%)

Requests Now

71

After Optimization

40

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

Accessibility Review

fitflop.net accessibility score

79

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

fitflop.net 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fitflop.net SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fitflop.net can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fitflop.net 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 data is detected on the main page of FITFLOP. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: