8.1 sec in total
1.2 sec
4.8 sec
2.1 sec
Visit a1record.com now to see the best up-to-date A1 RECORD content for Japan and also check out these interesting facts you probably never knew about a1record.com
supreme
Visit a1record.comWe analyzed A1record.com page load time and found that the first response time was 1.2 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
a1record.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value8.5 s
2/100
25%
Value10.4 s
8/100
10%
Value930 ms
30/100
30%
Value0.116
85/100
15%
Value13.0 s
12/100
10%
1169 ms
314 ms
334 ms
337 ms
222 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 12% of them (13 requests) were addressed to the original A1record.com, 55% (58 requests) were made to Img15.shop-pro.jp and 13% (14 requests) were made to Img.shop-pro.jp. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain A1record.com.
Page size can be reduced by 1.7 MB (16%)
10.1 MB
8.5 MB
In fact, the total size of A1record.com main page is 10.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. 85% 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 9.2 MB which makes up the majority of the site volume.
Potential reduce by 103.4 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 26.5 kB, which is 23% 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 103.4 kB or 89% of the original size.
Potential reduce by 971.5 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, A1 RECORD needs image optimization as it can save up to 971.5 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 335.0 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 335.0 kB or 66% of the original size.
Potential reduce by 255.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. A1record.com needs all CSS files to be minified and compressed as it can save up to 255.1 kB or 83% of the original size.
Number of requests can be reduced by 35 (34%)
103
68
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A1 RECORD. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
a1record.com
1169 ms
colormekit.css
314 ms
colormekit-responsive.css
334 ms
cross-border-cart.css
337 ms
index.css
222 ms
top.css
219 ms
jquery.min.js
20 ms
jquery.tile.js
34 ms
jquery.skOuterClick.js
32 ms
supersized.3.2.7.js
43 ms
supersized.shutter.js
33 ms
jquery.bxslider.css
331 ms
jquery.bxslider.min.js
331 ms
embed.js
160 ms
jquery.wookmark.min.js
13 ms
gmo_header.js.php
338 ms
gmo_header.css.php
545 ms
cart.js
541 ms
product_stock.js
554 ms
li.php
376 ms
li.php
375 ms
header_menu_btn.png
37 ms
slideshow_img0.JPG
69 ms
slideshow_img1.JPG
124 ms
slideshow_img2.JPG
130 ms
slideshow_img3.jpg
122 ms
slideshow_img4.jpg
125 ms
slideshow_img5.jpg
127 ms
98953403_th.jpg
126 ms
99052313_th.jpg
199 ms
99053142_th.jpg
158 ms
99053523_th.jpg
199 ms
99053890_th.jpg
147 ms
99058013_th.jpg
197 ms
99058227_th.jpg
196 ms
99106904_th.jpg
354 ms
99479829_th.jpg
234 ms
79896166_th.jpg
208 ms
88762988_th.jpg
266 ms
89670501_th.jpg
293 ms
90830579_th.jpg
251 ms
90832813_th.jpg
236 ms
94470825_th.jpg
338 ms
99053779_th.jpg
267 ms
99058149_th.jpg
361 ms
16833952_th.jpg
348 ms
35431048_th.jpg
350 ms
40031537_th.JPG
394 ms
55621674_th.jpg
361 ms
87151357_th.jpg
394 ms
87151997_th.jpg
362 ms
88765274_th.jpg
463 ms
90832860_th.jpg
437 ms
91861462_th.jpg
450 ms
91865775_th.jpg
442 ms
91904165_th.jpg
541 ms
91904172_th.jpg
450 ms
88759993_th.jpg
463 ms
icons15.gif
359 ms
icons16.gif
362 ms
icons1.gif
540 ms
card2.gif
25 ms
card6.gif
24 ms
card18.gif
24 ms
card0.gif
25 ms
card9.gif
25 ms
icon_16-w.png
24 ms
icon_16-b.png
23 ms
99053999_th.jpg
434 ms
99054470_th.jpg
434 ms
41539614_th.jpg
433 ms
56681037_th.jpg
433 ms
77075725_th.jpg
430 ms
91861791_th.jpg
432 ms
31482908_th.jpg
426 ms
cZpD9KbBZ2k
97 ms
54256205_th.jpg
409 ms
secure.shop-pro.jp
416 ms
62769875_th.jpg
365 ms
LLMCIqtD1mQ
99 ms
66075108_th.jpg
364 ms
72501356_th.jpg
365 ms
87076506_th.jpg
368 ms
99009579_th.jpg
369 ms
99011778_th.jpg
368 ms
99120432_th.jpg
389 ms
99120581_th.jpg
337 ms
www-embed-player-vflfNyN_r.css
28 ms
www-embed-player.js
53 ms
99120994_th.jpg
334 ms
99122309_th.jpg
327 ms
71605510_th.jpg
322 ms
qrcode.jpg
321 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
128 ms
ad_status.js
129 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
179 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
179 ms
progress.gif
61 ms
jquery-1.6.4.min.js
1151 ms
easyXDM.min.js
530 ms
gmohd_logo2.gif
212 ms
login.gif
210 ms
regist.gif
211 ms
gmohd_bg.gif
11 ms
checkSession.do
876 ms
easyXDM.js
820 ms
a1record.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.
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
Form elements do not have associated labels
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.
a1record.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
General
Impact
Issue
Detected JavaScript libraries
a1record.com 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 A1record.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 A1record.com 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.
a1record.com
Open Graph description is not detected on the main page of A1 RECORD. 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: