Tools & Wizards About Us
expnavi.net screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

expnavi.net

のぞみ新幹線ナビ

Page Load Speed

4 sec in total

First Response

912 ms

Resources Loaded

3 sec

Page Rendered

97 ms

expnavi.net screenshot

About Website

Welcome to expnavi.net homepage info - get ready to check Expnavi best content for Japan right away, or after learning these important things about expnavi.net

のぞみ新幹線ナビは、新幹線に関する情報を発信しているサイトです。新幹線に関するオトクな情報やニュースを掲載しています。

Visit expnavi.net

Key Findings

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

Performance Metrics

expnavi.net performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value2,470 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.522

15/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

expnavi.jp

912 ms

jquery.mobile-1.1.0.min.css

30 ms

style.css

175 ms

jquery_mobile.css

349 ms

jquery-1.6.4.min.js

36 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Expnavi.net, 21% (3 requests) were made to Code.jquery.com and 14% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (912 ms) relates to the external source Expnavi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 36.3 kB (11%)

Content Size

335.0 kB

After Optimization

298.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Expnavi.net main page is 335.0 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. Only 10% of websites need less resources to load. Javascripts take 316.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 6.0 kB

  • Original 8.4 kB
  • After minification 8.3 kB
  • After compression 2.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 6.0 kB or 72% of the original size.

JavaScript Optimization

-9%

Potential reduce by 30.1 kB

  • Original 316.9 kB
  • After minification 316.9 kB
  • After compression 286.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 180 B

  • Original 9.7 kB
  • After minification 9.7 kB
  • After compression 9.6 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. Expnavi.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (54%)

Requests Now

13

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Expnavi. 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

expnavi.jp

expnavi.jp

912 ms

jquery.mobile-1.1.0.min.css

jquery.mobile-1.1.0.min.css

30 ms

style.css

style.css

175 ms

jquery_mobile.css

jquery_mobile.css

349 ms

jquery-1.6.4.min.js

jquery-1.6.4.min.js

36 ms

common.js

common.js

494 ms

common2.js

common2.js

497 ms

jquery.mobile.js

jquery.mobile.js

864 ms

js

js

97 ms

adsbygoogle.js

adsbygoogle.js

171 ms

ga.js

ga.js

120 ms

ajax-loader.gif

ajax-loader.gif

100 ms

show_ads_impl.js

show_ads_impl.js

378 ms

__utm.gif

__utm.gif

13 ms

Accessibility Review

expnavi.net accessibility score

100

Accessibility Issues

Best Practices

expnavi.net best practices score

83

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

Page has valid source maps

SEO Factors

expnavi.net SEO score

100

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Expnavi.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Expnavi.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

expnavi.net

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