4.6 sec in total
870 ms
3.4 sec
272 ms
Click here to check amazing Sharp GALAPAGOS content for Japan. Otherwise, check out these important facts you probably never knew about sharpgalapagos.jp
シャープ株式会社 GALAPAGOS公式ポータルサイト。シャープ 株式会社が運営する国内最大級の配信点数を誇る総合電子書籍ストア「GALAPAGOS STORE(ガラパゴスストア)」のサービス、Android/iOS/Windows対応アプリや対応端末の紹介をおこなっています。
Visit sharpgalapagos.jpWe analyzed Sharpgalapagos.jp page load time and found that the first response time was 870 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
sharpgalapagos.jp performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value5.6 s
17/100
25%
Value2.5 s
97/100
10%
Value0 ms
100/100
30%
Value0.003
100/100
15%
Value1.9 s
100/100
10%
870 ms
493 ms
493 ms
370 ms
895 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 41% of them (48 requests) were addressed to the original Sharpgalapagos.jp, 19% (22 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Sharpgalapagos.jp.
Page size can be reduced by 161.0 kB (15%)
1.1 MB
923.5 kB
In fact, the total size of Sharpgalapagos.jp main page is 1.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. 70% of websites need less resources to load. Images take 862.9 kB which makes up the majority of the site volume.
Potential reduce by 10.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 10.6 kB or 69% of the original size.
Potential reduce by 17.2 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. Sharp GALAPAGOS images are well optimized though.
Potential reduce by 92.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 92.5 kB or 59% of the original size.
Potential reduce by 40.7 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. Sharpgalapagos.jp needs all CSS files to be minified and compressed as it can save up to 40.7 kB or 81% of the original size.
Number of requests can be reduced by 47 (41%)
115
68
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sharp GALAPAGOS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
sharpgalapagos.jp
870 ms
reset.css
493 ms
style.css
493 ms
flexslider.css
370 ms
jquery.js
895 ms
ga.js
35 ms
gnavi_bg.jpg
169 ms
logo.gif
169 ms
btn_home.gif
185 ms
btn_products.gif
340 ms
img_search.gif
341 ms
btn_go.gif
366 ms
img_galapagos.gif
583 ms
btn_support.gif
368 ms
gnavi_img.jpg
831 ms
gnavi_img_right.jpg
515 ms
slide004.jpg
2368 ms
line_dot.gif
705 ms
border.png
734 ms
banner001.jpg
1099 ms
banner002.jpg
1097 ms
news_bg.gif
733 ms
news.jpg
903 ms
mark.jpg
900 ms
obi01.gif
998 ms
btn001.jpg
1084 ms
btn002.jpg
1087 ms
btn003.jpg
1167 ms
btn006.jpg
1233 ms
btn007.jpg
1254 ms
btn008.jpg
1282 ms
obi02.gif
1280 ms
img_ttl_twitter.gif
1331 ms
snavi01.jpg
1400 ms
snavi02.jpg
1420 ms
snavi03.jpg
1466 ms
snavi04.jpg
1466 ms
snavi05.jpg
1496 ms
snavi06.jpg
1566 ms
snavi07.jpg
1585 ms
widgets.js
19 ms
530 ms
snavi08.jpg
1636 ms
__utm.gif
12 ms
likebox.php
466 ms
like.php
195 ms
share.jpg
1487 ms
share_de.jpg
1501 ms
share_mx.jpg
1554 ms
qeKvIRsJabD.js
38 ms
LVx-xkvaJ0b.png
30 ms
share_yh.jpg
1424 ms
share_gg.jpg
1498 ms
pagetop.jpg
1475 ms
copyright.jpg
1466 ms
410ucuAGgaJ.css
10 ms
tSbl8xBI27R.css
15 ms
Czh0gDTFcBt.css
24 ms
Ek6lpayKeeB.css
42 ms
EoarYgA68t4.css
24 ms
q68gy-v_YMF.js
39 ms
FJmpeSpHpjS.js
58 ms
0wM5s1Khldu.js
57 ms
1bNoFZUdlYZ.js
38 ms
njO1TPvGzoR.js
56 ms
1QuX41zDRrx.js
56 ms
Oagsvfb4VWi.js
67 ms
LTv6ZK-5zxz.js
70 ms
1FCa-btixu2.js
68 ms
img_ttl_facebook.gif
1391 ms
style.css
187 ms
main.js
711 ms
229882_443462289028201_550948323_n.jpg
127 ms
safe_image.php
176 ms
safe_image.php
86 ms
safe_image.php
84 ms
safe_image.php
72 ms
safe_image.php
70 ms
484144_410421635665600_1202203892_n.jpg
59 ms
10698499_709317472492358_177365665875625338_n.jpg
60 ms
944948_932776476797960_8758350725288237203_n.jpg
63 ms
11221356_1015669405159533_5209005423035145542_n.jpg
66 ms
1779073_256007971239635_1515467124_n.jpg
63 ms
426985_174935055953730_1430106221_n.jpg
64 ms
10354686_10150004552801856_220367501106153455_n.jpg
66 ms
12360309_925866404158212_3429808493048844505_n.jpg
83 ms
wL6VQj7Ab77.png
54 ms
s7jcwEQH7Sx.png
47 ms
QDwYpIaRyfG.png
55 ms
K00K-UgnsKu.png
47 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
55 ms
syndication
93 ms
342105014510182403
151 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
5 ms
proxy.jpg
100 ms
proxy.jpg
76 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
6 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
8 ms
72VFA85z_normal.png
150 ms
CdzyvPUUAAAjpG1.jpg:small
250 ms
CdziGuNUIAAjwR_.jpg:small
331 ms
CdzT4fpUsAAQNgS.jpg:small
157 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
50 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
59 ms
proxy.jpg
28 ms
proxy.jpg
53 ms
loading.gif
176 ms
jot.html
2 ms
data.xml
176 ms
sstb-BT000020676901501501900207_001_03.jpg
207 ms
BT000012685703103101900206_001_00_resize.jpg
200 ms
sstb-BT000021164101901901900206_001_03.jpg
202 ms
mbj-20005_121004152_l.jpg
203 ms
img11000020160314221541015.jpg
206 ms
btn_store.jpg
352 ms
sharpgalapagos.jp accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
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>).
sharpgalapagos.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
sharpgalapagos.jp SEO score
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sharpgalapagos.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 Sharpgalapagos.jp main page’s claimed encoding is shift_jis. 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.
sharpgalapagos.jp
Open Graph description is not detected on the main page of Sharp GALAPAGOS. 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: