Tools & Wizards About Us
travelstandard.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

travelstandard.net

企業情報 | 海外旅行・ツアーはトラベルスタンダードジャパン

Page Load Speed

5.6 sec in total

First Response

1.2 sec

Resources Loaded

4.3 sec

Page Rendered

185 ms

travelstandard.net screenshot

About Website

Click here to check amazing Travelstandard content for Japan. Otherwise, check out these important facts you probably never knew about travelstandard.net

弊社はお客様の大切な時間をご提供する旅行会社として、海外旅行の知識と経験が豊富なベテランスタッフを揃えております。現状に満足する事なく常に最新情報を収集し共有する事で、お客様へ最新の現地情報をご提供する事もできます。また弊社をお選び頂いたお客様に安心して楽しんで頂く為に、旅行会社として最上位の第一種旅行業の免許を保持しております。これは観光庁の厳しい審査を通過し、お客様に安心して海外旅行を楽しんで...

Visit travelstandard.net

Key Findings

We analyzed Travelstandard.net page load time and found that the first response time was 1.2 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

travelstandard.net performance score

0

Network Requests Diagram

www.travelstandard.net

1188 ms

style.css

622 ms

navi.css

314 ms

add.css

330 ms

heightLine.js

343 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 63% of them (20 requests) were addressed to the original Travelstandard.net, 6% (2 requests) were made to Hp.travelstandard.net and 6% (2 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Travelstandard.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 442.7 kB (54%)

Content Size

812.7 kB

After Optimization

370.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Travelstandard.net main page is 812.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 523.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 49.9 kB

  • Original 68.4 kB
  • After minification 62.3 kB
  • After compression 18.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. 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 49.9 kB or 73% of the original size.

Image Optimization

-17%

Potential reduce by 31.2 kB

  • Original 180.5 kB
  • After minification 149.3 kB

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. Obviously, Travelstandard needs image optimization as it can save up to 31.2 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 327.6 kB

  • Original 523.6 kB
  • After minification 521.3 kB
  • After compression 196.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 327.6 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 34.0 kB

  • Original 40.2 kB
  • After minification 25.4 kB
  • After compression 6.2 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. Travelstandard.net needs all CSS files to be minified and compressed as it can save up to 34.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (47%)

Requests Now

30

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.travelstandard.net

www.travelstandard.net

1188 ms

style.css

style.css

622 ms

navi.css

navi.css

314 ms

add.css

add.css

330 ms

heightLine.js

heightLine.js

343 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

1281 ms

jquery-1.3.2.js

jquery-1.3.2.js

51 ms

jquery.color.js

jquery.color.js

516 ms

addthis_widget.js

addthis_widget.js

11 ms

map_rev.png

map_rev.png

925 ms

side_top.png

side_top.png

551 ms

logo_travelwith.png

logo_travelwith.png

552 ms

iconSNS_fb.png

iconSNS_fb.png

552 ms

iconSNS_twitter.png

iconSNS_twitter.png

552 ms

iconSNS_ameblo.png

iconSNS_ameblo.png

553 ms

iconSNS_pinterest.png

iconSNS_pinterest.png

553 ms

ttll_top.png

ttll_top.png

658 ms

gtm.js

gtm.js

106 ms

bg_side.jpg

bg_side.jpg

666 ms

bg_highlights.png

bg_highlights.png

1339 ms

icon_vBlkDown.png

icon_vBlkDown.png

593 ms

parts_hr.png

parts_hr.png

603 ms

parts_leftRadi.gif

parts_leftRadi.gif

594 ms

parts_rightRadi.gif

parts_rightRadi.gif

908 ms

bg_navHeadIe.png

bg_navHeadIe.png

916 ms

300lo.json

300lo.json

30 ms

dc.js

dc.js

45 ms

conversion_async.js

conversion_async.js

43 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

34 ms

57 ms

__utm.gif

__utm.gif

20 ms

42 ms

SEO Factors

travelstandard.net SEO score

0

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 Travelstandard.net 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 Travelstandard.net 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

travelstandard.net

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