Tools & Wizards About Us
ht-workshop.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ht-workshop.co.jp

株式会社フラオリタヒチ

Page Load Speed

760 ms in total

First Response

99 ms

Resources Loaded

586 ms

Page Rendered

75 ms

ht-workshop.co.jp screenshot

About Website

Visit ht-workshop.co.jp now to see the best up-to-date Ht Workshop content and also check out these interesting facts you probably never knew about ht-workshop.co.jp

フラ、タヒチアンダンスのワークショップ情報をお届けします。 フラワークショップ、タヒチアンダンスワークショップを定期的に開催しています。 招聘する講師は全て本場のクムフラ、ダンサーです。 その他にもハワイ、タヒチの情報をお届けします。

Visit ht-workshop.co.jp

Key Findings

We analyzed Ht-workshop.co.jp page load time and found that the first response time was 99 ms and then it took 661 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

ht-workshop.co.jp performance score

0

Network Requests Diagram

ht-workshop.co.jp

99 ms

www.ht-workshop.co.jp

80 ms

bt

90 ms

require.min.js

42 ms

main-r.min.js

46 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Ht-workshop.co.jp, 77% (30 requests) were made to Static.parastorage.com and 13% (5 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (280 ms) relates to the external source Static.parastorage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (77%)

Content Size

2.8 MB

After Optimization

654.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Ht-workshop.co.jp main page is 2.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. Javascripts take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 36.8 kB

  • Original 47.1 kB
  • After minification 46.9 kB
  • After compression 10.3 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 36.8 kB or 78% of the original size.

JavaScript Optimization

-77%

Potential reduce by 2.1 MB

  • Original 2.8 MB
  • After minification 2.7 MB
  • After compression 642.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 2.1 MB or 77% of the original size.

CSS Optimization

-77%

Potential reduce by 5.8 kB

  • Original 7.5 kB
  • After minification 6.0 kB
  • After compression 1.7 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. Ht-workshop.co.jp needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (78%)

Requests Now

37

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ht Workshop. 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 as a result speed up the page load time.

Network Requests Diagram

ht-workshop.co.jp

ht-workshop.co.jp

99 ms

www.ht-workshop.co.jp

www.ht-workshop.co.jp

80 ms

bt

bt

90 ms

require.min.js

require.min.js

42 ms

main-r.min.js

main-r.min.js

46 ms

viewer.css

viewer.css

43 ms

UpgradeBrowser.js

UpgradeBrowser.js

56 ms

dynamicmodel

dynamicmodel

9 ms

ugc-viewer

ugc-viewer

95 ms

bt

bt

219 ms

skins.min.js

skins.min.js

92 ms

components.min.js

components.min.js

68 ms

utils.min.js

utils.min.js

28 ms

core.min.js

core.min.js

90 ms

react-with-addons.min.js

react-with-addons.min.js

90 ms

lodash.min.js

lodash.min.js

89 ms

TweenMax.min.js

TweenMax.min.js

92 ms

layout.min.js

layout.min.js

93 ms

tpa.min.js

tpa.min.js

92 ms

fonts.min.js

fonts.min.js

89 ms

animations.min.js

animations.min.js

90 ms

swfobject.min.js

swfobject.min.js

88 ms

mousetrap.min.js

mousetrap.min.js

90 ms

tweenEngine.min.js

tweenEngine.min.js

91 ms

DrawSVGPlugin.min.js

DrawSVGPlugin.min.js

91 ms

react-dom.min.js

react-dom.min.js

206 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

207 ms

widgets.min.js

widgets.min.js

90 ms

experiment.js

experiment.js

207 ms

render.min.js

render.min.js

205 ms

wixappsCore.min.js

wixappsCore.min.js

208 ms

wixappsClassics.min.js

wixappsClassics.min.js

280 ms

wixappsBuilder.min.js

wixappsBuilder.min.js

207 ms

zepto.min.js

zepto.min.js

207 ms

color.min.js

color.min.js

205 ms

react-dom-server.min.js

react-dom-server.min.js

128 ms

bt

bt

97 ms

dc.js

dc.js

32 ms

bt

bt

37 ms

SEO Factors

ht-workshop.co.jp SEO score

0

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 Ht-workshop.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 Ht-workshop.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

ht-workshop.co.jp

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: