5.9 sec in total
605 ms
5 sec
241 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 605 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
cross-a.jp performance score
name
value
score
weighting
Value6.8 s
1/100
10%
Value12.4 s
0/100
25%
Value10.5 s
7/100
10%
Value140 ms
96/100
30%
Value0.186
66/100
15%
Value11.0 s
21/100
10%
605 ms
314 ms
690 ms
33 ms
727 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 10% of them (6 requests) were addressed to the original Cross-a.jp, 59% (35 requests) were made to Img11.shop-pro.jp and 7% (4 requests) were made to Img03.shop-pro.jp. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Img11.shop-pro.jp.
Page size can be reduced by 325.8 kB (27%)
1.2 MB
903.1 kB
In fact, the total size of Cross-a.jp main page is 1.2 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. 30% of websites need less resources to load. Images take 779.2 kB which makes up the majority of the site volume.
Potential reduce by 14.6 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 14.6 kB or 70% of the original size.
Potential reduce by 4.6 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 279.5 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 279.5 kB or 70% of the original size.
Potential reduce by 27.1 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 27.1 kB or 83% of the original size.
Number of requests can be reduced by 17 (29%)
58
41
The browser has sent 58 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 11 to 1 for JavaScripts and as a result speed up the page load time.
cross-a.jp
605 ms
cross-border-cart.css
314 ms
index.css
690 ms
jquery.min.js
33 ms
jquery.js
727 ms
jquery.innerfade.js
580 ms
widget.js
64 ms
gmo_header.js.php
337 ms
gmo_header.css.php
332 ms
cart.js
334 ms
product_stock.js
364 ms
li.php
310 ms
li.php
337 ms
acpt_n6r1c6.gif
730 ms
background.jpg
258 ms
logo.gif
303 ms
gn_itemlineup.gif
356 ms
gn_aboutzero.gif
301 ms
gn_aboutplessence.gif
281 ms
gn_media.gif
274 ms
gn_guide.gif
542 ms
gn_voice.gif
527 ms
gn_blog.gif
538 ms
gn_qa.gif
634 ms
gn_shopping.gif
633 ms
gn_contact.gif
637 ms
hn_mm.gif
799 ms
hn_cart.gif
831 ms
hn_shop.gif
808 ms
hn_blog.gif
928 ms
info.gif
908 ms
bn_login.gif
919 ms
bn_mem.gif
1064 ms
tp_bnr_plessence0722.jpg
1790 ms
tp_bnr_teiki_st.jpg
2030 ms
tp_bnr_prize.jpg
1692 ms
tp_bnr_zeroset.jpg
1912 ms
tp_bnr_plessence.jpg
1882 ms
tp_bnr_zero.jpg
1861 ms
btn_shopping.gif
1979 ms
media_bana.jpg
2293 ms
bihada_recipi_interview.jpg
2351 ms
tp_news_tit_03.gif
2105 ms
delivery_top.gif
2442 ms
bnr_teiki_plessence.jpg
2664 ms
bnr_tp_zero2.jpg
2479 ms
bihada_bnr.jpg
2531 ms
map_tp.gif
2504 ms
ga.js
15 ms
secure.shop-pro.jp
523 ms
__utm.gif
11 ms
jquery-1.6.4.min.js
1182 ms
easyXDM.min.js
545 ms
gmohd_logo2.gif
187 ms
login.gif
185 ms
regist.gif
184 ms
gmohd_bg.gif
5 ms
checkSession.do
946 ms
easyXDM.js
965 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
[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.
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
EUC-JP
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 euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
cross-a.jp
Open Graph data is detected on the main page of Cross A. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: