Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

fatema.jp

有限会社ファテマ ネット販売事業部

Page Load Speed

8.9 sec in total

First Response

618 ms

Resources Loaded

7.5 sec

Page Rendered

835 ms

fatema.jp screenshot

About Website

Visit fatema.jp now to see the best up-to-date Fatema content and also check out these interesting facts you probably never knew about fatema.jp

有限会社ファテマ ネット販売事業部では、ラスタカラー製品、アルパカ製品を始め衣装小物等の販売、フルオーダーのウェディングドレス、舞台衣装、コスプレ衣装、着ぐるみ等を製作しております。ぜひお気軽にご相談ください。

Visit fatema.jp

Key Findings

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

fatema.jp performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.145

77/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

www.fatema.jp

618 ms

colormekit.css

313 ms

colormekit-responsive.css

333 ms

cross-border-cart.css

355 ms

index.css

746 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 10% of them (12 requests) were addressed to the original Fatema.jp, 57% (69 requests) were made to Img20.shop-pro.jp and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Img20.shop-pro.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 373.7 kB (23%)

Content Size

1.6 MB

After Optimization

1.2 MB

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

HTML Optimization

-87%

Potential reduce by 70.1 kB

  • Original 80.3 kB
  • After minification 64.5 kB
  • After compression 10.1 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 15.8 kB, which is 20% 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 70.1 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 40.9 kB

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

JavaScript Optimization

-67%

Potential reduce by 223.5 kB

  • Original 333.4 kB
  • After minification 253.5 kB
  • After compression 109.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 223.5 kB or 67% of the original size.

CSS Optimization

-81%

Potential reduce by 39.2 kB

  • Original 48.5 kB
  • After minification 38.9 kB
  • After compression 9.3 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. Fatema.jp needs all CSS files to be minified and compressed as it can save up to 39.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (33%)

Requests Now

120

After Optimization

81

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

Accessibility Review

fatema.jp accessibility score

84

Accessibility Issues

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

fatema.jp best practices score

67

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

SEO Factors

fatema.jp SEO score

88

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

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

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fatema.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 Fatema.jp main page’s claimed encoding is euc-jp. 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 Fatema. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: