5.4 sec in total
250 ms
3.9 sec
1.3 sec
Click here to check amazing Frann content for Japan. Otherwise, check out these important facts you probably never knew about frann.jp
Visit frann.jpWe analyzed Frann.jp page load time and found that the first response time was 250 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster. This domain responded with an error, which can significantly jeopardize Frann.jp rating and web reputation
frann.jp performance score
250 ms
12 ms
22 ms
36 ms
34 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Frann.jp, 16% (22 requests) were made to Blog-imgs-86.fc2.com and 13% (17 requests) were made to Blog-imgs-90.fc2.com. The less responsive or slowest element that took the longest time to load (703 ms) relates to the external source B.st-hatena.com.
Page size can be reduced by 257.6 kB (23%)
1.1 MB
844.9 kB
In fact, the total size of Frann.jp main page is 1.1 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 822.9 kB which makes up the majority of the site volume.
Potential reduce by 46.8 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 7.3 kB, which is 13% 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 46.8 kB or 84% of the original size.
Potential reduce by 92.8 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. Obviously, Frann needs image optimization as it can save up to 92.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 71.6 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 71.6 kB or 43% of the original size.
Potential reduce by 46.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. Frann.jp needs all CSS files to be minified and compressed as it can save up to 46.4 kB or 82% of the original size.
Number of requests can be reduced by 55 (50%)
111
56
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frann. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
frann.jp
250 ms
jquery.js
12 ms
scrolltopcontrol.js
22 ms
592ba.css
36 ms
jquery.min.js
34 ms
e7d5a53aabfb45ffa6e90fa8f48676e0
583 ms
fbb14deae0b6760389ec40dcb5ac6c50
613 ms
a8db3bf692cace4ce9a36ef85766a319
617 ms
bg1.jpg
34 ms
entry_img_622.jpg
395 ms
s_nigaoemaker.png
38 ms
entertainments88_31.gif
569 ms
br_c_1730_1.gif
416 ms
c_01.gif
148 ms
headbg.jpg
17 ms
bg6.png
22 ms
kage.png
27 ms
entry_img_621.jpg
13 ms
entry_img_620.jpg
24 ms
2016030209575517b.jpg
42 ms
1_20160206200321b83.jpg
24 ms
2_20160206200322b7c.jpg
22 ms
3_20160206200324dc9s.jpg
29 ms
6_20160206200339dca.jpg
63 ms
entry_img_558.jpg
40 ms
5_20160206200327d60.jpg
48 ms
4_20160206200325f10s.jpg
186 ms
7_2016020620034092bs.jpg
81 ms
8_20160206200342b41s.jpg
40 ms
entry_img_534s.jpg
67 ms
13_20160206200401a38s.jpg
66 ms
1_201602161852377e0s.jpg
99 ms
2016020620040078bs.jpg
67 ms
14_201602062004039c4s.jpg
71 ms
2_2016021408114890b.jpg
99 ms
16_20160206200418a81s.jpg
79 ms
17_20160206200420171s.jpg
80 ms
10_2016020620034547es.jpg
83 ms
entry_img_618.jpg
226 ms
2_20160224174751807s.jpg
47 ms
1_20160224174750e02s.jpg
50 ms
entry_img_622.jpg
147 ms
entry_img_621.jpg
146 ms
entry_img_620.jpg
143 ms
entry_img_619.jpg
223 ms
entry_img_617.jpg
354 ms
entry_img_616.jpg
287 ms
entry_img_615.jpg
295 ms
entry_img_614.jpg
555 ms
entry_img_613.jpg
239 ms
90 ms
87 ms
94 ms
73 ms
entry_img_622.jpg
79 ms
entry_img_621.jpg
77 ms
entry_img_620.jpg
73 ms
entry_img_619.jpg
74 ms
c05198d2db81cf24ed6e252555d54cf9
401 ms
72 ms
86 ms
84 ms
94 ms
1.0.1.js
344 ms
ninja_onetag.css
399 ms
trac.js
332 ms
1.0.0.js
183 ms
fotbg.jpg
43 ms
button-only@2x.png
696 ms
widgets.js
120 ms
bookmark_button.js
703 ms
btn.js
41 ms
platform.js
96 ms
ptop.png
30 ms
sync
322 ms
button
21 ms
button.css
102 ms
shared.js
122 ms
button.js
124 ms
cb=gapi.loaded_0
54 ms
cb=gapi.loaded_1
79 ms
fastbutton
190 ms
like.php
232 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
188 ms
e7d5a53aabfb45ffa6e90fa8f48676e0
271 ms
fbb14deae0b6760389ec40dcb5ac6c50
309 ms
a8db3bf692cace4ce9a36ef85766a319
449 ms
pocket_button.png
33 ms
postmessageRelay
39 ms
api.js
77 ms
core:rpc:shindig.random:shindig.sha1.js
126 ms
2536007149-postmessagerelay.js
74 ms
cb=gapi.loaded_0
92 ms
cb=gapi.loaded_1
59 ms
cookiesync
220 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
103 ms
rU2ubZ6l1Q5.js
88 ms
LVx-xkvaJ0b.png
85 ms
sync
316 ms
sync
351 ms
push_sync
320 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
58 ms
ads.js
36 ms
ib
240 ms
adcomp_pc.js
6 ms
sspcore_spot.js
191 ms
js1
524 ms
ib
257 ms
jot
78 ms
ib
203 ms
1.1.0.js
173 ms
ssp_spot.ashx
312 ms
cookiesync
187 ms
204 ms
sync
175 ms
receive_sync
158 ms
reset.css
9 ms
entry-button.css
8 ms
bbtn-l_v3.png
3 ms
adcore.js
5 ms
adcore_pc.js
8 ms
adcore_pc_inline.js
8 ms
ad_spot.aspx
541 ms
js
618 ms
js
538 ms
style.css
173 ms
ad_creative.ashx
218 ms
RestoreXidToMediaStorage.html
11 ms
ADTECH;cfp=1;rndc=1456893844;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456893844945
342 ms
ADTECH;cfp=1;rndc=1456893844;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456893845023
304 ms
sync
11 ms
pixel
27 ms
generic
14 ms
generic
7 ms
frann.jp SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frann.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 Frann.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.
frann.jp
Open Graph description is not detected on the main page of Frann. 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: