18.2 sec in total
1.3 sec
16.3 sec
654 ms
Click here to check amazing Nanjfan content for Japan. Otherwise, check out these important facts you probably never knew about nanjfan.com
Visit nanjfan.comWe analyzed Nanjfan.com page load time and found that the first response time was 1.3 sec and then it took 17 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
nanjfan.com performance score
1270 ms
534 ms
475 ms
328 ms
397 ms
Our browser made a total of 222 requests to load all elements on the main page. We found that 21% of them (47 requests) were addressed to the original Nanjfan.com, 6% (14 requests) were made to Cs.adingo.jp and 4% (9 requests) were made to I.adingo.jp. The less responsive or slowest element that took the longest time to load (8.2 sec) belongs to the original domain Nanjfan.com.
Page size can be reduced by 143.9 kB (19%)
766.6 kB
622.7 kB
In fact, the total size of Nanjfan.com main page is 766.6 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. 45% of websites need less resources to load. Images take 554.8 kB which makes up the majority of the site volume.
Potential reduce by 44.0 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 44.0 kB or 82% of the original size.
Potential reduce by 3.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. Nanjfan images are well optimized though.
Potential reduce by 87.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 87.2 kB or 60% of the original size.
Potential reduce by 9.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. Nanjfan.com needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 78% of the original size.
Number of requests can be reduced by 136 (70%)
195
59
The browser has sent 195 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nanjfan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and as a result speed up the page load time.
nanjfan.com
1270 ms
index.css
534 ms
sh.adingo.jp
475 ms
sh.adingo.jp
328 ms
sh.adingo.jp
397 ms
sh.adingo.jp
409 ms
jquery.min.js
39 ms
jquery.pjax.min.js
530 ms
jquery.dotdotdot.min.js
528 ms
default.js
596 ms
sh.adingo.jp
355 ms
top-back.min.png
634 ms
top.min.png
639 ms
sync
913 ms
push_sync
892 ms
cm
511 ms
sync
235 ms
sync
268 ms
i.adingo.jp
496 ms
253199.jpg
891 ms
253198.jpg
599 ms
253195.jpg
609 ms
253196.jpg
613 ms
253197.jpg
1156 ms
253194.jpg
1155 ms
253193.jpg
1185 ms
253192.jpg
1215 ms
253191.jpg
1221 ms
253189.jpg
4767 ms
253190.jpg
1790 ms
253187.jpg
2134 ms
253188.jpg
1832 ms
253186.jpg
2144 ms
253185.jpg
2487 ms
253184.jpg
2505 ms
253182.jpg
2777 ms
253181.jpg
4531 ms
253183.jpg
2793 ms
253180.jpg
4530 ms
253179.jpg
4528 ms
253178.jpg
4833 ms
253177.jpg
4847 ms
253176.jpg
6906 ms
253173.jpg
6722 ms
253175.jpg
5149 ms
253174.jpg
5334 ms
253172.jpg
5441 ms
253171.jpg
5446 ms
253170.jpg
5747 ms
253169.jpg
5972 ms
253168.jpg
8155 ms
253163.jpg
6713 ms
i.adingo.jp
449 ms
253164.jpg
6368 ms
i.adingo.jp
414 ms
i.adingo.jp
417 ms
pixel.htm
167 ms
jstag
189 ms
sync
784 ms
i.adingo.jp
448 ms
pixel
81 ms
822 ms
796 ms
ddc.htm
160 ms
788 ms
Pug
171 ms
pixel
113 ms
rtset
174 ms
rum
168 ms
u.php
201 ms
191 ms
um
145 ms
423 ms
410 ms
389 ms
merge
62 ms
mapuser
56 ms
xrefid.xgi
59 ms
rum
58 ms
sync
84 ms
253166.jpg
5983 ms
lr.gif
76 ms
253165.jpg
7818 ms
tap.php
401 ms
253167.jpg
6562 ms
253162.jpg
6757 ms
253158.jpg
6778 ms
acj
160 ms
pixel.gif
168 ms
bd
99 ms
bd
102 ms
NAX3575957919030507024
137 ms
sd
144 ms
ads.js
1102 ms
ri
79 ms
378 ms
253155.jpg
6972 ms
183 ms
adcore.js
43 ms
adcore_pc.js
104 ms
adcore_pc_inline.js
79 ms
ad_spot.aspx
640 ms
pixel.htm
77 ms
sync
68 ms
i.adingo.jp
5616 ms
acj
82 ms
ddc.htm
104 ms
a105d4d95f40c338037487d5deefeebc
641 ms
ri
91 ms
269 ms
g.js
3206 ms
pixel
315 ms
4499
2491 ms
2609645014635672667
267 ms
216 ms
262 ms
179 ms
adsct
245 ms
cf245708-1438-4500-9b56-29190804f8e4
211 ms
demconf.jpg
44 ms
appnexus
1999 ms
style.css
1803 ms
ad_creative.ashx
1796 ms
match
30 ms
13a9811779149931c29064d956b130ae
1921 ms
ibs:dpid=375&dpuuid=2609645014635672667
195 ms
222 ms
i.adingo.jp
449 ms
1.0.1.js
458 ms
i.adingo.jp
444 ms
appnexus
92 ms
sync
91 ms
-7565803891085394620
96 ms
217 ms
cs
130 ms
xrefid.xgi
79 ms
5643d240-fdc8-11e5-8658-005056a25f1a
89 ms
VB53efeb1e-fdc8-11e5-908a-0a18075171fc
69 ms
1.0.0.js
1825 ms
42 ms
a105d4d95f40c338037487d5deefeebc
262 ms
js1
610 ms
ib
479 ms
1.1.0.js
426 ms
js
547 ms
sync
289 ms
sync
452 ms
sync
525 ms
push_sync
361 ms
cookiesync
209 ms
cookiesync
306 ms
sync
240 ms
receive_sync
175 ms
ADTECH;cfp=1;rndc=1460147261;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1460147261125
406 ms
sh.adingo.jp
468 ms
show.php
387 ms
sync
148 ms
pixel
68 ms
generic
144 ms
mapuser
330 ms
mapuser
737 ms
mapuser
348 ms
mapuser
351 ms
generic
62 ms
mapuser
345 ms
mapuser
357 ms
0.gif
242 ms
sync
573 ms
cm
428 ms
sync
53 ms
sync
55 ms
sg.gif
408 ms
a1033891.js
458 ms
i.adingo.jp
386 ms
mapuser
33 ms
175 ms
193 ms
jsk
451 ms
161 ms
js1
444 ms
gl0
189 ms
cs
278 ms
sync
174 ms
push_sync
187 ms
acs
239 ms
acs
418 ms
js
622 ms
acs
330 ms
cs
240 ms
cs
238 ms
pixel
59 ms
sync
49 ms
423 ms
gcs
445 ms
cs
235 ms
cs
254 ms
cs
235 ms
yads.js
1046 ms
cs
225 ms
mapuser
164 ms
yads_vimps-1.4.1.js
601 ms
tag
664 ms
yads-iframe.html
218 ms
usermatch
83 ms
pixel.htm
91 ms
VwgUNsAoJV8AAf1xLt0AAABy%26636
29 ms
pixel
24 ms
115 ms
mapuser
173 ms
cse
182 ms
cs
81 ms
ddc.htm
63 ms
crum
74 ms
crum
85 ms
mapuser
69 ms
crum
47 ms
crum
330 ms
rum
51 ms
crum
45 ms
tag
536 ms
oi
435 ms
RestoreXidToMediaStorage.html
59 ms
nanjfan.com SEO score
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nanjfan.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Nanjfan.com 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.
nanjfan.com
Open Graph description is not detected on the main page of Nanjfan. 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: