11.1 sec in total
745 ms
9.7 sec
567 ms
Click here to check amazing FUNDO content for Japan. Otherwise, check out these important facts you probably never knew about fundo.jp
今SNSで旬なネタや情報、様々な雑学を提供するWEBメディア『FUNDO』
Visit fundo.jpWe analyzed Fundo.jp page load time and found that the first response time was 745 ms and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fundo.jp performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value16.0 s
0/100
25%
Value19.0 s
0/100
10%
Value7,320 ms
0/100
30%
Value0.2
62/100
15%
Value34.0 s
0/100
10%
745 ms
342 ms
355 ms
31 ms
746 ms
Our browser made a total of 219 requests to load all elements on the main page. We found that 16% of them (36 requests) were addressed to the original Fundo.jp, 5% (11 requests) were made to Aladdin.genieesspv.jp and 5% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Fundo.jp.
Page size can be reduced by 244.3 kB (14%)
1.7 MB
1.5 MB
In fact, the total size of Fundo.jp main page is 1.7 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 64.4 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 64.4 kB or 76% of the original size.
Potential reduce by 54.5 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. FUNDO images are well optimized though.
Potential reduce by 85.0 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 85.0 kB or 36% of the original size.
Potential reduce by 40.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. Fundo.jp needs all CSS files to be minified and compressed as it can save up to 40.4 kB or 81% of the original size.
Number of requests can be reduced by 137 (67%)
204
67
The browser has sent 204 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FUNDO. 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 from 5 to 1 for CSS and as a result speed up the page load time.
fundo.jp
745 ms
default.css
342 ms
style.css
355 ms
jquery.min.js
31 ms
pagetop.js
746 ms
adsbygoogle.js
8 ms
a1030922.js
371 ms
a1035388.js
371 ms
advs-instream.js
16 ms
compass.js
13 ms
tablet.css
346 ms
smart.css
323 ms
fbevents.js
87 ms
logo.svg
316 ms
facebook.svg
318 ms
twitter.svg
337 ms
beji.jpg
754 ms
main2.jpg
728 ms
CcOnjuPUMAAUcYTr1.jpg
1083 ms
samune-nami.jpg
990 ms
goh.jpg
992 ms
main.jpg
1245 ms
main1.jpg
1642 ms
main91.jpg
1496 ms
main90.jpg
1866 ms
fd30000316.jpg
1545 ms
mainmain6.jpg
1821 ms
main92.jpg
1865 ms
318113B500000578-0-image-a-58_1456317756828r1.jpg
2355 ms
main_R4.jpg
2434 ms
crown.svg
1975 ms
main44-120x80.jpg
2134 ms
fd141015e022s-120x80.jpg
2195 ms
CHMcsMdUgAAzP2jrs-120x80.jpg
2208 ms
SrxkBgTr11-120x80.jpg
2313 ms
hand4r-120x80.jpg
2483 ms
fd140812d00001s-120x80.jpg
2528 ms
main19-120x80.jpg
2519 ms
fd140729b00009s-120x80.jpg
2684 ms
main52-120x80.jpg
2698 ms
main9-120x80.jpg
2814 ms
bnr-app.jpg
3744 ms
page_top.svg
2876 ms
cookie_enabled_get_apac.html
364 ms
sdk.js
208 ms
ca-pub-7908153757590041.js
54 ms
zrt_lookup.html
42 ms
show_ads_impl.js
55 ms
jsk
470 ms
137 ms
ads
284 ms
osd.js
25 ms
ads
232 ms
59 ms
xd_arbiter.php
132 ms
xd_arbiter.php
306 ms
3110009178226643139
47 ms
abg.js
47 ms
m_js_controller.js
56 ms
googlelogo_color_112x36dp.png
129 ms
14654292472565254905
72 ms
x_button_blue2.png
72 ms
s
60 ms
pixel
39 ms
gl0
188 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
12 ms
sync
10 ms
imp
250 ms
sync
354 ms
acs
190 ms
acs
366 ms
309 ms
cs
199 ms
js1
478 ms
sync
3 ms
gl0
203 ms
cs
165 ms
acs
193 ms
cs
215 ms
js
522 ms
gcs
371 ms
gcs
866 ms
ajs.php
229 ms
gl0
193 ms
jstag
13 ms
gl0
188 ms
lg.php
29 ms
match.aspx
28 ms
acj
89 ms
99ab983df96a80cb1b6df7f6ef9836b7
43 ms
pd
38 ms
ads
240 ms
gl0
188 ms
ri
21 ms
crown_y.svg
367 ms
4c1315d1-5a6b-e8a5-99bb-a6b165c4a7e2
33 ms
pixel
34 ms
widgets.js
12 ms
sd
8 ms
sd
30 ms
jsk
248 ms
sd
26 ms
sd
6 ms
5171746271700867932
39 ms
usermatch
23 ms
usermatch
26 ms
casale
12 ms
cm
14 ms
cs
191 ms
pixel
49 ms
casale
26 ms
23 ms
js
615 ms
gl3
199 ms
crum
54 ms
rum
56 ms
rum
44 ms
crum
43 ms
crum
22 ms
rum
19 ms
rum
10 ms
set
299 ms
sd
5 ms
xrefid.xgi
6 ms
8caa37b3465c8d7e7d4336b66d4edf20.gif
35 ms
js
33 ms
pixel
26 ms
4448
18 ms
pixel.htm
52 ms
img
201 ms
analytics.js
42 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
40 ms
ad
545 ms
ddc.htm
139 ms
collect
119 ms
Pug
109 ms
pixel
132 ms
rtset
136 ms
rum
111 ms
180 ms
g.js
156 ms
3977893079887413374
126 ms
4499
121 ms
3977893079887413374
192 ms
pixel
150 ms
u.php
193 ms
3977893079887413374
146 ms
collect
214 ms
iframe
188 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
131 ms
pixel.gif
152 ms
merge
128 ms
tap.php
131 ms
mapuser
138 ms
xrefid.xgi
137 ms
page.php
270 ms
sync
491 ms
sync
123 ms
175 ms
169 ms
165 ms
e9e856d6-247d-4900-a599-3aa3373c5ab3
147 ms
7822546105569028327
143 ms
142 ms
adsct
220 ms
lr.gif
3723 ms
img
95 ms
bd
94 ms
img
141 ms
NAX3738109209107928466
91 ms
match
71 ms
demconf.jpg
93 ms
ga-audiences
166 ms
demconf.jpg
79 ms
cs
83 ms
a41579b1-e004-11e5-b128-005056a21e49
81 ms
bd
80 ms
appnexus
83 ms
appnexus
91 ms
activeview
75 ms
jot
142 ms
E9-rX0jGnNc.css
191 ms
_rx8naC75Dy.js
307 ms
3o1espZ6Mhb.js
329 ms
nfTYZZc0iSn.js
393 ms
TAa414b66d-e004-11e5-a2a5-00163ebe92e0
52 ms
sci
151 ms
bd
44 ms
369ed99a204d023592a804547c42c81809cf511a
123 ms
imp
395 ms
cs
225 ms
1463905_1459857294287415_4755360577649858008_n.png
210 ms
10616567_1459857644287380_6607913845926260279_n.png
250 ms
11227057_477968679024772_8097605537531684083_n.jpg
292 ms
1379841_10150004552801901_469209496895221757_n.jpg
326 ms
11179947_100727793596519_889448203896340915_n.jpg
332 ms
11223796_505953119570298_6953338621879964533_n.jpg
331 ms
3609_197967967227676_8812445623566233986_n.jpg
334 ms
179155_102158949990888_494887241_n.jpg
333 ms
12509743_771104103035459_8553083891229968943_n.jpg
332 ms
12705608_1675662972673104_9090270379031284371_n.jpg
365 ms
wL6VQj7Ab77.png
55 ms
s7jcwEQH7Sx.png
54 ms
gcs
167 ms
R9a_DtVRZgv.js
41 ms
cUDgRFxaoIk.js
42 ms
0JBr1QHp8Gi.js
43 ms
kDOzhTr2W91.js
80 ms
tap.php
18 ms
img
26 ms
gcs
682 ms
sd
5 ms
img
49 ms
mapuser
5 ms
Pug
20 ms
u.php
61 ms
img
174 ms
ui
14 ms
sync
302 ms
fundo.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
fundo.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fundo.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fundo.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 Fundo.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.
fundo.jp
Open Graph data is detected on the main page of FUNDO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: