15.9 sec in total
3.3 sec
11.7 sec
994 ms
Welcome to getnavi.jp homepage info - get ready to check Get Navi best content for Japan right away, or after learning these important things about getnavi.jp
アイテム情報誌「GetNavi(ゲットナビ)」のウェブサイトです。デジタル製品や生活家電、ガジェットだけでなく、カルチャーやグルメなど、「いま知っておきたい」情報がたっぷり!
Visit getnavi.jpWe analyzed Getnavi.jp page load time and found that the first response time was 3.3 sec and then it took 12.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
getnavi.jp performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value17.5 s
0/100
25%
Value17.2 s
0/100
10%
Value4,580 ms
0/100
30%
Value0.287
42/100
15%
Value32.5 s
0/100
10%
3262 ms
507 ms
327 ms
350 ms
379 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 59% of them (86 requests) were addressed to the original Getnavi.jp, 12% (17 requests) were made to Pbs.twimg.com and 7% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Getnavi.jp.
Page size can be reduced by 448.9 kB (10%)
4.5 MB
4.1 MB
In fact, the total size of Getnavi.jp main page is 4.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. 70% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 81.3 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 24.8 kB, which is 26% 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 81.3 kB or 84% of the original size.
Potential reduce by 189.2 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. Get Navi images are well optimized though.
Potential reduce by 137.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 137.9 kB or 66% of the original size.
Potential reduce by 40.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. Getnavi.jp needs all CSS files to be minified and compressed as it can save up to 40.6 kB or 81% of the original size.
Number of requests can be reduced by 32 (22%)
146
114
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Get Navi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
getnavi.jp
3262 ms
common.css
507 ms
style.css
327 ms
modernizr.js
350 ms
custom-nextpage-style.css
379 ms
pagenavi-css.css
379 ms
default.min.css
672 ms
pjs.js
519 ms
jquery.min.js
738 ms
blurme.js
333 ms
isotope.pkgd.min.js
467 ms
common.js
398 ms
gnw160212_07_1.jpg
532 ms
image003-500x333.jpg
587 ms
030-031_12-500x344.jpg
648 ms
%E5%90%8D%E7%A7%B0%E6%9C%AA%E8%A8%AD%E5%AE%9A-1-500x354.jpg
976 ms
%E5%AE%9F_44_04-500x334.jpg
996 ms
MG_6104h-001-500x436.jpg
1057 ms
00211-500x375.jpg
1057 ms
%E5%AE%9F25-011-500x374.jpg
1107 ms
gnw160212_03_01-500x375.jpg
1137 ms
gnw160212_05_01-500x375.jpg
1596 ms
00111-500x358.jpg
1699 ms
gnw160212_04_11.jpg
1582 ms
0063-500x375.jpg
1757 ms
5-500x404.jpg
1745 ms
gnw160212_07_10-500x375.jpg
1685 ms
img_91882_2-500x375.jpg
2237 ms
0018-500x367.jpg
2155 ms
gntwitter_ico2-150x150.png
2213 ms
kobasio1-150x150.jpg
2041 ms
k.matsui_mini-e1424769140262-150x150.jpg
2041 ms
hirashima_p-150x150.jpg
2105 ms
E-250x354.jpg
2774 ms
H1_hontoni-353x450-250x319.jpg
2590 ms
151210_web1_04-250x354.jpg
2790 ms
bunbogu-hyo1-e14496502867291-250x336.jpg
2895 ms
%E3%80%90%E8%A1%A81%E3%80%91%E3%81%9D%E3%81%B0%E6%89%8B%E5%B8%B3-250x359.jpg
2696 ms
151103_web01_1-250x355.jpg
2943 ms
VV%E6%9C%AC%E8%A1%A81-250x354.jpg
3286 ms
151005_web1_H1-250x417.jpg
3345 ms
151002_web01_hyoushi-250x357.jpg
3431 ms
150929_web03_A-250x353.jpg
3371 ms
sdk.js
86 ms
analytics.js
84 ms
150929_web02_H1-250x354.jpg
3573 ms
collect
23 ms
collect
84 ms
150826_h01-250x353.jpg
3617 ms
118 ms
xd_arbiter.php
70 ms
xd_arbiter.php
138 ms
hyou1_R-250x355.jpg
3546 ms
150806_tsukemen_61-250x336.jpg
3744 ms
cm
158 ms
cm
185 ms
widgets.js
57 ms
cm
179 ms
hyoshi-250x318.jpg
3401 ms
%E3%83%9F%E3%83%8B%E5%9B%9B%E9%A7%862015_%E8%A1%A8%E7%B4%99-250x316.jpg
3491 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
22 ms
Ra%E8%A1%A8%E7%B4%99-250x355.jpg
3530 ms
syndication
112 ms
557355480767418368
308 ms
like_box.php
86 ms
4056107793-250x355.jpg
3585 ms
ce_pc_renewal1_300x250.gif
54 ms
188 ms
assoc300x250_fsnx_big10_0210.png
35 ms
155 ms
assoc_300_250.jpg
19 ms
156 ms
siylcCr24Vv.css
95 ms
0q9EiyOzKa_.css
113 ms
_rx8naC75Dy.js
149 ms
x5F9OMjKyLw.js
181 ms
ICDbTSzjQEg.js
166 ms
TTCre3391I0.js
166 ms
12717662_1059804714076656_9159980545866865515_n.jpg
137 ms
12742794_1062353437155117_5076817755299702717_n.png
153 ms
12803160_1697414077184174_1554055594355856201_n.jpg
156 ms
5618_849674725154596_751737989107023118_n.jpg
196 ms
1937033_705642866202660_9002286466705955462_n.jpg
237 ms
12705772_10208492008079627_5268247557663315354_n.jpg
177 ms
12347959_859910880774062_9098363183055716919_n.jpg
177 ms
68951_139928462818875_849649321_n.jpg
193 ms
12651286_138486696533125_5951917628999681470_n.jpg
174 ms
wL6VQj7Ab77.png
18 ms
s7jcwEQH7Sx.png
19 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
2 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
gnw_arrowsTab160223.jpg
3453 ms
VqFVO1jK_normal.png
149 ms
CcXk7zbUMAAGcyO.jpg:small
218 ms
CcSJOnTUsAELN-u.jpg:small
276 ms
CcSGBr6UMAAJbau.jpg:small
269 ms
CcLmRfjUMAASrMp.jpg:small
377 ms
CcJUE6ZUsAAgPki.jpg:small
272 ms
CcJSr64VAAANnsN.jpg:small
344 ms
CcH-yU1VIAAl6iJ.jpg:small
370 ms
CcH-BvIUYAAz7zF.jpg:small
397 ms
CcH9HBzUUAABARf.jpg:small
381 ms
CcHznP-UkAIGHml.jpg:small
419 ms
CcD_yWGUUAAnScA.jpg:small
373 ms
CcD_HnvUMAAPXSY.jpg:small
482 ms
CcD-qx2UYAIzNdQ.jpg:small
510 ms
CcEW7MAUMAENbIR.jpg:small
432 ms
CcDWFuqUEAAw1yN.jpg:small
462 ms
CcCxihfUUAAnd5z.jpg:small
557 ms
bn_spring.jpg
3450 ms
GNW%E3%82%A2%E3%83%B3%E3%82%B1%E3%83%BC%E3%83%88%E3%83%90%E3%83%8A%E3%83%BC.jpg
3552 ms
006-01.jpg
3761 ms
gnw160114_02_0501.jpg
3674 ms
1603135_01.jpg
4099 ms
I6-MnjEovm5.js
20 ms
vlXaquuXMrr.js
54 ms
jot
25 ms
38-1-690x601.jpg
3590 ms
img31_1.jpg
3552 ms
bn_honmono.jpg
3909 ms
banner_white.jpg
3839 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-02-24-10.09.34.png
5284 ms
img_91882_2-250x187.jpg
3835 ms
%E5%90%8D%E7%A7%B0%E6%9C%AA%E8%A8%AD%E5%AE%9A-1-250x177.jpg
3657 ms
image-250x141.jpg
3576 ms
%E7%94%BB%E5%83%8F31-250x128.jpg
3993 ms
0035-250x167.jpg
3734 ms
pop_01-250x219.jpg
3701 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-02-24-10.09.34-250x339.png
4291 ms
1510141_01-250x141.jpg
3490 ms
gnw160210_03_08-250x178.jpg
3564 ms
gnw160212_03_01-250x188.jpg
3538 ms
bn_weekly.gif
3660 ms
NEGIMA_300_web.gif
5291 ms
mamabloger_banner.jpg
4504 ms
aomurotop2.jpg
3546 ms
muplus_w300h150.jpg
3403 ms
new_logo.png
3476 ms
icn_glass.png
3666 ms
icn_books.png
3540 ms
icn_book_open.png
3412 ms
icn_book.png
3639 ms
icn_coup.png
3545 ms
icn_ranking_1.png
3447 ms
icn_ranking_2.png
3423 ms
icn_ranking_3.png
3638 ms
bg.png
3576 ms
getnavi.jp accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
getnavi.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
getnavi.jp SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Getnavi.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Getnavi.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.
getnavi.jp
Open Graph data is detected on the main page of Get Navi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: