5.9 sec in total
468 ms
5.1 sec
395 ms
Click here to check amazing En Anifone content for Japan. Otherwise, check out these important facts you probably never knew about en.anifone.com
企業・場所・人々、世界を感動でつなぎ、笑顔をとどける。多様化する顧客接点をシームレスに結合すること、次世代マーケティングの新たなアイデアを創造すること、すべて、LEGSなら解決できます。
Visit en.anifone.comWe analyzed En.anifone.com page load time and found that the first response time was 468 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
en.anifone.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value4.2 s
45/100
25%
Value4.2 s
78/100
10%
Value930 ms
30/100
30%
Value0.079
94/100
15%
Value7.2 s
51/100
10%
468 ms
1385 ms
939 ms
575 ms
764 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original En.anifone.com, 96% (66 requests) were made to Legs.co.jp and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Legs.co.jp.
Page size can be reduced by 388.9 kB (25%)
1.6 MB
1.2 MB
In fact, the total size of En.anifone.com main page is 1.6 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. 25% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 26.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. This page needs HTML code to be minified as it can gain 5.6 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 26.9 kB or 83% of the original size.
Potential reduce by 71.8 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. En Anifone images are well optimized though.
Potential reduce by 255.2 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 255.2 kB or 68% of the original size.
Potential reduce by 35.0 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. En.anifone.com needs all CSS files to be minified and compressed as it can save up to 35.0 kB or 82% of the original size.
Number of requests can be reduced by 22 (33%)
67
45
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of En Anifone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
en.anifone.com
468 ms
www.legs.co.jp
1385 ms
default.css
939 ms
common.css
575 ms
home.css
764 ms
jquery.fancybox.css
573 ms
jquery.fancybox-buttons.css
383 ms
modernizr.js
956 ms
jquery-1.7.1.min.js
791 ms
jquery-ui-1.8.18.min.js
1782 ms
jquery.bgpos.js
207 ms
jquery.fancybox.pack.js
585 ms
jquery.fancybox-buttons.js
395 ms
jquery.hoverpanels.js
565 ms
jquery.autoheight.js
586 ms
common.js
587 ms
home.js
751 ms
zoomer.js
774 ms
txtHdTel.png
358 ms
icoHdMail.png
361 ms
icoHdPerson.png
521 ms
bgHd.png
1000 ms
logoHd.png
546 ms
navHd.png
1229 ms
topKeyVisualBack.png
1934 ms
topKeyVisualLogo.png
937 ms
topKeyVisualObjCng01.png
559 ms
topKeyVisualObjCng02.png
896 ms
topKeyVisualObjCng03.png
931 ms
topKeyVisualObjCng04.png
748 ms
topKeyVisualObjCng05.png
938 ms
topKeyVisualObjCng06.png
1276 ms
topKeyVisualObjCng07.png
1313 ms
topKeyVisualObj10.png
1128 ms
topKeyVisualObj11.png
1128 ms
topKeyVisualObj12.png
1317 ms
topKeyVisualObj14.png
1319 ms
topKeyVisualObj15.png
1463 ms
topKeyVisualObj16.png
1509 ms
topKeyVisualObj17.png
1509 ms
topKeyVisualObj27.png
1511 ms
topKeyVisualObj19.png
1547 ms
topKeyVisualObj20.png
1650 ms
topKeyVisualObj21.png
1696 ms
topKeyVisualObj22.png
1698 ms
topKeyVisualObj23.png
1667 ms
topKeyVisualObj24.png
1600 ms
topKeyVisualObj25.png
1680 ms
topKeyVisualObj26.png
1724 ms
topKeyVisualObj28.png
1730 ms
topKeyVisualObj29.png
1757 ms
topKeyVisualObj30.png
1582 ms
bgFt.png
836 ms
bgMain3Line.png
960 ms
topImg4strength.png
2399 ms
commonBrtLinkArrow.png
1556 ms
topTtl01.png
1543 ms
topBtnAbout.png
1761 ms
topBtnService.png
1574 ms
topBtnIr.png
1558 ms
topBtnCareer.png
1540 ms
irNewsIconPR.gif
1346 ms
irNewsIconOthers.gif
1534 ms
footerBtnBanner01.png
1515 ms
footerBtnBanner03.png
1387 ms
icoPankuzuHome.png
1512 ms
icoPankuzuArrow.png
211 ms
ga.js
24 ms
__utm.gif
10 ms
en.anifone.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
en.anifone.com 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
en.anifone.com 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise En.anifone.com 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 En.anifone.com 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.
en.anifone.com
Open Graph description is not detected on the main page of En Anifone. 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: