Tools & Wizards About Us
hanayanomae.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hanayanomae.com

Page Load Speed

7.9 sec in total

First Response

1.4 sec

Resources Loaded

6 sec

Page Rendered

510 ms

hanayanomae.com screenshot

About Website

Welcome to hanayanomae.com homepage info - get ready to check Hanayanomae best content right away, or after learning these important things about hanayanomae.com

いつもキレイをカンタンに。花やの前の美容室は山梨県と中目黒の美容室です。 山梨本店、国母店、南アルプス店、十日市場店、甲斐篠原店、中目黒店、6つの店舗でお待ちしております。

Visit hanayanomae.com

Key Findings

We analyzed Hanayanomae.com page load time and found that the first response time was 1.4 sec and then it took 6.5 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

hanayanomae.com performance score

0

Network Requests Diagram

hanayanomae.com

1364 ms

css

24 ms

import.css

337 ms

slider.css

346 ms

xSlider.css

346 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 70% of them (76 requests) were addressed to the original Hanayanomae.com, 7% (8 requests) were made to Platform.twitter.com and 5% (5 requests) were made to O.twimg.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Hanayanomae.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 468.1 kB (14%)

Content Size

3.5 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hanayanomae.com main page is 3.5 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 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 46.9 kB

  • Original 56.4 kB
  • After minification 38.8 kB
  • After compression 9.5 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 17.6 kB, which is 31% 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 46.9 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 44.7 kB

  • Original 2.9 MB
  • After minification 2.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. Hanayanomae images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 300.8 kB

  • Original 426.8 kB
  • After minification 413.6 kB
  • After compression 126.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 300.8 kB or 70% of the original size.

CSS Optimization

-85%

Potential reduce by 75.8 kB

  • Original 88.8 kB
  • After minification 77.3 kB
  • After compression 13.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. Hanayanomae.com needs all CSS files to be minified and compressed as it can save up to 75.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (23%)

Requests Now

104

After Optimization

80

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hanayanomae.com

hanayanomae.com

1364 ms

css

css

24 ms

import.css

import.css

337 ms

slider.css

slider.css

346 ms

xSlider.css

xSlider.css

346 ms

ore3.js

ore3.js

732 ms

ore3_scroller.js

ore3_scroller.js

548 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

1326 ms

jquery-ui-1.9.2.min.js

jquery-ui-1.9.2.min.js

1879 ms

function.js

function.js

729 ms

jquery.slider.js

jquery.slider.js

731 ms

jquery.xSlider.js

jquery.xSlider.js

864 ms

reset.css

reset.css

586 ms

common.css

common.css

571 ms

style.css

style.css

948 ms

s_retargeting.js

s_retargeting.js

530 ms

conversion.js

conversion.js

18 ms

analytics.js

analytics.js

13 ms

sdk.js

sdk.js

163 ms

btn_reserve.png

btn_reserve.png

229 ms

logo.gif

logo.gif

218 ms

btn_fb.gif

btn_fb.gif

218 ms

btn_twitter.gif

btn_twitter.gif

218 ms

nav01.gif

nav01.gif

219 ms

nav02.gif

nav02.gif

219 ms

nav03.gif

nav03.gif

394 ms

nav04.gif

nav04.gif

396 ms

nav05.gif

nav05.gif

388 ms

nav06.gif

nav06.gif

389 ms

ico_top_arrow.gif

ico_top_arrow.gif

394 ms

ico_arrow.png

ico_arrow.png

382 ms

photo01.jpg

photo01.jpg

1218 ms

photo04.jpg

photo04.jpg

1971 ms

photo05.jpg

photo05.jpg

2185 ms

photo06.jpg

photo06.jpg

1814 ms

photo07.jpg

photo07.jpg

1308 ms

bg_contents.gif

bg_contents.gif

587 ms

photo01.jpg

photo01.jpg

954 ms

photo02.jpg

photo02.jpg

1141 ms

photo03.jpg

photo03.jpg

1330 ms

photo04.jpg

photo04.jpg

1388 ms

photo05.jpg

photo05.jpg

1495 ms

photo06.jpg

photo06.jpg

1518 ms

bg_recommend.gif

bg_recommend.gif

2054 ms

photo05.jpg

photo05.jpg

1688 ms

photo04.jpg

photo04.jpg

1710 ms

photo03.jpg

photo03.jpg

1874 ms

img_phone.gif

img_phone.gif

1898 ms

txt_apl.gif

txt_apl.gif

1992 ms

img_apl_map.gif

img_apl_map.gif

2062 ms

img_apl_girl.gif

img_apl_girl.gif

2085 ms

img_apl_logo.gif

img_apl_logo.gif

2143 ms

img_appstore.gif

img_appstore.gif

2171 ms

img_googleplay.gif

img_googleplay.gif

2222 ms

btn_more.gif

btn_more.gif

2246 ms

widgets.js

widgets.js

16 ms

collect

collect

22 ms

MViwy4K6e56oHcyeMzjbCQ.ttf

MViwy4K6e56oHcyeMzjbCQ.ttf

20 ms

130 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

79 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

83 ms

175 ms

28.jpg

28.jpg

2063 ms

ico_1.png

ico_1.png

2106 ms

27.jpg

27.jpg

2146 ms

26.jpg

26.jpg

2149 ms

ico_4.png

ico_4.png

2179 ms

xd_arbiter.php

xd_arbiter.php

159 ms

xd_arbiter.php

xd_arbiter.php

284 ms

25.jpg

25.jpg

2222 ms

ga-audiences

ga-audiences

99 ms

syndication

syndication

134 ms

469737206915923969

469737206915923969

292 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

35 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

51 ms

49 ms

bg_concept.jpg

bg_concept.jpg

3020 ms

ttl_h2.png

ttl_h2.png

2280 ms

btn_more.png

btn_more.png

2155 ms

photo_style_book.jpg

photo_style_book.jpg

2156 ms

btn_more.png

btn_more.png

2172 ms

photo_seijin.jpg

photo_seijin.jpg

2239 ms

proxy.jpg

proxy.jpg

256 ms

proxy.jpg

proxy.jpg

400 ms

proxy.jpg

proxy.jpg

344 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

5 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

6 ms

photo_recruit.jpg

photo_recruit.jpg

2141 ms

c51ac55fa77e48467b01178b77315207_normal.png

c51ac55fa77e48467b01178b77315207_normal.png

302 ms

Mv4fgDci_normal.jpg

Mv4fgDci_normal.jpg

328 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

38 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

90 ms

proxy.jpg

proxy.jpg

178 ms

proxy.jpg

proxy.jpg

230 ms

ico_fb.gif

ico_fb.gif

1771 ms

jot.html

jot.html

2 ms

ico_twitter.gif

ico_twitter.gif

1591 ms

photo05.jpg

photo05.jpg

1602 ms

photo02.jpg

photo02.jpg

1532 ms

photo03.jpg

photo03.jpg

1568 ms

photo04.jpg

photo04.jpg

1523 ms

btn_pagetop.gif

btn_pagetop.gif

1408 ms

bg_footer.gif

bg_footer.gif

1485 ms

ico_arrow.png

ico_arrow.png

1326 ms

nav01_on.gif

nav01_on.gif

1365 ms

nav02_on.gif

nav02_on.gif

1259 ms

nav03_on.gif

nav03_on.gif

1211 ms

nav05_on.gif

nav05_on.gif

1290 ms

SEO Factors

hanayanomae.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hanayanomae.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Hanayanomae.com 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

hanayanomae.com

Open Graph data is detected on the main page of Hanayanomae. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: