2.9 sec in total
748 ms
2 sec
142 ms
Click here to check amazing Eco Splax content for Japan. Otherwise, check out these important facts you probably never knew about eco.splax.net
オンラインお絵かき「エココロ」…みんなでお絵かき!
Visit eco.splax.netWe analyzed Eco.splax.net page load time and found that the first response time was 748 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
eco.splax.net performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value2.7 s
85/100
25%
Value3.0 s
94/100
10%
Value80 ms
99/100
30%
Value0
100/100
15%
Value3.9 s
88/100
10%
748 ms
336 ms
507 ms
383 ms
571 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 44% of them (19 requests) were addressed to the original Eco.splax.net, 16% (7 requests) were made to Apis.google.com and 7% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (798 ms) belongs to the original domain Eco.splax.net.
Page size can be reduced by 48.9 kB (22%)
226.1 kB
177.1 kB
In fact, the total size of Eco.splax.net main page is 226.1 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. 35% of websites need less resources to load. Images take 173.2 kB which makes up the majority of the site volume.
Potential reduce by 6.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. 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 6.8 kB or 63% of the original size.
Potential reduce by 17.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. Eco Splax images are well optimized though.
Potential reduce by 12.1 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 12.1 kB or 44% of the original size.
Potential reduce by 12.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. Eco.splax.net needs all CSS files to be minified and compressed as it can save up to 12.9 kB or 90% of the original size.
Number of requests can be reduced by 22 (55%)
40
18
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eco Splax. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
eco.splax.net
748 ms
common.js
336 ms
putflash.js
507 ms
common.css
383 ms
menu.css
571 ms
top.css
379 ms
oekkec.js
371 ms
widgets.js
5 ms
plusone.js
96 ms
urchin.js
45 ms
alert130726.gif
352 ms
eco120508_1.jpg
568 ms
eco120508_2.gif
359 ms
background.jpg
757 ms
eco120508_3.jpg
337 ms
eco120508_4.jpg
200 ms
eco120508_5.gif
387 ms
eco120508_6.jpg
798 ms
exp_top.gif
470 ms
spacer.gif
505 ms
fig1.gif
574 ms
exp_bottom.gif
650 ms
cb=gapi.loaded_0
31 ms
cb=gapi.loaded_1
51 ms
fastbutton
222 ms
__utm.gif
22 ms
statistics.asp
153 ms
track.js
173 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
54 ms
like.php
100 ms
postmessageRelay
71 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
18 ms
api.js
37 ms
core:rpc:shindig.random:shindig.sha1.js
68 ms
2536007149-postmessagerelay.js
54 ms
vpc6VNjRPXV.js
487 ms
LVx-xkvaJ0b.png
550 ms
track-visibility.aspx
188 ms
push
203 ms
jot
113 ms
cb=gapi.loaded_0
25 ms
cb=gapi.loaded_1
19 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
93 ms
eco.splax.net 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
eco.splax.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
eco.splax.net 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
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eco.splax.net 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 Eco.splax.net main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
eco.splax.net
Open Graph description is not detected on the main page of Eco Splax. 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: