7.9 sec in total
524 ms
7.1 sec
251 ms
Click here to check amazing Worldvision content for Japan. Otherwise, check out these important facts you probably never knew about worldvision.jp
特定非営利活動(NPO)法人ワールド・ビジョン・ジャパンは、寄付・募金で世界の子どもを支援する国際協力NGO。貧困、紛争、災害など厳しい環境に生きる子どもたちに支援を届けるため、すべての子どもたちが健やかに成長できる世界を目指して活動しています。
Visit worldvision.jpWe analyzed Worldvision.jp page load time and found that the first response time was 524 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
worldvision.jp performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value31.3 s
0/100
25%
Value13.9 s
1/100
10%
Value670 ms
45/100
30%
Value0.237
53/100
15%
Value33.5 s
0/100
10%
524 ms
1061 ms
341 ms
517 ms
27 ms
Our browser made a total of 221 requests to load all elements on the main page. We found that 20% of them (44 requests) were addressed to the original Worldvision.jp, 11% (24 requests) were made to Static.xx.fbcdn.net and 6% (14 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Worldvision.jp.
Page size can be reduced by 264.6 kB (40%)
657.7 kB
393.2 kB
In fact, the total size of Worldvision.jp main page is 657.7 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. 60% of websites need less resources to load. Javascripts take 265.5 kB which makes up the majority of the site volume.
Potential reduce by 57.9 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 57.9 kB or 75% of the original size.
Potential reduce by 11.0 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. Worldvision images are well optimized though.
Potential reduce by 142.7 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 142.7 kB or 54% of the original size.
Potential reduce by 52.9 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. Worldvision.jp needs all CSS files to be minified and compressed as it can save up to 52.9 kB or 82% of the original size.
Number of requests can be reduced by 145 (74%)
195
50
The browser has sent 195 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Worldvision. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 71 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
worldvision.jp
524 ms
www.worldvision.jp
1061 ms
reset.css
341 ms
common.css
517 ms
jquery-1.11.2.min.js
27 ms
jquery.min.js
1031 ms
selectivizr-min.js
689 ms
tabs.js
767 ms
validationEngine.jquery.css
688 ms
fontplus.js
1009 ms
jquery.cookie.js
684 ms
easyselectbox.min.js
751 ms
login.js
852 ms
doubleclick.js
925 ms
common_wrap.css
853 ms
top.css
920 ms
succeed_param.js
930 ms
platform.js
91 ms
widgets.js
123 ms
wv_title.gif
190 ms
head_mywv_login.gif
187 ms
headIcon_fb.gif
259 ms
headIcon_twitter.gif
186 ms
headIcon_youtube.gif
188 ms
headIcon_blog.gif
187 ms
headSlide_childsponsor_btn.gif
380 ms
headSlide_childsponsor_btn02.gif
381 ms
news_detail.gif
381 ms
TOP_PC_477_226px.jpg
697 ms
news_ZAR_smartphone226x226.jpg
385 ms
PCtvtop.jpg
765 ms
eventInfo_detailBtn.jpg
601 ms
topBana_blog.gif
601 ms
topBana_houjin_shien.gif
601 ms
topBaba_ad.gif
601 ms
foot_graph.gif
779 ms
gtm.js
186 ms
sdk.js
339 ms
head_globalNavi.gif
769 ms
cse.js
208 ms
navi.gif
925 ms
1000x400PC.jpg
1264 ms
default_news_list.html
764 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
60 ms
cb=gapi.loaded_0
28 ms
cb=gapi.loaded_1
55 ms
fastbutton
112 ms
footer_bg.jpg
1163 ms
footList_icon.png
827 ms
footList_icon_sub.png
870 ms
postmessageRelay
97 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
75 ms
analytics.js
210 ms
conversion_async.js
197 ms
lb
180 ms
segmentation.js
206 ms
fbds.js
251 ms
so_sg.js
909 ms
m.js
827 ms
aiom.js
825 ms
so_sg.js
911 ms
pixel.js
703 ms
s_retargeting.js
1035 ms
nendRt.js
186 ms
top.js
681 ms
mone.64e97e852d9_2168.js
987 ms
fbevents.js
245 ms
lb
178 ms
cb=gapi.loaded_0
86 ms
cb=gapi.loaded_1
50 ms
0549.js
212 ms
jsapi
184 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
228 ms
api.js
106 ms
core:rpc:shindig.random:shindig.sha1.js
198 ms
2536007149-postmessagerelay.js
207 ms
246 ms
xd_arbiter.php
344 ms
jot
284 ms
210 ms
collect
58 ms
cnt
734 ms
redirect.js
734 ms
default+ja.css
50 ms
default+ja.I.js
98 ms
s
151 ms
t.js
185 ms
u
212 ms
200 ms
207 ms
default.css
23 ms
async-ads.js
115 ms
google_custom_search_watermark.gif
60 ms
small-logo.png
25 ms
search_box_icon.png
29 ms
clear.png
29 ms
input.gif
481 ms
btn.gif
516 ms
28 ms
ga-audiences
26 ms
52 ms
47 ms
s
37 ms
newsIcon_office.gif
262 ms
newsIcon_advocacy.gif
306 ms
newsIcon_press.gif
397 ms
KcDeqwasAgent.js
148 ms
aio
170 ms
Collection.aspx
154 ms
rtbsync.js
33 ms
pixel
42 ms
marking
225 ms
Sync.aspx
668 ms
Sync.aspx
651 ms
Sync.aspx
660 ms
Sync.aspx
665 ms
Sync.aspx
672 ms
Sync.aspx
656 ms
Sync.aspx
699 ms
Sync.aspx
699 ms
Sync.aspx
698 ms
Sync.aspx
671 ms
Sync.aspx
697 ms
Sync.aspx
658 ms
DynamicRetargetUserSync.aspx
693 ms
Collection.aspx
726 ms
csync
216 ms
csync
380 ms
pixel
168 ms
csync
173 ms
pix
180 ms
sd
5 ms
sync
208 ms
Sync.aspx
841 ms
cookiesync
651 ms
614 ms
pixel
22 ms
sd
16 ms
Pug
50 ms
is
817 ms
adv.js
75 ms
sync
171 ms
sync
14 ms
sync.ad-stir.com
245 ms
combo
163 ms
sync
8 ms
161 ms
dg_gateway.js
777 ms
Collection.aspx
154 ms
Collection.aspx
177 ms
adgeneration
325 ms
pb.html
28 ms
pixel
13 ms
630 ms
605 ms
606 ms
tap.php
437 ms
mapuser
151 ms
Collection.aspx
161 ms
Collection.aspx
154 ms
pixel
13 ms
Collection.aspx
158 ms
151 ms
adv_inner.js
13 ms
Collection.aspx
618 ms
beacon.html
11 ms
adv.aspx
942 ms
adv.aspx
1028 ms
like_box.php
210 ms
like.php
94 ms
sd
6 ms
pixel
16 ms
tap.php
288 ms
Pug
39 ms
mapuser
148 ms
set
638 ms
sync
826 ms
sync
29 ms
vpc6VNjRPXV.js
298 ms
LVx-xkvaJ0b.png
209 ms
sync
713 ms
9hoskrDulPm.css
118 ms
MrxxdBM8xso.css
121 ms
VYrT35wvj6g.css
132 ms
_rx8naC75Dy.js
199 ms
x5F9OMjKyLw.js
222 ms
ICDbTSzjQEg.js
154 ms
TTCre3391I0.js
172 ms
C-h3nYPqETO.js
215 ms
rFmE1g6Dkoz.js
301 ms
7cm7D75Y0Sf.js
251 ms
oRoBXlHCpEy.js
249 ms
336JejShbZp.js
249 ms
sj-JwAJi4AH.js
278 ms
DKRU1bYTkTw.js
256 ms
ZNPAadQNc33.js
263 ms
W0OV23mIOyO.js
277 ms
36TdwhIHusi.js
288 ms
1878_1044862648890176_6102358773305177049_n.jpg
120 ms
551894_380976538612127_659682029_n.jpg
118 ms
12187724_104874163208617_366352558615964927_n.jpg
124 ms
998597_349202728542401_978433115_n.jpg
124 ms
12744081_181291535575906_7066026616277241084_n.jpg
126 ms
12643000_161985450841022_5383658121623213971_n.jpg
126 ms
12670444_1852466751646627_2467212032650154948_n.jpg
124 ms
12541148_1547226925603554_8655202263815404096_n.jpg
126 ms
11350918_1674240349458984_1963063163232825313_n.jpg
148 ms
1908382_700848399983439_8688148091060851293_n.jpg
125 ms
12400579_936787916400605_2884019823307506695_n.jpg
126 ms
148429_114750565258738_4163382_n.jpg
126 ms
10629610_692019900874196_4936343442653584994_n.jpg
128 ms
10501729_1477879439117780_769174487330881940_n.jpg
129 ms
wL6VQj7Ab77.png
129 ms
s7jcwEQH7Sx.png
131 ms
pUFVdPjIRct.png
65 ms
I6-MnjEovm5.js
39 ms
vlXaquuXMrr.js
81 ms
sync
215 ms
sync
247 ms
dgcore.js
11 ms
adSiteVisit.js
23 ms
worldvision.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
worldvision.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
Issues were logged in the Issues panel in Chrome Devtools
worldvision.jp SEO score
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Worldvision.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 Worldvision.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.
worldvision.jp
Open Graph data is detected on the main page of Worldvision. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: