Tools & Wizards About Us
tokyo-strings.co.jp screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

tokyo-strings.co.jp

TokyoStrings - top page

Page Load Speed

4.8 sec in total

First Response

978 ms

Resources Loaded

3.6 sec

Page Rendered

160 ms

tokyo-strings.co.jp screenshot

About Website

Visit tokyo-strings.co.jp now to see the best up-to-date Tokyo Strings content and also check out these interesting facts you probably never knew about tokyo-strings.co.jp

The store specializing in stringed instruments which are the most famous in Japan is [TOKYO-STRING]

Visit tokyo-strings.co.jp

Key Findings

We analyzed Tokyo-strings.co.jp page load time and found that the first response time was 978 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

tokyo-strings.co.jp performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.118

85/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

tokyo-strings.co.jp

978 ms

reset.css

338 ms

base.css

339 ms

menu.css

519 ms

advanced-slider.css

347 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 62% of them (41 requests) were addressed to the original Tokyo-strings.co.jp, 27% (18 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Tokyo-strings.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 91.9 kB (6%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokyo-strings.co.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.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 18.9 kB

  • Original 24.3 kB
  • After minification 23.2 kB
  • After compression 5.4 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 18.9 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 4.1 kB

  • Original 1.4 MB
  • After minification 1.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. Tokyo Strings images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 52.1 kB

  • Original 133.2 kB
  • After minification 133.2 kB
  • After compression 81.2 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 52.1 kB or 39% of the original size.

CSS Optimization

-72%

Potential reduce by 16.8 kB

  • Original 23.2 kB
  • After minification 22.8 kB
  • After compression 6.4 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. Tokyo-strings.co.jp needs all CSS files to be minified and compressed as it can save up to 16.8 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (59%)

Requests Now

63

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tokyo-strings.co.jp

tokyo-strings.co.jp

978 ms

reset.css

reset.css

338 ms

base.css

base.css

339 ms

menu.css

menu.css

519 ms

advanced-slider.css

advanced-slider.css

347 ms

pixel.css

pixel.css

537 ms

thickbox.css

thickbox.css

515 ms

top-info.css

top-info.css

506 ms

slidebox.css

slidebox.css

508 ms

jquery.treeview.css

jquery.treeview.css

522 ms

15 ms

jquery.cookie.js

jquery.cookie.js

675 ms

jquery.treeview.js

jquery.treeview.js

677 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

687 ms

sprite.js

sprite.js

689 ms

jquery.scrollablecombo.js

jquery.scrollablecombo.js

693 ms

jquery.advancedSlider.min.js

jquery.advancedSlider.min.js

1413 ms

slidebox.js

slidebox.js

844 ms

jquery.contextmenu.r2.packed.js

jquery.contextmenu.r2.packed.js

844 ms

commonend.js

commonend.js

859 ms

loader.js

loader.js

21 ms

thickbox.js

thickbox.js

700 ms

jquery.min.js

jquery.min.js

21 ms

bg.jpg

bg.jpg

525 ms

menu_1.jpg

menu_1.jpg

525 ms

rogo_.jpg

rogo_.jpg

850 ms

mini_menu.png

mini_menu.png

182 ms

menu_2.jpg

menu_2.jpg

523 ms

main_bg.png

main_bg.png

334 ms

ms.jpg

ms.jpg

1236 ms

company.jpg

company.jpg

1486 ms

674 ms

viola2.jpg

viola2.jpg

1366 ms

top_info_bg.jpg

top_info_bg.jpg

1367 ms

twe_btn.jpg

twe_btn.jpg

845 ms

top_info_btn_en.jpg

top_info_btn_en.jpg

1013 ms

rogo_s.png

rogo_s.png

990 ms

ga.js

ga.js

38 ms

widgets.js

widgets.js

25 ms

loadingAnimation.gif

loadingAnimation.gif

1092 ms

down.png

down.png

1106 ms

f_icon.png

f_icon.png

1261 ms

footer_bg.png

footer_bg.png

1280 ms

arrows.png

arrows.png

1328 ms

buttons.png

buttons.png

1430 ms

preloader2.gif

preloader2.gif

1451 ms

__utm.gif

__utm.gif

24 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

45 ms

settings

settings

98 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

4 ms

TokyoString

TokyoString

74 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

6 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

29 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

36 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

34 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

33 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

35 ms

_buildManifest.js

_buildManifest.js

34 ms

_ssgManifest.js

_ssgManifest.js

81 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

10 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

11 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

7 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

16 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

10 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

16 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

9 ms

Accessibility Review

tokyo-strings.co.jp accessibility score

94

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

tokyo-strings.co.jp best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tokyo-strings.co.jp SEO score

69

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyo-strings.co.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Tokyo-strings.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

tokyo-strings.co.jp

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