6 sec in total
944 ms
4.8 sec
240 ms
Click here to check amazing ELEPHANT content. Otherwise, check out these important facts you probably never knew about elephant.ne.jp
Visit elephant.ne.jpWe analyzed Elephant.ne.jp page load time and found that the first response time was 944 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.
elephant.ne.jp performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value3.3 s
69/100
25%
Value5.3 s
59/100
10%
Value0 ms
100/100
30%
Value0.021
100/100
15%
Value1.4 s
100/100
10%
944 ms
225 ms
18 ms
447 ms
438 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 99% of them (70 requests) were addressed to the original Elephant.ne.jp, 1% (1 request) were made to Adobe.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Elephant.ne.jp.
Page size can be reduced by 125.8 kB (24%)
518.3 kB
392.4 kB
In fact, the total size of Elephant.ne.jp main page is 518.3 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 498.4 kB which makes up the majority of the site volume.
Potential reduce by 16.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 3.2 kB, which is 16% 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 16.7 kB or 84% of the original size.
Potential reduce by 109.2 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, ELEPHANT needs image optimization as it can save up to 109.2 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Number of requests can be reduced by 18 (26%)
69
51
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ELEPHANT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
elephant.ne.jp
944 ms
swfobject_modified.js
225 ms
get_flash_player.gif
18 ms
background.jpg
447 ms
spacer.gif
438 ms
index-s_r1_c1.jpg
460 ms
index-s_r1_c2.jpg
456 ms
index-s_r1_c5.jpg
467 ms
index-s_r1_c6.jpg
469 ms
index-s_r1_c7.jpg
664 ms
index-s_r1_c8.jpg
669 ms
index-s_r1_c9.jpg
684 ms
index-s_r1_c12.jpg
686 ms
index-s_r1_c13.jpg
695 ms
index-s_r2_c1.jpg
699 ms
home.jpg
882 ms
whatnews.jpg
893 ms
products.jpg
904 ms
support.jpg
906 ms
register.jpg
920 ms
faq.jpg
929 ms
contact.jpg
1098 ms
special.jpg
1113 ms
index-s_r2_c13.jpg
1131 ms
index-s_r3_c1.jpg
1135 ms
index-s_r3_c2.jpg
1145 ms
index-s_r3_c4.jpg
1160 ms
index-s_r3_c5.jpg
1325 ms
index-s_r3_c6.jpg
1335 ms
index-s_r3_c7.jpg
1357 ms
index-s_r3_c8.jpg
1356 ms
index-s_r3_c9.jpg
1370 ms
index-s_r3_c12.jpg
1392 ms
index-s_r3_c13.jpg
1542 ms
index-s_r4_c1.jpg
1558 ms
index-s_r4_c13.jpg
1810 ms
index-s_r5_c1.jpg
1578 ms
index-s_r5_c2.jpg
1599 ms
index-s_r5_c3.jpg
1623 ms
index-s_r5_c10.jpg
1339 ms
index-s_r5_c11.jpg
1344 ms
index-s_r5_c13.jpg
1358 ms
banner_corner_left.jpg
1376 ms
bottom_banner_topic.jpg
1412 ms
banner_corner_right.jpg
1530 ms
wega-icon.jpg
1355 ms
index-s_r7_c2.jpg
1367 ms
20160301_1b322.jpg
1578 ms
20160301_41ac4.jpg
1826 ms
20160301_51be7.jpg
1648 ms
20160301_84447.jpg
1736 ms
20160108_8b266.jpg
1583 ms
20160108_212ed.jpg
1587 ms
20160107_722b2.jpg
1801 ms
20160107_57b51.jpg
1902 ms
20160107_085e1.jpg
1950 ms
20160107_31295.jpg
1983 ms
20151223_c9cb8.jpg
1825 ms
20151223_9b200.jpg
1847 ms
banner_corner_right_s.jpg
1797 ms
banner_corner_left_b.jpg
1905 ms
index-s_r8_c3.jpg
1944 ms
banner_corner_right_b.jpg
1973 ms
home_f2.jpg
238 ms
whatnews_f2.jpg
230 ms
products_f2.jpg
244 ms
support_f2.jpg
235 ms
register_f2.jpg
235 ms
faq_f2.jpg
238 ms
contact_f2.jpg
448 ms
special_f2.jpg
456 ms
elephant.ne.jp accessibility score
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
<object> elements do not have alternate text
elephant.ne.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
elephant.ne.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
Document uses plugins
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elephant.ne.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Elephant.ne.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.
elephant.ne.jp
Open Graph description is not detected on the main page of ELEPHANT. 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: