Analyze

locknlock.tw: 樂扣樂扣

樂扣樂扣提供您超過800種生活用品,提供您各種尺寸與用途的專利設計四面環扣保鮮盒、不鏽鋼鍋具、不沾鍋與獨特造型且色彩豐富的保溫杯、且年年還會推出超過100個以上富有創造性的新品,不管是生活居家或是外出旅遊的商品,都在樂扣樂扣官方旗艦店。

Page load speed analysis

  • 52/100

    Normal result
  • 5

    Successful tests
  • 3

    Failed tests
  • First response

    843 ms

  • Resources loaded

    10.7 sec

  • Page rendered

    317 ms

  • Total page load time

    11.9 sec

Welcome to locknlock.tw homepage info - get ready to check Locknlock best content for Taiwan right away, or after learning these important things about locknlock.tw

We analyzed Locknlock.tw page load time and found that the first response time was 843 ms and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Page optimization

  • HTML 101.2 kB
    Images 10.6 MB
    Javascripts 698.4 kB
    CSS 477.0 kB

    In fact, the total size of Locknlock.tw main page is 11.9 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. 80% 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 10.6 MB which makes up the majority of the site volume.

    • Original 101.2 kB
    • After minification 63.4 kB
    • After compression 12.5 kB

    HTML optimization

    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 37.7 kB, which is 37% 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 88.7 kB or 88% of the original size.

    • Original 10.6 MB
    • After optimization 2.6 MB

    Image optimization

    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, Locknlock needs image optimization as it can save up to 8.0 MB or 76% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

    • Original 698.4 kB
    • After minification 676.6 kB
    • After compression 232.8 kB

    JavaScript optimization

    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 465.5 kB or 67% of the original size.

    • Original 477.0 kB
    • After minification 441.2 kB
    • After compression 72.5 kB

    CSS optimization

    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. Locknlock.tw needs all CSS files to be minified and compressed as it can save up to 404.5 kB or 85% of the original size.

Network requests diagram

  • locknlock.tw
  • index.php
  • fck_editorarea.css
  • df_style.css
  • style.css
  • hotfood_product.css
  • membercss.css
  • group.css
  • buycss.css
  • style.css
  • jquery.jscrollpane.css
  • jquery-1.9.1.min.js
  • jquery.masonry.min.js
  • jquery.slides.js
  • jquery.fancybox.css
  • jquery.fancybox.pack.js
  • jqtransform.css
  • jquery.jqtransform.js
  • jquery.loupe.min.js
  • jquery.jscrollpane.min.js
  • jquery.mousewheel.js
  • function.js
  • ij-ajax.js
  • _ij_package.js
  • dojo.js
  • jquery-1.9.1.min.js
  • cart_rightlist.png
  • logo.jpg
  • prod_sort_menu_10.jpg
  • prod_sort_menu_68.jpg
  • prod_sort_menu_84.jpg
  • prod_sort_menu_124.jpg
  • prod_sort_menu_11.jpg
  • prod_sort_menu_52.jpg
  • prod_sort_menu_64.jpg
  • prod_sort_menu_65.jpg
  • prod_sort_menu_74.jpg
  • conversion.js
  • prod_sort_menu_12.jpg
  • prod_sort_menu_69.jpg
  • prod_sort_menu_118.jpg
  • reset.css
  • reset.css
  • prod_sort_menu_27.jpg
  • prod_sort_menu_54.jpg
  • prod_sort_menu_75.jpg
  • reset.css
  • setting.css
  • prod_sort_menu_128.jpg
  • prod_sort_menu_131.jpg
  • prod_sort_menu_119.jpg
  • prod_sort_menu_120.jpg
  • prod_sort_menu_121.jpg
  • prod_sort_menu_71.gif
  • prod_sort_menu_16.jpg
  • prod_sort_menu_140.jpg
  • prod_sort_menu_73.jpg
  • prod_sort_menu_20.jpg
  • prod_sort_menu_78.jpg
  • prod_sort_menu_49.jpg
  • prod_sort_menu_108.jpg
  • prod_sort_menu_14.jpg
  • prod_sort_menu_111.jpg
  • prod_sort_menu_112.jpg
  • prod_sort_menu_129.jpg
  • prod_sort_menu_130.jpg
  • prod_sort_menu_83.jpg
  • prod_sort_menu_44.jpg
  • prod_sort_menu_85.jpg
  • prod_sort_menu_45.jpg
  • prod_sort_menu_107.jpg
  • prod_sort_menu_143.jpg
  • prod_sort_menu_86.jpg
  • prod_sort_menu_46.jpg
  • prod_sort_menu_87.jpg
  • prod_sort_menu_47.jpg
  • prod_sort_menu_105.jpg
  • prod_sort_menu_48.jpg
  • prod_sort_menu_88.jpg
  • prod_sort_menu_25.jpg
  • prod_sort_menu_89.jpg
  • prod_sort_menu_29.jpg
  • prod_sort_menu_141.jpg
  • prod_sort_menu_90.jpg
  • prod_sort_menu_31.jpg
  • prod_sort_menu_91.jpg
  • gtm.js
  • SuzYPWWp59Q
  • analytics.js
  • GweqQoZUE2U
  • fbevents.js
  • conversion_async.js
  • collect
  • collect
  • collect
  • Y0MsmytLhJs
  • collect
  • www-embed-player-vflZsBgOl.css
  • www-embed-player.js
  • base.js
  • api.shopping_cart.php
  • prod_sort_menu_37.jpg
  • ga-audiences
  • prod_sort_menu_92.jpg
  • prod_sort_menu_38.jpg
  • prod_sort_menu_95.jpg
  • 6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
  • ad_status.js
  • prod_sort_menu_77.jpg
  • prod_sort_menu_101.jpg
  • 2UX7WLTfW3W8TclTUvlFyQ.woff
  • RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
  • prod_sort_menu_79.jpg
  • prod_sort_menu_132.jpg
  • prod_sort_menu_133.jpg
  • prod_sort_menu_145.jpg
  • prod_sort_menu_146.jpg
  • wpicon_img_761.jpg
  • wpicon_img_755.jpg
  • wpicon_img_762.jpg
  • wpicon_img_758.jpg
  • wpicon_img_759.jpg
  • wpicon_img_760.jpg
  • %E7%B2%BE%E9%81%B8%E7%B5%84%E4%BB%B6%E5%A5%BD%E7%A6%AE%E5%84%AA%E6%83%A0-13.jpg
  • %E7%B2%BE%E9%81%B8%E7%B5%84%E4%BB%B6%E5%A5%BD%E7%A6%AE%E5%84%AA%E6%83%A0-11-2-1.jpg
  • %E6%9C%AA%E5%91%BD%E5%90%8D-2(1).jpg
  • Locknlock_ISO_9001.jpg
  • wpicon_img_492.jpg
  • lock_newImg11.jpg
  • lock_newImg12.jpg
  • lock_newImg13.jpg
  • lock_newImg07.jpg
  • lock_sImg01.jpg
  • lock_sImg02.jpg
  • lock_sImg03.jpg
  • lock_sImg04.jpg
  • lock_sImg05.jpg
  • lock_sImg06.jpg
  • footer_attests.jpg
  • copyright_logo.jpg
  • main_menu_bg.jpg
  • img_cartList-bg.png
  • img_shortcut_cartcar.png
  • btn_goCart.png
  • index_19.jpg
  • top_menu01_a.png
  • top_menu02_a.png
  • top_menu03_a.png
  • top_menu04_a.png
  • top_menu05_a.png
  • top_menu06_a.png
  • Tmenu06_car_line.gif
  • menu_home.gif
  • menu_line.gif
  • title_square_icon.gif
  • moreProduct_arrow.gif
  • lock_newImg08.jpg
  • lock_newIcon01.gif
  • lock_newIcon02.gif
  • footer_menu_icon01.png
  • footer_menu_icon02.png
  • footer_menu_icon03.png
  • footer_menu_icon04.png
  • footer_menu_icon05.png

Our browser made a total of 169 requests to load all elements on the main page. We found that 85% of them (144 requests) were addressed to the original Locknlock.tw, 2% (4 requests) were made to Google.com and 2% (3 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain Locknlock.tw.

Additional info on locknlock.tw

Requests

The browser has sent 161 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Locknlock. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.

22

Javascripts

118

Images

16

CSS

5

AJAX

161

All

Possible request optimization

1

Javascripts

92

Images

1

CSS

5

AJAX

62

Optimized

99

All

Normal result

Redirects

As for redirects, our browser was forwarded to http://locknlock.tw/locknlock/ before it reached this domain.

IP address

Locknlock.tw uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

locknlock.tw

levis.com.tw

lanew.com.tw

hushpuppies.com.tw

btu.com.tw

18.179.85.184

54.199.152.213

DNS records

Type Host Target/ip TTL Other
NS

locknlock.tw

cns2.net-chinese.com.tw 43200
NS

locknlock.tw

cns1.net-chinese.com.tw 43200
SOA

locknlock.tw

43200 Mname: cns1.net-chinese.com.tw
Rname: abuse.digiage.com.tw
Serial: 2012021713
Refresh: 28800
Retry: 7200
Expire: 691200
Minimum-ttl: 43200
MX

locknlock.tw

ALT3.ASPMX.L.GOOGLE.COM 43200 Pri: 8
MX

locknlock.tw

mxb.mailgun.org 43200 Pri: 10

Language and encoding

Good result

Language

ZH zh language flag

Detected

ZH zh language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Locknlock.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Locknlock.tw 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.

HTTPS certificate

SSL Certificate

Locknlock.tw has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 100% of all visits is Taiwan. It lies approximately 1400 miles away from the server location (Japan) and such a distance cannot critically affect website speed, but moving the server closer to their user base in Taiwan can speed up Locknlock.tw page load time anyway.

Normal result

Poor result

Social Sharing Optimization

Open Graph description is not detected on the main page of Locknlock. 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:

locknlock.tw

Share this report in social media

Analyze another website

Analyze