Tools & Wizards About Us
na-re.jp screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

na-re.jp

心理カウンセリングとメンタルケアの「ナチュラルリソース」 | 心理カウンセリングとメンタルケアの「ナチュラルリソース」：カウンセリングルーム・東京都渋谷・青山・表参道（全国対応可）

Page Load Speed

5.3 sec in total

First Response

592 ms

Resources Loaded

4.5 sec

Page Rendered

266 ms

na-re.jp screenshot

About Website

Click here to check amazing Na Re content for Japan. Otherwise, check out these important facts you probably never knew about na-re.jp

心理カウンセリングルーム『ナチュラルリソース』（東京都渋谷区・青山）では、依存症・うつ病・境界性パーソナリティ障害の専門セラピストによるカウンセリングを得意としています。電話番号03-6447-2704。

Visit na-re.jp

Key Findings

We analyzed Na-re.jp page load time and found that the first response time was 592 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

na-re.jp performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

na-re.jp

592 ms

na-re.jp

1075 ms

wp-emoji-release.min.js

179 ms

style.min.css

359 ms

styles.css

536 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 87% of them (53 requests) were addressed to the original Na-re.jp, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Na-re.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 302.4 kB (20%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 24.8 kB

  • Original 32.9 kB
  • After minification 29.0 kB
  • After compression 8.1 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 3.9 kB, which is 12% 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 24.8 kB or 76% of the original size.

Image Optimization

-21%

Potential reduce by 270.4 kB

  • Original 1.3 MB
  • After minification 1.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. Obviously, Na Re needs image optimization as it can save up to 270.4 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 2.4 kB

  • Original 136.3 kB
  • After minification 135.6 kB
  • After compression 133.9 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

-15%

Potential reduce by 4.8 kB

  • Original 31.8 kB
  • After minification 31.8 kB
  • After compression 27.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. Na-re.jp needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (41%)

Requests Now

58

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

na-re.jp

na-re.jp

592 ms

na-re.jp

na-re.jp

1075 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

179 ms

style.min.css

style.min.css

359 ms

styles.css

styles.css

536 ms

whats-new.css

whats-new.css

671 ms

style.css

style.css

676 ms

normalize.css

normalize.css

729 ms

font-awesome.min.css

font-awesome.min.css

778 ms

style.css

style.css

782 ms

jquery.min.js

jquery.min.js

26 ms

jquery.min.js

jquery.min.js

976 ms

jquery.cookie.js

jquery.cookie.js

847 ms

fontsize.js

fontsize.js

855 ms

getIframeHeight.js

getIframeHeight.js

910 ms

sp-head.js

sp-head.js

994 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

1175 ms

custom_header.js

custom_header.js

1025 ms

sp_head.css

sp_head.css

1034 ms

ajaxzip3.js

ajaxzip3.js

22 ms

js

js

63 ms

comment-reply.min.js

comment-reply.min.js

1091 ms

scripts.js

scripts.js

1255 ms

base.js

base.js

1256 ms

scroll.js

scroll.js

1257 ms

wp-embed.min.js

wp-embed.min.js

1256 ms

allheaderbg.jpg

allheaderbg.jpg

187 ms

header-mark.jpg

header-mark.jpg

595 ms

mojisize.png

mojisize.png

208 ms

moji-small1.png

moji-small1.png

242 ms

moji-midium1.png

moji-midium1.png

380 ms

moji-big1.png

moji-big1.png

387 ms

header-tel.png

header-tel.png

374 ms

logo.png

logo.png

415 ms

header-gmenu-1.png

header-gmenu-1.png

445 ms

top-titlepic-1.png

top-titlepic-1.png

558 ms

top-topic01.png

top-topic01.png

895 ms

top-topic03.png

top-topic03.png

911 ms

top-topic02.png

top-topic02.png

1003 ms

icon-note.jpg

icon-note.jpg

646 ms

icon-list01.png

icon-list01.png

735 ms

icon-last-child.png

icon-last-child.png

803 ms

icon-people01.png

icon-people01.png

848 ms

sidebunner01.png

sidebunner01.png

1082 ms

side-checktest.png

side-checktest.png

1008 ms

side-about.png

side-about.png

1085 ms

side-tokui.png

side-tokui.png

1072 ms

side-callservice.png

side-callservice.png

1090 ms

side-multilingual.png

side-multilingual.png

1208 ms

side-groupe.png

side-groupe.png

1216 ms

side-eap.png

side-eap.png

1254 ms

side-mental.png

side-mental.png

1265 ms

side-qr.png

side-qr.png

1300 ms

footer-mark.jpg

footer-mark.jpg

1285 ms

handimage.png

handimage.png

1554 ms

js

js

51 ms

analytics.js

analytics.js

14 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1522 ms

collect

collect

11 ms

collect

collect

62 ms

ga-audiences

ga-audiences

28 ms

Accessibility Review

na-re.jp accessibility score

69

Accessibility Issues

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

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

na-re.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

na-re.jp SEO score

93

Search Engine Optimization Advices

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

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 Na-re.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 Na-re.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

na-re.jp

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