Report Summary

  • 0

    Performance

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

feiler.jp

フェイラー公式オンラインショップ

Page Load Speed

15.4 sec in total

First Response

341 ms

Resources Loaded

14 sec

Page Rendered

1.1 sec

feiler.jp screenshot

About Website

Welcome to feiler.jp homepage info - get ready to check Feiler best content for Japan right away, or after learning these important things about feiler.jp

フェイラー/FEILERのタオル。歴史と伝統に彩られたフェイラー/FEILERのシュニール織は、世界の人々を魅了し続けています。ドイツ・フェイラー(FEILER) 社総輸入元 フェイラージャパン株式会社による公式通販なので安心してショッピングをお楽しみください。

Visit feiler.jp

Key Findings

We analyzed Feiler.jp page load time and found that the first response time was 341 ms and then it took 15.1 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

feiler.jp performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value36.7 s

0/100

25%

SI (Speed Index)

Value29.8 s

0/100

10%

TBT (Total Blocking Time)

Value4,910 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.433

0/100

15%

TTI (Time to Interactive)

Value35.4 s

0/100

10%

Network Requests Diagram

feiler.jp

341 ms

default.aspx

2 ms

default.aspx

1403 ms

gtm.js

105 ms

reset.css

660 ms

Our browser made a total of 311 requests to load all elements on the main page. We found that 62% of them (194 requests) were addressed to the original Feiler.jp, 6% (20 requests) were made to Show.revico.jp and 2% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Feiler.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 708.1 kB (12%)

Content Size

5.9 MB

After Optimization

5.2 MB

In fact, the total size of Feiler.jp main page is 5.9 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 a small number of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 113.3 kB

  • Original 137.7 kB
  • After minification 123.3 kB
  • After compression 24.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 113.3 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 150.3 kB

  • Original 4.0 MB
  • After minification 3.8 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. Feiler images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 402.5 kB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 1.3 MB

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 402.5 kB or 23% of the original size.

CSS Optimization

-46%

Potential reduce by 42.1 kB

  • Original 91.1 kB
  • After minification 90.6 kB
  • After compression 49.0 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. Feiler.jp needs all CSS files to be minified and compressed as it can save up to 42.1 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 142 (47%)

Requests Now

302

After Optimization

160

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

Accessibility Review

feiler.jp accessibility score

58

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

feiler.jp 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

feiler.jp SEO score

79

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Feiler.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Feiler.jp main page’s claimed encoding is shift_jis. 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 Feiler. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: