7.2 sec in total
788 ms
6 sec
397 ms
Visit elgin.jp now to see the best up-to-date Elgin content for Japan and also check out these interesting facts you probably never knew about elgin.jp
エルジン ELGIN 腕時計の専門店でございます。
Visit elgin.jpWe analyzed Elgin.jp page load time and found that the first response time was 788 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
elgin.jp performance score
788 ms
317 ms
342 ms
357 ms
309 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 66% of them (69 requests) were addressed to the original Elgin.jp, 8% (8 requests) were made to Rakuten.ne.jp and 5% (5 requests) were made to Thumbnail.image.rakuten.co.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Elgin.jp.
Page size can be reduced by 157.6 kB (25%)
641.4 kB
483.8 kB
In fact, the total size of Elgin.jp main page is 641.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 515.3 kB which makes up the majority of the site volume.
Potential reduce by 54.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. 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 54.4 kB or 82% of the original size.
Potential reduce by 56.4 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, Elgin needs image optimization as it can save up to 56.4 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 5.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 5.0 kB or 56% of the original size.
Potential reduce by 41.8 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. Elgin.jp needs all CSS files to be minified and compressed as it can save up to 41.8 kB or 82% of the original size.
Number of requests can be reduced by 53 (52%)
101
48
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elgin. 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 CSS and as a result speed up the page load time.
elgin.jp
788 ms
m_sys_common.css
317 ms
import.css
342 ms
script.js
357 ms
check_history.css
309 ms
pager.css
316 ms
shopdetail.css
331 ms
ranking.css
334 ms
basket.css
345 ms
security.css
360 ms
category_menu.css
649 ms
topicpath.css
661 ms
catalog.css
665 ms
count2.makeshop.jp
521 ms
24276-a.jpg
433 ms
fk1391s-bp-1.jpg
401 ms
hist11.jpg
612 ms
body_bg.png
184 ms
logo.gif
173 ms
hNav01.png
307 ms
hNav02.png
308 ms
hNav03.png
320 ms
hNav04.png
332 ms
headBasketSwitch1.png
502 ms
topimage_logo.jpg
1117 ms
searchTitle.png
648 ms
l_searchBtn.png
660 ms
categoryTitle.png
651 ms
l_memberBtn.png
664 ms
leftdot.gif
825 ms
bannertitle.gif
958 ms
syoutikubai_p3.jpg
1210 ms
syoutikubai_p1.jpg
1209 ms
syoutikubai_p4.jpg
1202 ms
syoutikubai_elgin.gif
1130 ms
syoutikubai_el.jpg
1286 ms
left_edge.gif
1443 ms
right_edge.gif
1439 ms
maintitle2.gif
1545 ms
0000000001813.jpg
1556 ms
0000000001803.jpg
1564 ms
0000000001793.jpg
1617 ms
0000000001783.jpg
1750 ms
0000000001773.jpg
1781 ms
0000000001723.jpg
1868 ms
0000000001743.jpg
1889 ms
0000000001713.jpg
1938 ms
0000000001703.jpg
1925 ms
0000000001693.jpg
2238 ms
icon2.gif
2086 ms
iconU.gif
2225 ms
0000000001673.jpg
2250 ms
watcser-image2.gif
401 ms
watcser-image1.gif
392 ms
rr1.gif
396 ms
rr2.gif
404 ms
rr3.gif
405 ms
rr4.gif
665 ms
rr5.gif
659 ms
fk1215s-b-1.jpg
951 ms
fk1392s-bp-1.jpg
260 ms
fk1381s-bp-1.jpg
266 ms
fk1315s-bp-1.jpg
239 ms
0010000001553.jpg
2216 ms
aq_tag_aos.js
141 ms
452 ms
maintitle1.gif
2083 ms
0010000001343.jpg
2224 ms
EM34BYVZ46DUGEQNJE6A
126 ms
0010000000993.jpg
2248 ms
0010000000753.jpg
2282 ms
0010000000853.jpg
2268 ms
review_title.gif
2269 ms
0010000001003.jpg
2285 ms
gmsync
302 ms
segmentation.js
49 ms
350 ms
cnt
385 ms
0010000001543.jpg
2087 ms
newstitle.gif
2210 ms
specialtitle.gif
2262 ms
0010000001163.jpg
2409 ms
pagetopBtn.png
2110 ms
gNav01.png
2090 ms
gNav02.png
2007 ms
gNav03.png
2040 ms
gNav04.png
2057 ms
gNav05.png
2077 ms
listIconR.png
2155 ms
starIcon1.png
2097 ms
footerDot.png
2041 ms
beacon.html
54 ms
pixel
21 ms
cs
347 ms
Pug
23 ms
set
305 ms
sd
5 ms
pixel
19 ms
tap.php
7 ms
sync
343 ms
sync
70 ms
sync
247 ms
mapuser
149 ms
sync
287 ms
elgin.jp SEO score
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elgin.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 Elgin.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.
elgin.jp
Open Graph description is not detected on the main page of Elgin. 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: