Tools & Wizards About Us
insolite.co.jp screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

insolite.co.jp

INSOLITE - 広尾の美容院 アンソリット・ボーテ（麻布・渋谷地区）

Page Load Speed

6.9 sec in total

First Response

530 ms

Resources Loaded

5.5 sec

Page Rendered

877 ms

insolite.co.jp screenshot

About Website

Welcome to insolite.co.jp homepage info - get ready to check INSOLITE best content right away, or after learning these important things about insolite.co.jp

INSOLITE 広尾の美容院｜アンソリット・ボーテ　広尾の美容院 アンソリット・ボーテ（麻布・渋谷地区） 広尾の美容院 gアンソリット 広尾・麻布・渋谷地区の美容室 ヘッドスパ 広尾駅徒歩3分

Visit insolite.co.jp

Key Findings

We analyzed Insolite.co.jp page load time and found that the first response time was 530 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

insolite.co.jp performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

insolite.co.jp

530 ms

insolite.co.jp

1147 ms

pc_loader.css

174 ms

jquery.min.js

24 ms

pace.min.js

346 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 96% of them (70 requests) were addressed to the original Insolite.co.jp, 1% (1 request) were made to Ajax.googleapis.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Insolite.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 222.2 kB (3%)

Content Size

7.8 MB

After Optimization

7.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Insolite.co.jp main page is 7.8 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 7.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 29.9 kB

  • Original 35.6 kB
  • After minification 31.7 kB
  • After compression 5.7 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 3.9 kB, which is 11% 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 29.9 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 140.5 kB

  • Original 7.5 MB
  • After minification 7.4 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. INSOLITE images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 33.4 kB

  • Original 225.4 kB
  • After minification 225.4 kB
  • After compression 192.0 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 33.4 kB or 15% of the original size.

CSS Optimization

-76%

Potential reduce by 18.3 kB

  • Original 24.2 kB
  • After minification 18.6 kB
  • After compression 5.9 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. Insolite.co.jp needs all CSS files to be minified and compressed as it can save up to 18.3 kB or 76% of the original size.

Requests Breakdown

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

Requests Now

70

After Optimization

51

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

insolite.co.jp

insolite.co.jp

530 ms

insolite.co.jp

insolite.co.jp

1147 ms

pc_loader.css

pc_loader.css

174 ms

jquery.min.js

jquery.min.js

24 ms

pace.min.js

pace.min.js

346 ms

jquery.inview.min.js

jquery.inview.min.js

517 ms

ofi.min.js

ofi.min.js

520 ms

pc_common.js

pc_common.js

521 ms

css2

css2

39 ms

pc_common.css

pc_common.css

554 ms

pc_top.css

pc_top.css

553 ms

js

js

72 ms

slick.min.js

slick.min.js

613 ms

pixi.min.js

pixi.min.js

1208 ms

TweenMax.min.js

TweenMax.min.js

1034 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

689 ms

pc_top.js

pc_top.js

701 ms

logo.svg

logo.svg

179 ms

btn_h_menu-pc.svg

btn_h_menu-pc.svg

181 ms

h_menu_salon_sep-pc.png

h_menu_salon_sep-pc.png

255 ms

logo_insolite_beaute_w.svg

logo_insolite_beaute_w.svg

269 ms

logo_g_insolite_w.svg

logo_g_insolite_w.svg

355 ms

btn_is.svg

btn_is.svg

357 ms

logo_w.svg

logo_w.svg

429 ms

800x1200.jpg

800x1200.jpg

969 ms

btn_h_menu_close-sp.svg

btn_h_menu_close-sp.svg

532 ms

h_reserve_sep-pc.png

h_reserve_sep-pc.png

534 ms

top01.jpg

top01.jpg

2999 ms

top02.jpg

top02.jpg

1632 ms

LINE_ALBUM_230419_18.jpg

LINE_ALBUM_230419_18.jpg

1587 ms

thumb.php

thumb.php

889 ms

thumb.php

thumb.php

946 ms

thumb.php

thumb.php

1068 ms

thumb.php

thumb.php

1121 ms

thumb.php

thumb.php

1319 ms

thumb.php

thumb.php

1250 ms

thumb.php

thumb.php

1811 ms

thumb.php

thumb.php

1431 ms

thumb.php

thumb.php

1497 ms

logo_g_insolite.svg

logo_g_insolite.svg

1608 ms

icon_map.png

icon_map.png

1673 ms

LINE_ALBUM_230419_17.jpg

LINE_ALBUM_230419_17.jpg

1769 ms

logo_g_insolite_w.svg

logo_g_insolite_w.svg

1785 ms

salon_sep-pc.jpg

salon_sep-pc.jpg

1803 ms

logo_insolite_beaute.svg

logo_insolite_beaute.svg

1849 ms

LINE_ALBUM_230419_3(1).jpg

LINE_ALBUM_230419_3(1).jpg

1952 ms

logo_insolite_beaute_w.svg

logo_insolite_beaute_w.svg

1962 ms

thumb.php

thumb.php

1976 ms

thumb.php

thumb.php

1950 ms

thumb.php

thumb.php

1948 ms

thumb.php

thumb.php

2043 ms

thumb.php

thumb.php

1965 ms

thumb.php

thumb.php

1974 ms

thumb.php

thumb.php

1906 ms

thumb.php

thumb.php

1939 ms

thumb.php

thumb.php

1958 ms

38622477.BE0A459267E54594B88B82BA2E7000B9.19061010.jpeg

38622477.BE0A459267E54594B88B82BA2E7000B9.19061010.jpeg

2496 ms

IMG_5827-scaled.jpeg

IMG_5827-scaled.jpeg

2081 ms

S__102121484_0.jpg

S__102121484_0.jpg

1913 ms

S__25608223_0.jpg

S__25608223_0.jpg

2028 ms

IMG_5806-scaled.jpeg

IMG_5806-scaled.jpeg

2151 ms

68629980-6697-4FC7-9347-D91A6AF97F36-scaled.jpg

68629980-6697-4FC7-9347-D91A6AF97F36-scaled.jpg

2038 ms

S__102047773_0.jpg

S__102047773_0.jpg

1798 ms

S__102031373.jpg

S__102031373.jpg

1967 ms

f_salon_sep-pc.png

f_salon_sep-pc.png

1917 ms

f_icon_map.png

f_icon_map.png

1816 ms

f_map-pc.png

f_map-pc.png

1764 ms

clouds.jpg

clouds.jpg

1781 ms

top01.jpg

top01.jpg

1787 ms

top02.jpg

top02.jpg

1649 ms

top01.jpg

top01.jpg

1612 ms

top02.jpg

top02.jpg

1638 ms

undefined

undefined

1616 ms

Accessibility Review

insolite.co.jp accessibility score

92

Accessibility Issues

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

Links do not have a discernible name

Best Practices

insolite.co.jp best practices score

83

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

SEO Factors

insolite.co.jp SEO score

83

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Insolite.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Insolite.co.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

insolite.co.jp

Open Graph description is not detected on the main page of INSOLITE. 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: