Tools & Wizards About Us
tripnote.jp screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

tripnote.jp

トリップノート - みんなでつくる旅行ガイドブック

Page Load Speed

8 sec in total

First Response

1.2 sec

Resources Loaded

6.2 sec

Page Rendered

636 ms

tripnote.jp screenshot

About Website

Welcome to tripnote.jp homepage info - get ready to check Tripnote best content for Japan right away, or after learning these important things about tripnote.jp

みんなでつくる旅行・観光・おでかけガイドブック。現地取材のトラベルライターによるオリジナル旅行記事と、旅行好きなトラベラー会員による旅フォトをもとに、みんなで旅行ガイドブックを作っていくためのサービスです。塗りつぶし地図、旅のしおり、旅フォトなど旅を楽しむ機能が盛りだくさん。

Visit tripnote.jp

Key Findings

We analyzed Tripnote.jp page load time and found that the first response time was 1.2 sec and then it took 6.8 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

tripnote.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value2,370 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.492

17/100

15%

TTI (Time to Interactive)

Value26.0 s

0/100

10%

Network Requests Diagram

tripnote.jp

1164 ms

common.css

1316 ms

icon.css

692 ms

common.js

695 ms

jquery.min.js

66 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tripnote.jp, 52% (22 requests) were made to D340eiag32bpum.cloudfront.net and 26% (11 requests) were made to S3-tripnote-jp.s3-ap-northeast-1.amazonaws.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source D340eiag32bpum.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 265.8 kB (21%)

Content Size

1.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 29.3 kB

  • Original 41.0 kB
  • After minification 41.0 kB
  • After compression 11.8 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 29.3 kB or 71% of the original size.

Image Optimization

-11%

Potential reduce by 123.8 kB

  • Original 1.1 MB
  • After minification 961.4 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, Tripnote needs image optimization as it can save up to 123.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-42%

Potential reduce by 19.2 kB

  • Original 45.9 kB
  • After minification 36.3 kB
  • After compression 26.6 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 19.2 kB or 42% of the original size.

CSS Optimization

-88%

Potential reduce by 93.5 kB

  • Original 106.5 kB
  • After minification 86.4 kB
  • After compression 13.1 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. Tripnote.jp needs all CSS files to be minified and compressed as it can save up to 93.5 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (15%)

Requests Now

41

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tripnote.jp

tripnote.jp

1164 ms

common.css

common.css

1316 ms

icon.css

icon.css

692 ms

common.js

common.js

695 ms

jquery.min.js

jquery.min.js

66 ms

jquery.blockUI.js

jquery.blockUI.js

846 ms

jquery-contained-sticky-scroll.js

jquery-contained-sticky-scroll.js

689 ms

analytics.js

analytics.js

216 ms

4165-1hYPfFbachK00KRZd3YJ_mdm_re.jpg

4165-1hYPfFbachK00KRZd3YJ_mdm_re.jpg

1598 ms

logo.png

logo.png

199 ms

bookmark18.png

bookmark18.png

200 ms

download-app-store.png

download-app-store.png

197 ms

2903-QS7QY1A3AFfYcCwNK1AS_mdm_re.jpg

2903-QS7QY1A3AFfYcCwNK1AS_mdm_re.jpg

1486 ms

6457-6FE45kEwH6MAcB0sLhPu_sml_re.jpg

6457-6FE45kEwH6MAcB0sLhPu_sml_re.jpg

1025 ms

6668-HbCMJQsMYJwYGawYZQQG_sml_re.jpg

6668-HbCMJQsMYJwYGawYZQQG_sml_re.jpg

1011 ms

6674-tG3WJZRyLe0YRDPenB4t_sml_re.jpg

6674-tG3WJZRyLe0YRDPenB4t_sml_re.jpg

1036 ms

6485-Uucs1mrb32Gn6DYCPB9J_sml_re.jpg

6485-Uucs1mrb32Gn6DYCPB9J_sml_re.jpg

1064 ms

6373-sraqcY2VK7HK1XXzXVW3_sml_re.jpg

6373-sraqcY2VK7HK1XXzXVW3_sml_re.jpg

1966 ms

6193-KsMLG0ssRNF5g17kczB2_sml_re.jpg

6193-KsMLG0ssRNF5g17kczB2_sml_re.jpg

1854 ms

6076-KCtgsunCaXY0gTExGubU_sml_re.jpg

6076-KCtgsunCaXY0gTExGubU_sml_re.jpg

1041 ms

6266-KLddwd5eVXSsVPum7ZUY_sml_re.jpg

6266-KLddwd5eVXSsVPum7ZUY_sml_re.jpg

1049 ms

6148-0gv3D7Vhk9Zewb0aMM6m_sml_re.jpg

6148-0gv3D7Vhk9Zewb0aMM6m_sml_re.jpg

1973 ms

5401-tFe7hZDawkcDQLf91MLe_sml_re.jpg

5401-tFe7hZDawkcDQLf91MLe_sml_re.jpg

1843 ms

6143-RMW0Khq3ZN9MRmEZLm33_sml_re.jpg

6143-RMW0Khq3ZN9MRmEZLm33_sml_re.jpg

2267 ms

6016-nC3k11rHkkn7UXppzdMX_sml_re.jpg

6016-nC3k11rHkkn7UXppzdMX_sml_re.jpg

2400 ms

6052-1NhqKCHZBS2SRJqQqfPz_sml_re.jpg

6052-1NhqKCHZBS2SRJqQqfPz_sml_re.jpg

2667 ms

5958-kTtbQCsmWNVN3fDnQq4h_sml_re.jpg

5958-kTtbQCsmWNVN3fDnQq4h_sml_re.jpg

2617 ms

5914-q0uMwwKLBNLVLfVm0zkS_sml_re.jpg

5914-q0uMwwKLBNLVLfVm0zkS_sml_re.jpg

3004 ms

6083-P6deMT5nAqZswME21G4K_sml_re.jpg

6083-P6deMT5nAqZswME21G4K_sml_re.jpg

2770 ms

6013-enUEGtEYAPHMRaxFCwkc_sml_re.jpg

6013-enUEGtEYAPHMRaxFCwkc_sml_re.jpg

3202 ms

5930-LreNJXYsZ0Ykkm1tRhMb_sml_re.jpg

5930-LreNJXYsZ0Ykkm1tRhMb_sml_re.jpg

3183 ms

5869-qfbu63rahZDVeCZb7DPf_sml_re.jpg

5869-qfbu63rahZDVeCZb7DPf_sml_re.jpg

2612 ms

5683-RKKGBmYv7rzvFce3Sfn3_sml_re.jpg

5683-RKKGBmYv7rzvFce3Sfn3_sml_re.jpg

2615 ms

sdk.js

sdk.js

510 ms

image.png

image.png

712 ms

overseas300x200.png

overseas300x200.png

231 ms

domestic300x200.png

domestic300x200.png

319 ms

linkid.js

linkid.js

10 ms

collect

collect

22 ms

collect

collect

56 ms

144 ms

xd_arbiter.php

xd_arbiter.php

428 ms

Accessibility Review

tripnote.jp accessibility score

63

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tripnote.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

tripnote.jp SEO score

78

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 uses 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 Tripnote.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 Tripnote.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

tripnote.jp

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