5.4 sec in total
556 ms
4.4 sec
454 ms
Click here to check amazing Cross A content. Otherwise, check out these important facts you probably never knew about cross-a.jp
zero+PLessenceシャンプー・zeroスノーウィーソープが大人気!クロス・エ・キューブ|ショッピングカート
Visit cross-a.jpWe analyzed Cross-a.jp page load time and found that the first response time was 556 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cross-a.jp performance score
name
value
score
weighting
Value6.8 s
1/100
10%
Value13.5 s
0/100
25%
Value10.3 s
8/100
10%
Value970 ms
28/100
30%
Value0.181
67/100
15%
Value15.2 s
7/100
10%
556 ms
748 ms
758 ms
35 ms
774 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 59% of them (54 requests) were addressed to the original Cross-a.jp, 13% (12 requests) were made to Static.xx.fbcdn.net and 7% (6 requests) were made to Ec-concier.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Cross-a.jp.
Page size can be reduced by 82.1 kB (4%)
1.9 MB
1.8 MB
In fact, the total size of Cross-a.jp main page is 1.9 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 26.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. This page needs HTML code to be minified as it can gain 13.7 kB, which is 44% 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.2 kB or 83% of the original size.
Potential reduce by 19.3 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. Cross A images are well optimized though.
Potential reduce by 35.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 35.1 kB or 20% of the original size.
Potential reduce by 1.5 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. Cross-a.jp needs all CSS files to be minified and compressed as it can save up to 1.5 kB or 20% of the original size.
Number of requests can be reduced by 35 (40%)
87
52
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cross A. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
cross-a.jp
556 ms
style.css
748 ms
jquery.slider.css
758 ms
jquery.min.js
35 ms
jquery.slider.min.js
774 ms
my-script.js
836 ms
lpcv.js
949 ms
conversion.js
113 ms
analytics.js
121 ms
gtm.js
163 ms
logo.jpg
228 ms
logo_2.jpg
403 ms
h_right_info.png
400 ms
gnav_top.png
401 ms
gnav_regular.png
401 ms
gnav_media.png
518 ms
gnav_voice.png
518 ms
gnav_qa.png
554 ms
gnav_cart.png
559 ms
cac_s_bnr_spt.jpg
1290 ms
dellaborn_bnr_0328.jpg
1103 ms
cac_s_bnr_soap.jpg
1444 ms
ttl_m_head.png
725 ms
ttl_m_zero.png
733 ms
img_rec_01.jpg
740 ms
products_btn01_off.png
932 ms
img_rec_02.jpg
913 ms
item-42.jpg
1843 ms
ttl_itemlist.png
1094 ms
bnr_m_zero01.jpg
1554 ms
teiki_bnr_2305.jpg
1815 ms
bnr_m_insta.jpg
1285 ms
bnr_ourstory.jpg
1651 ms
f_top_btn.gif
1471 ms
f_logo.png
1673 ms
nav_line.gif
219 ms
icn_hnav_login.png
219 ms
gnav_top.png
220 ms
gnav_all-item.png
223 ms
gnav_regular.png
393 ms
gnav_media.png
393 ms
gnav_voice.png
393 ms
gnav_qa.png
507 ms
gnav_cart.png
549 ms
info.html
1623 ms
itemlist.html
1728 ms
62 ms
collect
12 ms
js
85 ms
79 ms
collect
121 ms
destination
122 ms
arrow_l.png
333 ms
arrow_r.png
334 ms
collect
191 ms
js
64 ms
analytics.js
676 ms
ga-audiences
14 ms
analytics.js
333 ms
main.js
166 ms
style.css
186 ms
ttl_news_info.png
184 ms
main.js
191 ms
zero_item02.jpg
236 ms
zero_item03.jpg
473 ms
zero_item01.jpg
234 ms
item-43.jpg
479 ms
item-72-mobile.jpg
471 ms
item-54.jpg
1025 ms
zero_soap01.jpg
273 ms
zero_soap02.jpg
472 ms
zero_soap03.jpg
477 ms
sdk.js
15 ms
main.js
831 ms
sdk.js
8 ms
page.php
122 ms
GdFGhXfmgSQ.css
20 ms
Aq3fWRqzWdY.js
31 ms
o1ndYS2og_B.js
25 ms
vxmlpLbAeCj.js
26 ms
Q-X-GXL_I_5.js
26 ms
_02W6YRik00.js
27 ms
p55HfXW__mM.js
24 ms
k_PjgALRjoR.js
29 ms
qJoe20iyDr0.js
28 ms
302161732_499417038856285_5445238932480956849_n.jpg
69 ms
301371902_499417035522952_8666222610465573075_n.jpg
110 ms
_iENDDwY6Fe.js
36 ms
EcPi7SsydEO.js
31 ms
UXtr_j2Fwe-.png
30 ms
collect
258 ms
cross-a.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 toggle fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
cross-a.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
Browser errors were logged to the console
cross-a.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 Cross-a.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 Cross-a.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.
cross-a.jp
Open Graph description is not detected on the main page of Cross A. 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: