16.3 sec in total
1.1 sec
14.3 sec
979 ms
Click here to check amazing Agney content. Otherwise, check out these important facts you probably never knew about agney.jp
【アグニー公式サイト】 お名入れが人気! 出産祝い、お食い初め、離乳食に最適なこども用ナチュラル雑貨 agney* Official Web Site
Visit agney.jpWe analyzed Agney.jp page load time and found that the first response time was 1.1 sec and then it took 15.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
agney.jp performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value18.6 s
0/100
25%
Value17.1 s
0/100
10%
Value2,720 ms
3/100
30%
Value0.141
78/100
15%
Value31.9 s
0/100
10%
1090 ms
679 ms
512 ms
1062 ms
562 ms
Our browser made a total of 176 requests to load all elements on the main page. We found that 90% of them (159 requests) were addressed to the original Agney.jp, 1% (2 requests) were made to Google-analytics.com and 1% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (8.9 sec) belongs to the original domain Agney.jp.
Page size can be reduced by 1.1 MB (9%)
12.3 MB
11.1 MB
In fact, the total size of Agney.jp main page is 12.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 11.6 MB which makes up the majority of the site volume.
Potential reduce by 41.2 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 41.2 kB or 80% of the original size.
Potential reduce by 649.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. Agney images are well optimized though.
Potential reduce by 215.8 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 215.8 kB or 62% of the original size.
Potential reduce by 237.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. Agney.jp needs all CSS files to be minified and compressed as it can save up to 237.9 kB or 83% of the original size.
Number of requests can be reduced by 12 (7%)
169
157
The browser has sent 169 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Agney. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
agney.jp
1090 ms
cmn_layout.css
679 ms
cmn_style.css
512 ms
jquery.js
1062 ms
common.js
562 ms
jquery.min.js
34 ms
jquery.bxslider.min.js
750 ms
jquery.bxslider.css
682 ms
s_retargeting.js
529 ms
analytics.js
109 ms
MH5Wx5xOu-Y
144 ms
bg_main01.gif
375 ms
bg_border02.png
187 ms
bg_border01.png
214 ms
019.png
1542 ms
013.png
1506 ms
014.png
1526 ms
015.png
1244 ms
016.png
1692 ms
017.png
1645 ms
img_gnavi01_on.png
1422 ms
img_gnavi02_no.png
1599 ms
img_gnavi03_no.png
1692 ms
img_gnavi04_no.png
1694 ms
img_gnavi06_no.png
1709 ms
img_gnavi05_no.png
1776 ms
contents040_no.png
1827 ms
contents047_no.png
1878 ms
contents048_no.png
1880 ms
contents042_no.png
2033 ms
contents044_no.png
1880 ms
contents043_no.png
1952 ms
contents041_no.png
2011 ms
contents046_no.png
2065 ms
contents045_no.png
2069 ms
bg_contents02.png
2054 ms
txt_contents07_no.png
2129 ms
img_contents02_no.png
2193 ms
img_contents03_no.png
2204 ms
img_contents04_no.png
2226 ms
img_contents05_no.png
2441 ms
img_contents06_no.png
2444 ms
r001.png
2304 ms
r448.PNG
2376 ms
r447.PNG
2373 ms
r446.PNG
2396 ms
r445.PNG
2429 ms
sdk.js
199 ms
collect
32 ms
www-embed-player-vflfNyN_r.css
65 ms
www-embed-player.js
94 ms
collect
73 ms
cinecaption.eot.woff
2345 ms
ga-audiences
96 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
52 ms
ad_status.js
92 ms
r444.PNG
2311 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
86 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
88 ms
141 ms
xd_arbiter.php
148 ms
xd_arbiter.php
269 ms
r443.PNG
2203 ms
r442.PNG
1392 ms
r441.PNG
1216 ms
r440.PNG
1162 ms
r439.PNG
1193 ms
r438.PNG
1200 ms
r437.PNG
1145 ms
r436.PNG
1177 ms
r435.PNG
1135 ms
r434.PNG
1153 ms
r433.PNG
1195 ms
r432.PNG
1207 ms
r431.PNG
1154 ms
r430.PNG
1183 ms
r429.PNG
1135 ms
r428.PNG
1141 ms
r427.PNG
1178 ms
r426.PNG
1134 ms
r425.PNG
1099 ms
r424.PNG
1163 ms
r423.PNG
1146 ms
r422.PNG
1132 ms
r421.PNG
1158 ms
r420.PNG
1127 ms
r419.PNG
1097 ms
r418.PNG
1179 ms
r417.PNG
1146 ms
r416.PNG
1079 ms
r415.PNG
1019 ms
r414.PNG
1046 ms
r413.PNG
1070 ms
r412.PNG
1108 ms
r411.PNG
1126 ms
r410.PNG
1089 ms
404.html
1091 ms
r409.PNG
1005 ms
r408.PNG
1036 ms
r407.PNG
1093 ms
r406.PNG
1099 ms
r405.PNG
1102 ms
r404.PNG
1099 ms
r403.PNG
1050 ms
r402.PNG
1029 ms
r401.PNG
1097 ms
r400.PNG
1090 ms
r399.PNG
1084 ms
r398.PNG
1106 ms
r397.PNG
1065 ms
r396.PNG
1028 ms
r395.PNG
1097 ms
r394.PNG
1069 ms
r393.PNG
1074 ms
r392.PNG
1093 ms
r391.PNG
1080 ms
r390.PNG
1054 ms
r389.PNG
1098 ms
r388.PNG
1050 ms
r387.PNG
1066 ms
r386.PNG
1083 ms
r385.PNG
1098 ms
r384.PNG
1071 ms
r383.PNG
1097 ms
r382.PNG
1043 ms
r381.PNG
1057 ms
r380.PNG
1068 ms
r379.PNG
1117 ms
r378.PNG
1089 ms
img_contents07_no.png
1098 ms
img_contents08_no.png
1035 ms
bg_sub01.gif
1059 ms
bg_border_sub01.png
1129 ms
ico_shoplist02_no.png
1130 ms
r_nav_q&a_no.png
1157 ms
cinecaption.TTF
8859 ms
ico_note02_no.png
1648 ms
r_nav_album_no.png
1155 ms
ico_riveret_no.png
1134 ms
ico_recruit_no.png
1174 ms
r_nav_cotton_no.png
1399 ms
ico_bnr_hibana_no.png
1240 ms
img_copyright01.png
1178 ms
ico_tree02.png
1360 ms
img_gnavi02_on.png
1333 ms
img_gnavi03_on.png
1674 ms
img_gnavi04_on.png
1582 ms
img_gnavi06_on.png
1544 ms
img_gnavi05_on.png
1866 ms
contents040_on.png
2380 ms
contents047_on.png
2327 ms
contents048_on.png
1996 ms
contents042_on.png
2508 ms
contents044_on.png
2244 ms
contents043_on.png
2261 ms
contents041_on.png
2540 ms
contents046_on.png
2506 ms
contents045_on.png
2482 ms
txt_contents07_on.png
2369 ms
img_contents02_on.png
2601 ms
img_contents03_on.png
2655 ms
img_contents04_on.png
2857 ms
img_contents05_on.png
2894 ms
img_contents06_on.png
2807 ms
img_contents07_on.png
2645 ms
img_contents08_on.png
2694 ms
ico_shoplist02_on.png
2748 ms
r_nav_q&a_on.png
2826 ms
ico_note02_on.png
2765 ms
r_nav_album_on.png
2787 ms
ico_riveret_on.png
2748 ms
ico_recruit_on.png
2640 ms
r_nav_cotton_on.png
2744 ms
ico_bnr_hibana_on.png
2699 ms
bx_loader.gif
2583 ms
controls.png
2591 ms
agney.jp 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.
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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
agney.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
Page has valid source maps
agney.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Agney.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 Agney.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.
agney.jp
Open Graph description is not detected on the main page of Agney. 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: