Tools & Wizards About Us
nanapi.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nanapi.jp

暮らしの情報サイトnanapiはサービスを終了いたしました | nanapi [ナナピ]

Page Load Speed

3.4 sec in total

First Response

324 ms

Resources Loaded

2.8 sec

Page Rendered

244 ms

nanapi.jp screenshot

About Website

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

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

Visit nanapi.jp

Key Findings

We analyzed Nanapi.jp page load time and found that the first response time was 324 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

nanapi.jp performance score

0

Network Requests Diagram

nanapi.jp

324 ms

nanapi.jp

868 ms

application-999209171d28e4a2dd592083f2e80f13.css

87 ms

application-7cb34ac6b3523c1554a37f25d4831e49.js

110 ms

outbrain.js

46 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Nanapi.jp, 28% (14 requests) were made to P.cdnanapi.com and 24% (12 requests) were made to Asset.cdnanapi.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source B.yjtag.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 796.2 kB (55%)

Content Size

1.4 MB

After Optimization

646.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-68%

Potential reduce by 24.0 kB

  • Original 35.1 kB
  • After minification 35.0 kB
  • After compression 11.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. 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 24.0 kB or 68% of the original size.

Image Optimization

-6%

Potential reduce by 15.4 kB

  • Original 264.7 kB
  • After minification 249.3 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. Nanapi images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 523.8 kB

  • Original 864.0 kB
  • After minification 864.0 kB
  • After compression 340.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 523.8 kB or 61% 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. 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 17 (37%)

Requests Now

46

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nanapi.jp

nanapi.jp

324 ms

nanapi.jp

nanapi.jp

868 ms

application-999209171d28e4a2dd592083f2e80f13.css

application-999209171d28e4a2dd592083f2e80f13.css

87 ms

application-7cb34ac6b3523c1554a37f25d4831e49.js

application-7cb34ac6b3523c1554a37f25d4831e49.js

110 ms

outbrain.js

outbrain.js

46 ms

analytics.js

analytics.js

310 ms

td-1.1.1.js

td-1.1.1.js

396 ms

body-bg-b5be131578d89df4c363816278f90971.png

body-bg-b5be131578d89df4c363816278f90971.png

116 ms

gpt.js

gpt.js

252 ms

gtm.js

gtm.js

275 ms

f58c7c19-1655-48a3-97bc-0cb098173fe8.jpg

f58c7c19-1655-48a3-97bc-0cb098173fe8.jpg

244 ms

bi.js

bi.js

784 ms

tag.js

tag.js

152 ms

iframe

iframe

1135 ms

load

load

403 ms

footer-bg-body-c8aa48580273daabdc7292e6f33cd614.jpg

footer-bg-body-c8aa48580273daabdc7292e6f33cd614.jpg

137 ms

header-bg-dbd9dad9df8ebbd7442c4b2b04ec48b3.png

header-bg-dbd9dad9df8ebbd7442c4b2b04ec48b3.png

136 ms

logo-header-4b73af627aa7a0f6e0508b7427fe6348.png

logo-header-4b73af627aa7a0f6e0508b7427fe6348.png

179 ms

icon-gn-header-a2c2dfb8302807d1934495f6efab1f4d.png

icon-gn-header-a2c2dfb8302807d1934495f6efab1f4d.png

164 ms

media-image-d13dc17e7ff7e0254370631f0a7b534a.png

media-image-d13dc17e7ff7e0254370631f0a7b534a.png

216 ms

icn-component-de4589143f191be2db7e878e780b03d9.png

icn-component-de4589143f191be2db7e878e780b03d9.png

141 ms

portal-theme-icon-25d5249d0a1e33f81179e2edd1eaedc2.png

portal-theme-icon-25d5249d0a1e33f81179e2edd1eaedc2.png

216 ms

icn-rc-relevant-926aed7a0853022b033a8636e8732bef.png

icn-rc-relevant-926aed7a0853022b033a8636e8732bef.png

217 ms

3ed3c0b1-4311-4994-b5d9-22a44fbf0d97.jpg

3ed3c0b1-4311-4994-b5d9-22a44fbf0d97.jpg

616 ms

20160223235507_56cc72cb3021b.jpg

20160223235507_56cc72cb3021b.jpg

613 ms

2476989c-e150-4b0d-892d-024a041c5a37.jpg

2476989c-e150-4b0d-892d-024a041c5a37.jpg

606 ms

20160226013707_56cf2db3ed8ff.jpg

20160226013707_56cf2db3ed8ff.jpg

629 ms

20160226004242_56cf20f22d104.jpg

20160226004242_56cf20f22d104.jpg

654 ms

479259b5-0e61-4cfe-9c64-8876ca5afd4d.jpg

479259b5-0e61-4cfe-9c64-8876ca5afd4d.jpg

624 ms

20160226001830_56cf1b46820e4.jpg

20160226001830_56cf1b46820e4.jpg

817 ms

20160225233549_56cf1145dbdb8.jpg

20160225233549_56cf1145dbdb8.jpg

1009 ms

601dd5a1-7e31-4ca1-a788-f016fb4c2acf.jpg

601dd5a1-7e31-4ca1-a788-f016fb4c2acf.jpg

1089 ms

2dda36d2-0a0e-4e7b-93c4-adff36f1ee65.JPG

2dda36d2-0a0e-4e7b-93c4-adff36f1ee65.JPG

1070 ms

tag

tag

118 ms

pubads_impl_81.js

pubads_impl_81.js

229 ms

collect

collect

36 ms

collect

collect

70 ms

collect

collect

71 ms

collect

collect

111 ms

6459ae35-3cda-4da5-aec1-707165d3697f.jpg

6459ae35-3cda-4da5-aec1-707165d3697f.jpg

223 ms

fbbfcfca-e009-48cc-a524-2f6ec9bfbac8.jpg

fbbfcfca-e009-48cc-a524-2f6ec9bfbac8.jpg

242 ms

41276b38-8156-4b0d-a1f2-4d4069e66c3a.jpg

41276b38-8156-4b0d-a1f2-4d4069e66c3a.jpg

272 ms

bg-linedot-gray-cb46768c59fed725656f502f4bf35c93.png

bg-linedot-gray-cb46768c59fed725656f502f4bf35c93.png

25 ms

ads

ads

145 ms

container.html

container.html

18 ms

s.sh.adingo.jp

s.sh.adingo.jp

778 ms

osd.js

osd.js

59 ms

697 ms

iframe

iframe

5 ms

sync

sync

22 ms

SEO Factors

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

nanapi.jp

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