8.3 sec in total
713 ms
6.8 sec
807 ms
Click here to check amazing Hayakawa Online content for Japan. Otherwise, check out these important facts you probably never knew about hayakawa-online.co.jp
Visit hayakawa-online.co.jpWe analyzed Hayakawa-online.co.jp page load time and found that the first response time was 713 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hayakawa-online.co.jp performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value6.3 s
10/100
25%
Value9.0 s
14/100
10%
Value1,510 ms
14/100
30%
Value0.106
88/100
15%
Value8.6 s
37/100
10%
713 ms
471 ms
316 ms
321 ms
337 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 64% of them (90 requests) were addressed to the original Hayakawa-online.co.jp, 7% (10 requests) were made to Static.xx.fbcdn.net and 5% (7 requests) were made to Gigaplus.makeshop.jp. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Hayakawa-online.co.jp.
Page size can be reduced by 354.2 kB (23%)
1.5 MB
1.2 MB
In fact, the total size of Hayakawa-online.co.jp main page is 1.5 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.2 MB which makes up the majority of the site volume.
Potential reduce by 50.1 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 50.1 kB or 81% of the original size.
Potential reduce by 72.7 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. Hayakawa Online images are well optimized though.
Potential reduce by 125.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 125.2 kB or 77% of the original size.
Potential reduce by 106.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. Hayakawa-online.co.jp needs all CSS files to be minified and compressed as it can save up to 106.1 kB or 84% of the original size.
Number of requests can be reduced by 46 (33%)
138
92
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hayakawa Online. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
hayakawa-online.co.jp
713 ms
m_sys_common.css
471 ms
import.css
316 ms
script.js
321 ms
shop_category_item.js
337 ms
require.js
537 ms
check_history.css
324 ms
pager.css
339 ms
shopdetail.css
368 ms
ranking.css
357 ms
basket.css
467 ms
security.css
540 ms
category_menu.css
679 ms
topicpath.css
669 ms
catalog.css
672 ms
analytics.js
128 ms
odyssey_banner.jpg
689 ms
count3.makeshop.jp
809 ms
waywardpines_banner.jpg
679 ms
ah_banner.jpg
678 ms
hokankeikaku.jpg
1652 ms
watashiirobanner.jpg
930 ms
watashiirpbanner_thum.jpg
593 ms
hokankeikaku_thum.jpg
1323 ms
header-bg.png
195 ms
header-logo.png
560 ms
header-btn-01.png
362 ms
header-btn-cart.png
467 ms
gnav-01.png
466 ms
gnav-02.png
482 ms
gnav-03.png
583 ms
gnav-04.png
671 ms
gnav-05.png
734 ms
side-bnr-01.png
745 ms
side-title-01.png
791 ms
side-btn-search-01.png
800 ms
side-title-02.png
880 ms
side-bnr-03.jpg
1230 ms
side-bnr-04.jpg
1279 ms
axnmystery.jpg
1638 ms
facebook.jpg
1320 ms
twitter.jpg
1320 ms
niconico.jpg
1639 ms
ebooks.jpg
1638 ms
ebooksmp.jpg
1639 ms
bungaku.jpg
1900 ms
side-bnr-06.png
1916 ms
side-bnr-07.png
2044 ms
sp.png
2173 ms
sf-contest.jpg
2240 ms
agasa_7.jpg
2363 ms
sf-series.jpg
2826 ms
thum-sf-contest.jpg
2224 ms
thum-agasa_7.jpg
2357 ms
thum-sf-series.jpg
2661 ms
sub-01.png
2554 ms
left_edge.gif
2553 ms
right_edge.gif
2679 ms
sub-02.png
2677 ms
0000000131603.jpg
2813 ms
collect
25 ms
collect
191 ms
0000000131503.jpg
2757 ms
widgets.js
105 ms
aq_tag_aos.js
260 ms
500 ms
0000000131493.jpg
2538 ms
0000000131283.jpg
2583 ms
likebox.php
234 ms
sub-03.png
2575 ms
0000000131523.jpg
2614 ms
0000000131463.jpg
2699 ms
EM34BYVZ46DUGEQNJE6A
164 ms
0000000131293.jpg
2700 ms
timeline.fe2df323b0284f547735e29f610f34bf.js
19 ms
syndication
203 ms
523741717518753793
556 ms
main.min.js
2687 ms
p_TUZUiNrjI.css
167 ms
CkaAj0ofVuQ.css
176 ms
mm0vjjrXdxr.js
222 ms
Ta5YnQdNSFy.js
345 ms
XXn49zk5GnD.js
343 ms
OwNnuMlrnxQ.js
344 ms
0000000131163.jpg
2656 ms
sub-04.png
2643 ms
specialtitle.gif
2710 ms
gmsync
531 ms
segmentation.js
514 ms
555 ms
0000000131053.jpg
2786 ms
0000000131063.jpg
2731 ms
11934945_965626303504353_4535016407857412396_n.jpg
494 ms
15912_447006355366353_496258758_n.jpg
469 ms
12313615_781474148642624_6637618883050560220_n.jpg
468 ms
12715708_676450385831571_5848035781889329155_n.jpg
465 ms
1959439_717368535008441_3162577884343755365_n.jpg
464 ms
1453308_1658341431114302_5122200177825229485_n.jpg
465 ms
wL6VQj7Ab77.png
156 ms
s7jcwEQH7Sx.png
156 ms
0000000131133.jpg
2410 ms
0000000131143.jpg
2387 ms
0000000127373.jpg
2393 ms
0000000130903.jpg
2509 ms
cnt
450 ms
0000000131273.jpg
2304 ms
0000000130913.jpg
2314 ms
0000000131263.jpg
2382 ms
timeline.d6812d7a233cc6acdaf452b485c20172.default.css
15 ms
timeline.d6812d7a233cc6acdaf452b485c20172.default.css
13 ms
sub-05.png
2381 ms
wBg80dBy2Ra.js
11 ms
WIQcBxwlOXr.js
41 ms
072_normal.JPG
123 ms
OxKIoOB-_normal.jpg
224 ms
tHm7zVXR_normal.jpg
215 ms
7QHA43_W_normal.jpg
220 ms
yyQjX9G__normal.png
221 ms
Ca_azrZUcAAQb_H.jpg:small
221 ms
CbMZak2UYAI6qeB.jpg:small
222 ms
0000000094573.jpg
2145 ms
0000000130923.jpg
2271 ms
0000000130933.jpg
2235 ms
jot
24 ms
0000000131073.jpg
2106 ms
0000000131193.jpg
2127 ms
0000000131313.jpg
2111 ms
0000000131303.jpg
1991 ms
0000000130983.jpg
2148 ms
0000000130443.jpg
2028 ms
0000000131153.jpg
2035 ms
footer-logo.png
2026 ms
arrow.png
2007 ms
icon-arr-01.png
2029 ms
slide-prev.png
2005 ms
slide-next.png
2017 ms
css_browser_selector.js
1592 ms
jquery.min.js
32 ms
init.js
1649 ms
script.min.js
1662 ms
hayakawa-online.co.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.
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
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.
hayakawa-online.co.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
hayakawa-online.co.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 Hayakawa-online.co.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 Hayakawa-online.co.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.
hayakawa-online.co.jp
Open Graph description is not detected on the main page of Hayakawa Online. 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: