Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fantastick.jp

デジタルをファッションに | 株式会社Fantastick

Page Load Speed

32.2 sec in total

First Response

567 ms

Resources Loaded

31.1 sec

Page Rendered

515 ms

fantastick.jp screenshot

About Website

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

IQOS・glo・Ploom TECH等の加熱式電子たばこや、iPhoneをはじめとするスマートフォン関連アクセサリーの企画・生産・販売を行う、株式会社Fantastick(ファンタスティック)のホームページです。

Visit fantastick.jp

Key Findings

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

fantastick.jp performance score

0

Network Requests Diagram

fantastick.jp

567 ms

www.fantastick.jp

10999 ms

import.css

332 ms

style.css

353 ms

jquery-1.6.4.min.js

1083 ms

Our browser made a total of 242 requests to load all elements on the main page. We found that 75% of them (181 requests) were addressed to the original Fantastick.jp, 6% (14 requests) were made to Paynetcafe.com and 5% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (11 sec) belongs to the original domain Fantastick.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (32%)

Content Size

3.9 MB

After Optimization

2.6 MB

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

HTML Optimization

-92%

Potential reduce by 178.0 kB

  • Original 193.2 kB
  • After minification 154.7 kB
  • After compression 15.2 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 38.6 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 178.0 kB or 92% of the original size.

Image Optimization

-24%

Potential reduce by 761.2 kB

  • Original 3.2 MB
  • After minification 2.5 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. Obviously, Fantastick needs image optimization as it can save up to 761.2 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 227.4 kB

  • Original 349.1 kB
  • After minification 294.6 kB
  • After compression 121.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 227.4 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 86.9 kB

  • Original 106.2 kB
  • After minification 76.1 kB
  • After compression 19.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. Fantastick.jp needs all CSS files to be minified and compressed as it can save up to 86.9 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

237

After Optimization

172

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

SEO Factors

fantastick.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fantastick.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 Fantastick.jp 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 description is not detected on the main page of Fantastick. 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: