Tools & Wizards About Us
taya-blog.jp screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

taya-blog.jp

美容院・美容室・ヘアサロン｜TAYA NET [タヤ ネット]

Page Load Speed

7.6 sec in total

First Response

1.6 sec

Resources Loaded

4.7 sec

Page Rendered

1.3 sec

taya-blog.jp screenshot

About Website

Welcome to taya-blog.jp homepage info - get ready to check TAYA Blog best content right away, or after learning these important things about taya-blog.jp

ヘアサロン（美容院・美容室）を全国に展開しているTAYA（田谷）グループのホームページです。

Visit taya-blog.jp

Key Findings

We analyzed Taya-blog.jp page load time and found that the first response time was 1.6 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

taya-blog.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.209

59/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

taya-blog.jp

1551 ms

reset.css

844 ms

tayablog.css

1192 ms

jquery-1.7.min.js

1881 ms

jquery.bgswitcher.js

1286 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 88% of them (38 requests) were addressed to the original Taya-blog.jp, 7% (3 requests) were made to Tayanet.sakura.ne.jp and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Taya-blog.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 200.0 kB (10%)

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 87.0 kB

  • Original 98.0 kB
  • After minification 95.8 kB
  • After compression 11.0 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 87.0 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 7.7 kB

  • Original 1.7 MB
  • After minification 1.7 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. TAYA Blog images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 100.9 kB

  • Original 157.4 kB
  • After minification 153.0 kB
  • After compression 56.5 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 100.9 kB or 64% of the original size.

CSS Optimization

-73%

Potential reduce by 4.4 kB

  • Original 6.0 kB
  • After minification 4.7 kB
  • After compression 1.6 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. Taya-blog.jp needs all CSS files to be minified and compressed as it can save up to 4.4 kB or 73% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

42

After Optimization

42

  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TAYA Blog. According to our analytics all requests are already optimized.

Network Requests Diagram

taya-blog.jp

taya-blog.jp

1551 ms

reset.css

reset.css

844 ms

tayablog.css

tayablog.css

1192 ms

jquery-1.7.min.js

jquery-1.7.min.js

1881 ms

jquery.bgswitcher.js

jquery.bgswitcher.js

1286 ms

analytics.js

analytics.js

23 ms

header_bar.png

header_bar.png

661 ms

spade.gif

spade.gif

531 ms

telephone.gif

telephone.gif

536 ms

soon.gif

soon.gif

537 ms

20160319_1-thumb-400x400-44415.jpg

20160319_1-thumb-400x400-44415.jpg

564 ms

20160318_8-thumb-550x309-44390.jpg

20160318_8-thumb-550x309-44390.jpg

176 ms

20160318_4-thumb-400x400-44394.jpg

20160318_4-thumb-400x400-44394.jpg

517 ms

20160318_10-thumb-400x400-44409.jpg

20160318_10-thumb-400x400-44409.jpg

350 ms

20160318_11-thumb-400x400-44412.jpg

20160318_11-thumb-400x400-44412.jpg

1090 ms

20160318_9-thumb-400x400-44397.jpg

20160318_9-thumb-400x400-44397.jpg

1094 ms

20160318_7-thumb-400x400-44400.jpg

20160318_7-thumb-400x400-44400.jpg

525 ms

20160318_6-thumb-400x400-44406.jpg

20160318_6-thumb-400x400-44406.jpg

855 ms

20160318_5-thumb-400x400-44403.jpg

20160318_5-thumb-400x400-44403.jpg

698 ms

20160318_1-thumb-350x464-44381.jpg

20160318_1-thumb-350x464-44381.jpg

751 ms

20160318_2-thumb-350x464-44384.jpg

20160318_2-thumb-350x464-44384.jpg

973 ms

20160318_3-thumb-400x301-44387.jpg

20160318_3-thumb-400x301-44387.jpg

871 ms

20160317_11.jpg

20160317_11.jpg

1128 ms

20160317_12.JPG

20160317_12.JPG

1196 ms

20160317_13.jpg

20160317_13.jpg

1047 ms

20160317_1-thumb-400x400-44375.jpg

20160317_1-thumb-400x400-44375.jpg

1303 ms

footer_logo.jpg

footer_logo.jpg

1218 ms

collect

collect

12 ms

icon_tayanet.png

icon_tayanet.png

1162 ms

icon_creative.png

icon_creative.png

1166 ms

icon_bjob.png

icon_bjob.png

1206 ms

icon_fb.png

icon_fb.png

1258 ms

icon_tw.png

icon_tw.png

1281 ms

main_chiba.jpg

main_chiba.jpg

2075 ms

main_tenjin.jpg

main_tenjin.jpg

1717 ms

main_machida.jpg

main_machida.jpg

1532 ms

main_ginza.jpg

main_ginza.jpg

1581 ms

main_shinsaibashi.jpg

main_shinsaibashi.jpg

1774 ms

main_kinshicho.jpg

main_kinshicho.jpg

1457 ms

main_kashii.jpg

main_kashii.jpg

2143 ms

main_kumamoto.jpg

main_kumamoto.jpg

1865 ms

main_herbis.jpg

main_herbis.jpg

1956 ms

main_cp_machida.jpg

main_cp_machida.jpg

2083 ms

Accessibility Review

taya-blog.jp accessibility score

98

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

Links do not have a discernible name

Best Practices

taya-blog.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

taya-blog.jp SEO score

87

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Taya-blog.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 Taya-blog.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

taya-blog.jp

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