6.9 sec in total
1 sec
5.6 sec
257 ms
Welcome to opticsmuseum.com homepage info - get ready to check Optics Museum best content right away, or after learning these important things about opticsmuseum.com
▒ 안경박물관 ▒ 옵틱스뮤지엄 ▒
Visit opticsmuseum.comWe analyzed Opticsmuseum.com page load time and found that the first response time was 1 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
opticsmuseum.com performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value1.8 s
98/100
25%
Value1.8 s
100/100
10%
Value0 ms
100/100
30%
Value0.001
100/100
15%
Value1.8 s
100/100
10%
1015 ms
391 ms
398 ms
5 ms
626 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 62% of them (72 requests) were addressed to the original Opticsmuseum.com, 22% (25 requests) were made to Scontent.cdninstagram.com and 4% (5 requests) were made to Snapwidget.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Opticsmuseum.com.
Page size can be reduced by 1.4 MB (52%)
2.7 MB
1.3 MB
In fact, the total size of Opticsmuseum.com main page is 2.7 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. 55% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 14.0 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 2.0 kB, which is 11% 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 14.0 kB or 74% of the original size.
Potential reduce by 1.2 MB
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, Optics Museum needs image optimization as it can save up to 1.2 MB or 51% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 83.1 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 83.1 kB or 53% of the original size.
Potential reduce by 51.9 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. Opticsmuseum.com needs all CSS files to be minified and compressed as it can save up to 51.9 kB or 81% of the original size.
Number of requests can be reduced by 26 (23%)
114
88
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Optics Museum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
opticsmuseum.com
1015 ms
common.js
391 ms
cid.generate.js
398 ms
wcslog.js
5 ms
optimizer.php
626 ms
optimizer.php
927 ms
1623 ms
2364 ms
top_banner.jpg
870 ms
logo_banner.jpg
838 ms
top_logo.png
621 ms
top_in.jpg
812 ms
top_join.jpg
627 ms
top_my.jpg
1032 ms
top_cart.jpg
1038 ms
top_order.jpg
922 ms
left_01.png
1054 ms
left_02.png
1057 ms
skin4_category24_menu.png
1091 ms
skin4_category29_menu.png
1148 ms
skin4_category30_menu.png
1231 ms
skin4_category31_menu.png
1242 ms
skin4_category25_menu.png
1269 ms
left_03.png
1264 ms
left_04.png
1286 ms
left_05.png
1361 ms
main_img01.jpg
2408 ms
main_img02.jpg
2251 ms
main_img03.jpg
2248 ms
main_img04.jpg
2457 ms
main_banner01.jpg
2087 ms
main_banner02.jpg
2235 ms
main_banner03.jpg
2692 ms
insta-title.jpg
2714 ms
insta-title-02.jpg
2659 ms
banner_03.png
2481 ms
banner_02.png
2601 ms
banner_04.png
2653 ms
banner_05.png
2685 ms
banner_06.png
2802 ms
banner_01.png
2851 ms
banner_07.png
2853 ms
m
511 ms
quickR_blog.jpg
2663 ms
quickR_face.jpg
2276 ms
quickR_top.jpg
2310 ms
weblog.js
629 ms
SubCategory
2251 ms
bottom_info.jpg
3032 ms
bottom_info_01.jpg
2419 ms
company_info.jpg
2987 ms
company_banner_ssl.jpg
2203 ms
company_banner_cafe24.jpg
2230 ms
company_banner_es.jpg
2230 ms
top_line.png
2346 ms
left_dot.png
2333 ms
top_logo_1.png
2252 ms
top_in_1.jpg
2301 ms
top_join_1.jpg
2372 ms
top_my_1.jpg
2409 ms
top_cart_1.jpg
2395 ms
top_order_1.jpg
2384 ms
combined.css
22 ms
smoothDivScroll.css
5 ms
stack_161235.js
57 ms
jquery.min.js
6 ms
analytics.js
27 ms
stackpile.api-6712054ce0.js
28 ms
12822377_190423368003731_1469727842_n.jpg
351 ms
12568923_1295000330516235_2091461917_a.jpg
398 ms
11821832_114740312255516_770274646_n.jpg
604 ms
12822490_437337353129194_1586107517_n.jpg
590 ms
924264_1584127328574322_329956327_a.jpg
532 ms
12822412_225881727758229_722463406_n.jpg
690 ms
12725101_1134622023223474_1611752476_a.jpg
617 ms
stackpile.api-6712054ce0.js
14 ms
collect
3 ms
collect
57 ms
left_01_1.png
1739 ms
left_02_1.png
1638 ms
left_03_1.png
1630 ms
left_04_1.png
1696 ms
bg.png
14 ms
10296638_230610513956977_739695571_n.jpg
140 ms
12139609_471402933053381_2069376078_n.jpg
146 ms
12822490_437337353129194_1586107517_n.jpg
111 ms
12822412_225881727758229_722463406_n.jpg
151 ms
12751015_958118657611224_66151771_n.jpg
153 ms
12677730_238331449833871_1103475761_n.jpg
176 ms
12677693_1706411792949254_1563769582_n.jpg
237 ms
12677690_1652168075046262_1558731949_n.jpg
267 ms
12547650_1021462517917939_1306149919_n.jpg
267 ms
12407296_1033186250071107_1081571770_n.jpg
596 ms
12568738_1757322104497059_1111996737_n.jpg
298 ms
12558662_870864786366074_785630862_n.jpg
333 ms
12568131_1230665416948592_1440454729_n.jpg
381 ms
12558548_157234714650352_1547549805_n.jpg
412 ms
12446098_1221299701237101_1660369633_n.jpg
427 ms
925496_1696029200616230_128295585_n.jpg
427 ms
12346239_1494605474180887_1019014069_n.jpg
487 ms
12345725_933049383468766_710120718_n.jpg
546 ms
collect
3 ms
nr-885.min.js
42 ms
left_05_1.png
1620 ms
a53393d12f
47 ms
banner_03_1.png
1614 ms
banner_02_1.png
1593 ms
banner_04_1.png
1489 ms
banner_05_1.png
1493 ms
banner_06_1.png
1568 ms
banner_01_1.png
1534 ms
banner_07_1.png
1576 ms
quickR_blog_1.jpg
1558 ms
quickR_face_1.jpg
1486 ms
quickR_top_1.jpg
1496 ms
a53393d12f
23 ms
opticsmuseum.com accessibility score
opticsmuseum.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
opticsmuseum.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Opticsmuseum.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Korean language. Our system also found out that Opticsmuseum.com main page’s claimed encoding is euc-kr. 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.
opticsmuseum.com
Open Graph description is not detected on the main page of Optics Museum. 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: