26.3 sec in total
728 ms
24.4 sec
1.2 sec
Visit glasseye.co.jp now to see the best up-to-date Glass Eye content for Japan and also check out these interesting facts you probably never knew about glasseye.co.jp
ルアー&クラフト【グラスアイ】ではバス釣りのトップウォーターをメインに釣具の通販・販売しています。トップウォーター用のウッド製のオリジナルルアーからグラスロッド、グラスアイスティックからオフセットのアルミハンドルまで取扱っています。
Visit glasseye.co.jpWe analyzed Glasseye.co.jp page load time and found that the first response time was 728 ms and then it took 25.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
glasseye.co.jp performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value30.7 s
0/100
25%
Value26.0 s
0/100
10%
Value1,370 ms
16/100
30%
Value0.57
12/100
15%
Value28.6 s
0/100
10%
728 ms
977 ms
444 ms
654 ms
460 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 65% of them (84 requests) were addressed to the original Glasseye.co.jp, 11% (14 requests) were made to Maps.googleapis.com and 5% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (19.6 sec) belongs to the original domain Glasseye.co.jp.
Page size can be reduced by 617.9 kB (27%)
2.3 MB
1.7 MB
In fact, the total size of Glasseye.co.jp main page is 2.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. 75% 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 43.8 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 43.8 kB or 86% of the original size.
Potential reduce by 27.8 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. Glass Eye images are well optimized though.
Potential reduce by 513.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 513.0 kB or 68% of the original size.
Potential reduce by 33.4 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. Glasseye.co.jp needs all CSS files to be minified and compressed as it can save up to 33.4 kB or 78% of the original size.
Number of requests can be reduced by 47 (39%)
121
74
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Glass Eye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
glasseye.co.jp
728 ms
www.glasseye.co.jp
977 ms
import.css
444 ms
mt.js
654 ms
cube.site.js
460 ms
cube.win_op.js
473 ms
jquery.min.js
185 ms
jquery.easing.1.3.js
472 ms
jquery.mousewheel.js
650 ms
jquery.rollOver.js
896 ms
jquery.slideImage.js
903 ms
jquery.fullSlide.js
2040 ms
jquery.customScroll.js
1791 ms
jquery.droppy.js
1101 ms
fixHeight.js
1125 ms
shadowbox.js
1662 ms
js
184 ms
config.js.php
1340 ms
ga.js
1496 ms
w_js.php
1304 ms
bookmark_button.js
424 ms
base.css
1323 ms
content.css
1451 ms
dmanager.css
1468 ms
shop.css
1612 ms
shop-other.css
1746 ms
shadowbox.css
1783 ms
extra.css
1879 ms
analytics.js
117 ms
bg.jpg
408 ms
header-bg.jpg
409 ms
logo.jpg
588 ms
header-contact.jpg
418 ms
header-tel.jpg
406 ms
gnav01.jpg
436 ms
gnav02.jpg
818 ms
gnav03.jpg
819 ms
gnav04.jpg
836 ms
gnav05.jpg
835 ms
gnav06.jpg
843 ms
data-141202120300.jpg
3108 ms
data-150319141402.jpg
2941 ms
data-141202123601.jpg
6181 ms
data-141129180103.jpg
2262 ms
data-141202134448.jpg
4557 ms
data-150319141703.jpg
3672 ms
data-141118160558.jpg
4174 ms
data-141118160419.jpg
4201 ms
data-141118160711.jpg
4618 ms
data-141202140025.jpg
6856 ms
newblog-title.jpg
4643 ms
2016324144126_t235x190.JPG
6490 ms
201624152215_t235x190.jpg
5266 ms
news-title.jpg
5647 ms
recommend-title.jpg
6247 ms
next.jpg
6035 ms
resize_image.php
6140 ms
resize_image.php
6573 ms
resize_image.php
6634 ms
resize_image.php
6672 ms
resize_image.php
6780 ms
resize_image.php
6980 ms
resize_image.php
7200 ms
resize_image.php
7232 ms
maps
190 ms
resize_image.php
7203 ms
collect
72 ms
plusone.js
186 ms
widgets.js
105 ms
embed
50 ms
js
189 ms
init_embed.js
138 ms
cb=gapi.loaded_0
35 ms
resize_image.php
6893 ms
prev.jpg
6899 ms
shopmenu-title.jpg
7225 ms
or.jpg
18611 ms
oh.jpg
15857 ms
common.js
53 ms
util.js
179 ms
streetview.js
100 ms
google_white4.png
38 ms
marker.js
95 ms
og.jpg
17875 ms
imagery_viewer.js
204 ms
controls.js
54 ms
op.jpg
13224 ms
GeoPhotoService.GetMetadata
129 ms
ov.jpg
18254 ms
os.jpg
11787 ms
oa.jpg
19634 ms
ol.jpg
14286 ms
transparent.png
75 ms
css
370 ms
geocoder.js
61 ms
sv4.png
153 ms
openhand_8_8.cur
253 ms
mapcnt6.png
286 ms
tmapctrl.png
309 ms
cbk
646 ms
GeoPhotoService.GetMetadata
81 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
222 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
319 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
372 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
473 ms
cbk
625 ms
cbk
360 ms
cbk
624 ms
cbk
626 ms
cbk
622 ms
data-150319132721.jpg
13841 ms
data-141210142834.jpg
13491 ms
data-141125192141.jpg
15914 ms
access-title.jpg
13376 ms
mainbanner.jpg
13336 ms
mainbanner02.jpg
13709 ms
mainbanner03.jpg
13727 ms
pagetop.jpg
14135 ms
footer-logo.jpg
14254 ms
common.js
59 ms
util.js
110 ms
stats.js
77 ms
AuthenticationService.Authenticate
358 ms
frame.png
13871 ms
stats.js
34 ms
AuthenticationService.Authenticate
40 ms
shopmenu-bg.jpg
13623 ms
QuotaService.RecordEvent
44 ms
13399 ms
glasseye.co.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.
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
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.
glasseye.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
glasseye.co.jp SEO score
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 Glasseye.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 Glasseye.co.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.
glasseye.co.jp
Open Graph description is not detected on the main page of Glass Eye. 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: