10 sec in total
1.2 sec
8.1 sec
796 ms
Click here to check amazing Anicom S content. Otherwise, check out these important facts you probably never knew about anicom-s.jp
ペット保険シェア15年連続NO.1の「アニコム損保」の保険は圧倒的な使いやすさが魅力!全国6,900以上の動物病院で窓口精算、LINEでの保険金請求が可能。犬・猫はもちろん、鳥・うさぎ・フェレットのペット保険もご用意しております。
Visit anicom-s.jpWe analyzed Anicom-s.jp page load time and found that the first response time was 1.2 sec and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
anicom-s.jp performance score
name
value
score
weighting
Value10.7 s
0/100
10%
Value13.0 s
0/100
25%
Value26.8 s
0/100
10%
Value2,750 ms
3/100
30%
Value0.001
100/100
15%
Value39.0 s
0/100
10%
1199 ms
510 ms
847 ms
852 ms
855 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Anicom-s.jp, 3% (3 requests) were made to Cache.dga.jp and 2% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Anicom-sompo.co.jp.
Page size can be reduced by 1.1 MB (26%)
4.1 MB
3.1 MB
In fact, the total size of Anicom-s.jp main page is 4.1 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 3.2 MB which makes up the majority of the site volume.
Potential reduce by 63.3 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 11.9 kB, which is 15% 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 63.3 kB or 81% of the original size.
Potential reduce by 343.4 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, Anicom S needs image optimization as it can save up to 343.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 387.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 387.2 kB or 71% of the original size.
Potential reduce by 291.2 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. Anicom-s.jp needs all CSS files to be minified and compressed as it can save up to 291.2 kB or 87% of the original size.
Number of requests can be reduced by 28 (29%)
96
68
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Anicom S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.anicom-sompo.co.jp
1199 ms
analytics.js
510 ms
base.css
847 ms
layout.css
852 ms
layout_sp.css
855 ms
colorbox.css
518 ms
contents.css
848 ms
contents_sp.css
1352 ms
swiper-bundle.min.css
36 ms
slick.css
690 ms
jquery.mCustomScrollbar.css
1200 ms
top.css
1185 ms
top_sp.css
1021 ms
jquery.js
2035 ms
distinction.js
1026 ms
jquery.colorbox-min.js
1193 ms
common.js
1368 ms
simulation.js
1356 ms
swiper-bundle.min.js
56 ms
slick.js
1537 ms
jquery.mCustomScrollbar.concat.min.js
1372 ms
top.js
1522 ms
form.js
1529 ms
form_caliculate_select_animal.js
1540 ms
get_wp_json.js
1544 ms
calc.js
1529 ms
altUrl.js
1199 ms
gtm.js
101 ms
as_logo.svg
271 ms
icon_01.png
173 ms
icon_02.png
274 ms
icon_03.png
275 ms
icon_04.png
276 ms
header_logo04.svg
274 ms
header_logo06.svg
344 ms
header_logo05.svg
357 ms
header_logo03.svg
346 ms
main11.jpg
685 ms
main11_sp.jpg
520 ms
main09.jpg
1028 ms
main09_sp.jpg
851 ms
main07.jpg
687 ms
main07_sp.jpg
697 ms
main10.jpg
1875 ms
main10_sp.jpg
1364 ms
main04.png
1199 ms
main04_sp.png
1040 ms
share_no1_sp.png
1189 ms
share_no1.png
1199 ms
reason01.png
1215 ms
navi.svg
1361 ms
reason02.png
1370 ms
reason03.png
1372 ms
reason04.png
1388 ms
index_im02.png
1532 ms
index_im04.png
1534 ms
index_information02.jpg
1541 ms
index_information03.jpg
1544 ms
index_information01.jpg
1559 ms
index_recommend_meimeisho.png
2211 ms
index_prevention09.png
1711 ms
index_prevention01.jpg
1715 ms
index_prevention03.jpg
1715 ms
index_prevention04.jpg
1715 ms
search_tool_n3.js
861 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
0 ms
posts
1912 ms
index_prevention08.jpg
1618 ms
index_prevention07.png
1618 ms
index_prevention05.jpg
1634 ms
index_service04.png
1774 ms
index_service05.png
1782 ms
index_service02.jpg
1720 ms
oricon_pc.svg
2749 ms
oricon_sp.svg
2877 ms
group_logo.svg
1715 ms
header_ic01.png
1551 ms
header_ic02.png
1667 ms
header_ic03.png
1688 ms
com_ic05.png
1560 ms
com_ic02.png
1380 ms
pc_family.png
1994 ms
pc_petit.png
1534 ms
pc_senior.png
1548 ms
index_im09_2.jpg
1383 ms
index_im10_2.jpg
1540 ms
index_im11_2.jpg
1534 ms
doc1.jpg
1724 ms
doc2.jpg
1740 ms
dog.png
2033 ms
cat.png
1987 ms
com_ic18.png
1727 ms
aside_ic01.png
1731 ms
com_ic30.png
1725 ms
com_ic36.png
1860 ms
new_i_search_assist.js
613 ms
new_ac.css
794 ms
header_ic04.png
173 ms
anicom-s.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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
anicom-s.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
anicom-s.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
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 Anicom-s.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 Anicom-s.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.
anicom-s.jp
Open Graph data is detected on the main page of Anicom S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: