5.5 sec in total
560 ms
4.7 sec
300 ms
Visit etoys.jp now to see the best up-to-date Etoys content for Japan and also check out these interesting facts you probably never knew about etoys.jp
たのしく学べるプログラミング教室です。小学校や科学館でもScratch(スクラッチ)やTurtle Graphics(タートルグラフィックス)、Python(パイソン)を利用した講座を開催してます。
Visit etoys.jpWe analyzed Etoys.jp page load time and found that the first response time was 560 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
etoys.jp performance score
name
value
score
weighting
Value3.7 s
31/100
10%
Value11.6 s
0/100
25%
Value7.4 s
28/100
10%
Value590 ms
50/100
30%
Value0.2
62/100
15%
Value10.9 s
21/100
10%
560 ms
174 ms
320 ms
344 ms
346 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 83% of them (101 requests) were addressed to the original Etoys.jp, 5% (6 requests) were made to Pagead2.googlesyndication.com and 4% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Etoys.jp.
Page size can be reduced by 570.4 kB (63%)
912.7 kB
342.2 kB
In fact, the total size of Etoys.jp main page is 912.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. 45% of websites need less resources to load. CSS take 354.4 kB which makes up the majority of the site volume.
Potential reduce by 29.7 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 6.0 kB, which is 17% 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 29.7 kB or 83% of the original size.
Potential reduce by 27.1 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, Etoys needs image optimization as it can save up to 27.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 200.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 200.9 kB or 66% of the original size.
Potential reduce by 312.7 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. Etoys.jp needs all CSS files to be minified and compressed as it can save up to 312.7 kB or 88% of the original size.
Number of requests can be reduced by 89 (75%)
118
29
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Etoys. 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 27 to 1 for CSS and as a result speed up the page load time.
etoys.jp
560 ms
style.css
174 ms
_else.css
320 ms
style.css
344 ms
index.css
346 ms
script.js
517 ms
show_ads.js
19 ms
common.css
223 ms
pagelayout.css
473 ms
printlayout.css
345 ms
blockskin.css
347 ms
wp_style.css
181 ms
overwrite.css
249 ms
style.css
368 ms
theme.css
175 ms
_else.css
176 ms
style.css
392 ms
_else.css
163 ms
jquery-1.8.3.min.js
684 ms
jquery.easing.1.3.js
179 ms
head.load.min.js
177 ms
movie.js
324 ms
parts.js
346 ms
fx.js
356 ms
override.js
363 ms
load.js
484 ms
analytics.js
82 ms
002back2.gif
183 ms
topimage_new.gif
393 ms
square_wht_right.gif
165 ms
square_wht_right.gif
175 ms
square_wht_right.gif
179 ms
real_col_homea.gif
181 ms
real_col_sun.gif
331 ms
real_col_moon.gif
349 ms
real_col_world.png
356 ms
real_col_photo.gif
351 ms
1_bf2_tl.png
383 ms
1_bf2_tr.png
491 ms
1_bf2_tc.png
524 ms
1_bf2_ml.png
529 ms
1_bf2_mr.png
530 ms
1_bf2_bg.png
553 ms
point-title.gif
591 ms
img20160207203413760862.jpg
1122 ms
plain_wht_right.gif
697 ms
img20160221210211883775.png
699 ms
flat_12_red.png
711 ms
plain_wht_right.gif
727 ms
1_bf2_bl.png
791 ms
1_bf2_br.png
875 ms
1_bf2_bc.png
875 ms
point-title.gif
885 ms
flat_12_red.png
927 ms
flat_12_red.png
987 ms
flat_12_red.png
1047 ms
plain_gry_right.gif
1048 ms
index_bg.gif
1057 ms
point-title.gif
1116 ms
plain_wht_right.gif
1182 ms
sign.jpg
1212 ms
point-title.gif
1213 ms
ca-pub-1920945524327076.js
171 ms
zrt_lookup.html
168 ms
show_ads_impl.js
174 ms
plain_wht_right.gif
1189 ms
collect
57 ms
collect
183 ms
_area_side_a.css
1127 ms
_area_billboard.css
1112 ms
_area_main.css
1212 ms
_area_header.css
1214 ms
_area_side_b.css
1213 ms
ads
153 ms
osd.js
86 ms
ads
344 ms
ads
273 ms
ga-audiences
194 ms
_area_footer.css
1095 ms
_block_footer.css
1097 ms
_block_header.css
1119 ms
_block_side_a.css
1228 ms
_block_side_b.css
1182 ms
_block_billboard.css
1176 ms
_block_main.css
1107 ms
sign.jpg
1241 ms
point-title.gif
1114 ms
plain_wht_right.gif
1208 ms
mindmap.jpg
1196 ms
point-title.gif
1189 ms
m_js_controller.js
231 ms
abg.js
305 ms
plain_wht_right.gif
1076 ms
sign.jpg
1119 ms
point-title.gif
1208 ms
loading.png
1195 ms
plain_wht_right.png
1137 ms
favicon
165 ms
googlelogo_color_112x36dp.png
174 ms
nessie_icon_tiamat_white.png
117 ms
hr.gif
1071 ms
8fba98a8f978eq.jpg
1101 ms
20110605pm.jpg
1107 ms
938c8ec589c88aw8ad9.jpg
1173 ms
x_button_blue2.png
93 ms
s
30 ms
20150221.jpg
1110 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
33 ms
8ed96y.jpg
1040 ms
83j8381838a83a.jpg
1243 ms
img_0481.jpg
1118 ms
20140629a.jpg
1048 ms
8cfa96d88es8fee95f183v838983u.jpg
1130 ms
e82c682d282a082a982aa82ed.jpg
1084 ms
p1000021.jpg
1053 ms
1_ic_bdprint3.png
1126 ms
1_ic_bdtext3_s.png
1139 ms
1_ic_bdtext3_m.png
1132 ms
1_ic_bdtext3_l.png
1156 ms
plain_wht_right.png
1057 ms
plain_gry_right.gif
1078 ms
activeview
37 ms
etoys.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
Links do not have a discernible name
etoys.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
etoys.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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Etoys.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 Etoys.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.
etoys.jp
Open Graph data is detected on the main page of Etoys. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: