Tools & Wizards About Us
check.nanapi.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

check.nanapi.jp

nanapi [ナナピ] | わかる・できる・たのしい！暮らしの情報サイト

Page Load Speed

4.2 sec in total

First Response

368 ms

Resources Loaded

3.5 sec

Page Rendered

331 ms

check.nanapi.jp screenshot

About Website

Click here to check amazing Check Nanapi content for Japan. Otherwise, check out these important facts you probably never knew about check.nanapi.jp

nanapiは、生活をもっと便利にするための知識や方法が集まる情報サイトです。

Visit check.nanapi.jp

Key Findings

We analyzed Check.nanapi.jp page load time and found that the first response time was 368 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

check.nanapi.jp performance score

0

Network Requests Diagram

check.nanapi.jp

368 ms

nanapi.jp

1007 ms

application-999209171d28e4a2dd592083f2e80f13.css

150 ms

application-180333c742598551264e7911bc9934d3.js

184 ms

outbrain.js

36 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Check.nanapi.jp, 28% (18 requests) were made to P.cdnanapi.com and 18% (12 requests) were made to Asset.cdnanapi.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Nanapi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 665.8 kB (52%)

Content Size

1.3 MB

After Optimization

618.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Check.nanapi.jp main page is 1.3 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. 45% of websites need less resources to load. Javascripts take 550.7 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 159.5 kB

  • Original 222.3 kB
  • After minification 222.2 kB
  • After compression 62.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 159.5 kB or 72% of the original size.

Image Optimization

-6%

Potential reduce by 14.1 kB

  • Original 233.1 kB
  • After minification 219.0 kB

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. Check Nanapi images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 259.2 kB

  • Original 550.7 kB
  • After minification 550.6 kB
  • After compression 291.5 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 259.2 kB or 47% of the original size.

CSS Optimization

-84%

Potential reduce by 233.1 kB

  • Original 278.4 kB
  • After minification 275.2 kB
  • After compression 45.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. Check.nanapi.jp needs all CSS files to be minified and compressed as it can save up to 233.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (38%)

Requests Now

60

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Check Nanapi. 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 as a result speed up the page load time.

Network Requests Diagram

check.nanapi.jp

check.nanapi.jp

368 ms

nanapi.jp

nanapi.jp

1007 ms

application-999209171d28e4a2dd592083f2e80f13.css

application-999209171d28e4a2dd592083f2e80f13.css

150 ms

application-180333c742598551264e7911bc9934d3.js

application-180333c742598551264e7911bc9934d3.js

184 ms

outbrain.js

outbrain.js

36 ms

analytics.js

analytics.js

178 ms

td-1.1.1.js

td-1.1.1.js

531 ms

body-bg-b5be131578d89df4c363816278f90971.png

body-bg-b5be131578d89df4c363816278f90971.png

141 ms

gpt.js

gpt.js

189 ms

gtm.js

gtm.js

253 ms

20140418110021_535087359cd19.jpg

20140418110021_535087359cd19.jpg

708 ms

20160313041146_56e469f22de9b.jpg

20160313041146_56e469f22de9b.jpg

322 ms

5b60e387-5036-4b77-9e9c-0926a79ad8a8.jpg

5b60e387-5036-4b77-9e9c-0926a79ad8a8.jpg

318 ms

f1de6963-838c-4158-a032-3ba943ffbd56.JPG

f1de6963-838c-4158-a032-3ba943ffbd56.JPG

316 ms

daca4f2e-82e8-41e4-aed2-29836737935c.jpg

daca4f2e-82e8-41e4-aed2-29836737935c.jpg

318 ms

ef288625-919b-4856-b4bf-2e1be3b3478c.jpg

ef288625-919b-4856-b4bf-2e1be3b3478c.jpg

319 ms

e57357ae-0d01-451c-866a-cb24eef44c54.jpg

e57357ae-0d01-451c-866a-cb24eef44c54.jpg

320 ms

1f2179f7-4960-4af1-b307-4c321c7fa3a1.jpg

1f2179f7-4960-4af1-b307-4c321c7fa3a1.jpg

321 ms

20160312172814_56e3d31e9137a.jpg

20160312172814_56e3d31e9137a.jpg

330 ms

20160313060436_56e48464dab73.jpg

20160313060436_56e48464dab73.jpg

322 ms

20160313054011_56e47eaba570b.jpg

20160313054011_56e47eaba570b.jpg

321 ms

footer-bg-body-c8aa48580273daabdc7292e6f33cd614.jpg

footer-bg-body-c8aa48580273daabdc7292e6f33cd614.jpg

151 ms

header-bg-dbd9dad9df8ebbd7442c4b2b04ec48b3.png

header-bg-dbd9dad9df8ebbd7442c4b2b04ec48b3.png

136 ms

logo-header-4b73af627aa7a0f6e0508b7427fe6348.png

logo-header-4b73af627aa7a0f6e0508b7427fe6348.png

157 ms

icon-gn-header-a2c2dfb8302807d1934495f6efab1f4d.png

icon-gn-header-a2c2dfb8302807d1934495f6efab1f4d.png

155 ms

media-image-d13dc17e7ff7e0254370631f0a7b534a.png

media-image-d13dc17e7ff7e0254370631f0a7b534a.png

156 ms

icn-component-de4589143f191be2db7e878e780b03d9.png

icn-component-de4589143f191be2db7e878e780b03d9.png

155 ms

portal-theme-icon-25d5249d0a1e33f81179e2edd1eaedc2.png

portal-theme-icon-25d5249d0a1e33f81179e2edd1eaedc2.png

156 ms

icn-rc-relevant-926aed7a0853022b033a8636e8732bef.png

icn-rc-relevant-926aed7a0853022b033a8636e8732bef.png

177 ms

bi.js

bi.js

781 ms

tag.js

tag.js

90 ms

iframe

iframe

968 ms

load

load

397 ms

collect

collect

44 ms

collect

collect

46 ms

pubads_impl_82.js

pubads_impl_82.js

112 ms

collect

collect

147 ms

tag

tag

72 ms

collect

collect

25 ms

ads

ads

327 ms

container.html

container.html

47 ms

765c06e8-fa55-4ed2-98f5-80c1e58b77c0.jpg

765c06e8-fa55-4ed2-98f5-80c1e58b77c0.jpg

23 ms

76d5587e-d253-4728-961f-8233d10c9c4e.jpg

76d5587e-d253-4728-961f-8233d10c9c4e.jpg

31 ms

ffb64ffe-7819-4330-ad9e-218b1841b423.jpg

ffb64ffe-7819-4330-ad9e-218b1841b423.jpg

11 ms

f9b8c9de-e2d8-4fcb-a720-220bb595141b.jpg

f9b8c9de-e2d8-4fcb-a720-220bb595141b.jpg

21 ms

adebae7f-5995-4461-9f34-f4693fd9272d.jpg

adebae7f-5995-4461-9f34-f4693fd9272d.jpg

15 ms

b12768c5-314a-496c-b271-5631a8528a31.jpg

b12768c5-314a-496c-b271-5631a8528a31.jpg

47 ms

46bee2e0-2bd7-443b-b74c-a818c0fc4da5.jpg

46bee2e0-2bd7-443b-b74c-a818c0fc4da5.jpg

33 ms

bg-linedot-gray-cb46768c59fed725656f502f4bf35c93.png

bg-linedot-gray-cb46768c59fed725656f502f4bf35c93.png

46 ms

expansion_embed.js

expansion_embed.js

78 ms

421 ms

abg.js

abg.js

36 ms

m_js_controller.js

m_js_controller.js

53 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

105 ms

osd.js

osd.js

101 ms

5311771886096778794

5311771886096778794

95 ms

13250232331523409936

13250232331523409936

96 ms

s

s

59 ms

x_button_blue2.png

x_button_blue2.png

54 ms

513 ms

iframe

iframe

10 ms

nr-885.min.js

nr-885.min.js

119 ms

ya.js

ya.js

509 ms

ui

ui

51 ms

e661423a1e

e661423a1e

104 ms

SEO Factors

check.nanapi.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Check.nanapi.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 Check.nanapi.jp main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

check.nanapi.jp

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