Tools & Wizards About Us

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

tripnote.jp

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

Page Load Speed

7 sec in total

First Response

1.9 sec

Resources Loaded

4.6 sec

Page Rendered

520 ms

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.9 sec and then it took 5.1 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

tripnote.jp performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value23.5 s

0/100

25%

SI (Speed Index)

Value20.9 s

0/100

10%

TBT (Total Blocking Time)

Value3,700 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.531

14/100

15%

TTI (Time to Interactive)

Value37.9 s

0/100

10%

Network Requests Diagram

tripnote.jp

1876 ms

base2.css

632 ms

top2.css

669 ms

8adea335ce.js

127 ms

common.js

632 ms

Our browser made a total of 165 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tripnote.jp, 30% (50 requests) were made to D340eiag32bpum.cloudfront.net and 14% (23 requests) were made to D3js6t9w4ak4j.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Tripnote.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 524.9 kB (14%)

Content Size

3.6 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tripnote.jp main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 206.8 kB

  • Original 255.2 kB
  • After minification 254.7 kB
  • After compression 48.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 206.8 kB or 81% of the original size.

Image Optimization

-9%

Potential reduce by 211.3 kB

  • Original 2.5 MB
  • After minification 2.3 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. Tripnote images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 93.2 kB

  • Original 882.4 kB
  • After minification 872.8 kB
  • After compression 789.1 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 93.2 kB or 11% of the original size.

CSS Optimization

-58%

Potential reduce by 13.6 kB

  • Original 23.6 kB
  • After minification 19.0 kB
  • After compression 10.0 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 13.6 kB or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (32%)

Requests Now

157

After Optimization

107

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 157 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 38 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

tripnote.jp accessibility score

76

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Missing source maps for large first-party JavaScript

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

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: