3.6 sec in total
623 ms
2.9 sec
60 ms
Visit locksy.com now to see the best up-to-date LOCKSY content and also check out these interesting facts you probably never knew about locksy.com
Locksy is an Korean kitchenware company that has been making everyday life better, fresher and smarter, with kitchenware that are beautiful design
Visit locksy.comWe analyzed Locksy.com page load time and found that the first response time was 623 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
locksy.com performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value9.4 s
0/100
25%
Value11.3 s
5/100
10%
Value140 ms
95/100
30%
Value0
100/100
15%
Value8.3 s
40/100
10%
623 ms
20 ms
191 ms
378 ms
380 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 71% of them (30 requests) were addressed to the original Locksy.com, 12% (5 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Locksy.com.
Page size can be reduced by 41.8 kB (3%)
1.4 MB
1.3 MB
In fact, the total size of Locksy.com main page is 1.4 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. 35% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 14.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. This page needs HTML code to be minified as it can gain 2.2 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.8 kB or 77% of the original size.
Potential reduce by 233 B
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. LOCKSY images are well optimized though.
Potential reduce by 23.3 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 23.3 kB or 24% of the original size.
Potential reduce by 3.6 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. Locksy.com needs all CSS files to be minified and compressed as it can save up to 3.6 kB or 14% of the original size.
Number of requests can be reduced by 20 (59%)
34
14
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LOCKSY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
locksy.com
623 ms
xeicon.min.css
20 ms
default.css
191 ms
font-awesome.min.css
378 ms
aos.css
380 ms
common.css
382 ms
mobile_navi.css
381 ms
jquery-1.12.4.min.js
564 ms
jquery-migrate-1.4.1.min.js
385 ms
common.js
575 ms
wrest.js
576 ms
placeholders.min.js
577 ms
gsap.min.js
46 ms
ScrollTrigger.min.js
68 ms
pushy.js
579 ms
aos.js
579 ms
jquery.fullPage.css
760 ms
jquery.fullPage.js
941 ms
player.js
60 ms
jquery.easing.1.3.js
773 ms
jquery.ui.totop.min.js
773 ms
main.js
772 ms
xeicon.min.css
34 ms
css2
28 ms
nb-icon.svg
198 ms
fb-icon.svg
375 ms
it-icon.svg
395 ms
yt-icon.svg
380 ms
top-logo.svg
379 ms
f-logo.svg
396 ms
view-arrow01.svg
560 ms
view-arrow02.svg
561 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoyeLQ.ttf
76 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzztgyeLQ.ttf
221 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzrQyeLQ.ttf
250 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzg01eLQ.ttf
267 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzkM1eLQ.ttf
247 ms
xeicon.ttf
24 ms
main2-bg01.jpg
941 ms
main3-bg01.jpg
1131 ms
main4-bg01.jpg
1321 ms
page-up.jpg
195 ms
locksy.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
locksy.com 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
General
Impact
Issue
Detected JavaScript libraries
locksy.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Locksy.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 Locksy.com 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.
locksy.com
Open Graph data is detected on the main page of LOCKSY. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: