Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

getnavi.jp

GetNavi web ゲットナビ | 「モノ・コト・暮らし」の深掘りレビュー&ニュース

Page Load Speed

15.9 sec in total

First Response

3.3 sec

Resources Loaded

11.7 sec

Page Rendered

994 ms

getnavi.jp screenshot

About Website

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

アイテム情報誌「GetNavi(ゲットナビ)」のウェブサイトです。デジタル製品や生活家電、ガジェットだけでなく、カルチャーやグルメなど、「いま知っておきたい」情報がたっぷり!

Visit getnavi.jp

Key Findings

We analyzed Getnavi.jp page load time and found that the first response time was 3.3 sec and then it took 12.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

getnavi.jp performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value17.2 s

0/100

10%

TBT (Total Blocking Time)

Value4,580 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.287

42/100

15%

TTI (Time to Interactive)

Value32.5 s

0/100

10%

Network Requests Diagram

getnavi.jp

3262 ms

common.css

507 ms

style.css

327 ms

modernizr.js

350 ms

custom-nextpage-style.css

379 ms

Our browser made a total of 147 requests to load all elements on the main page. We found that 59% of them (86 requests) were addressed to the original Getnavi.jp, 12% (17 requests) were made to Pbs.twimg.com and 7% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Getnavi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 448.9 kB (10%)

Content Size

4.5 MB

After Optimization

4.1 MB

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

HTML Optimization

-84%

Potential reduce by 81.3 kB

  • Original 97.2 kB
  • After minification 72.4 kB
  • After compression 15.9 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. This page needs HTML code to be minified as it can gain 24.8 kB, which is 26% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 81.3 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 189.2 kB

  • Original 4.2 MB
  • After minification 4.0 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. Get Navi images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 137.9 kB

  • Original 209.2 kB
  • After minification 203.0 kB
  • After compression 71.3 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 137.9 kB or 66% of the original size.

CSS Optimization

-81%

Potential reduce by 40.6 kB

  • Original 49.9 kB
  • After minification 35.5 kB
  • After compression 9.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. Getnavi.jp needs all CSS files to be minified and compressed as it can save up to 40.6 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

146

After Optimization

114

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

Accessibility Review

getnavi.jp accessibility score

88

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

Buttons do not have an accessible name

High

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

High

Links do not have a discernible name

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.

Best Practices

getnavi.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

getnavi.jp SEO score

98

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Getnavi.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 Getnavi.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 data is detected on the main page of Get Navi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: