Tools & Wizards About Us
o2navi.net screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

o2navi.net

酸素カプセルナビ-ご近所の酸素カプセルを見つけよう！

Page Load Speed

2.8 sec in total

First Response

794 ms

Resources Loaded

1.9 sec

Page Rendered

135 ms

o2navi.net screenshot

About Website

Click here to check amazing O 2 Navi content for Japan. Otherwise, check out these important facts you probably never knew about o2navi.net

酸素カプセルナビは、全国の酸素カプセルができるお店を地域別・特徴別に検索・発見できるサイトです。

Visit o2navi.net

Key Findings

We analyzed O2navi.net page load time and found that the first response time was 794 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

o2navi.net performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

84/100

25%

SI (Speed Index)

Value3.2 s

91/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

o2navi.net

794 ms

styles.css

716 ms

mt.js

558 ms

534 ms

header.gif

347 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 79% of them (11 requests) were addressed to the original O2navi.net, 14% (2 requests) were made to Google-analytics.com and 7% (1 request) were made to Oo.a.swcs.jp. The less responsive or slowest element that took the longest time to load (794 ms) belongs to the original domain O2navi.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 17.6 kB (44%)

Content Size

40.2 kB

After Optimization

22.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of O2navi.net main page is 40.2 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 20.9 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 7.4 kB

  • Original 10.1 kB
  • After minification 9.4 kB
  • After compression 2.7 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 7.4 kB or 74% of the original size.

JavaScript Optimization

-13%

Potential reduce by 2.7 kB

  • Original 20.9 kB
  • After minification 20.0 kB
  • After compression 18.2 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 2.7 kB or 13% of the original size.

CSS Optimization

-81%

Potential reduce by 7.5 kB

  • Original 9.3 kB
  • After minification 7.3 kB
  • After compression 1.7 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. O2navi.net needs all CSS files to be minified and compressed as it can save up to 7.5 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

13

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

o2navi.net

o2navi.net

794 ms

styles.css

styles.css

716 ms

mt.js

mt.js

558 ms

534 ms

header.gif

header.gif

347 ms

rss.gif

rss.gif

181 ms

v_top.gif

v_top.gif

345 ms

v_hd.gif

v_hd.gif

360 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

18 ms

back.gif

back.gif

331 ms

h2_back2.gif

h2_back2.gif

357 ms

h2_back.gif

h2_back.gif

361 ms

menu01.gif

menu01.gif

476 ms

Accessibility Review

o2navi.net accessibility score

92

Accessibility Issues

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

o2navi.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

o2navi.net SEO score

75

Search Engine Optimization Advices

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 O2navi.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 O2navi.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

o2navi.net

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