5.3 sec in total
812 ms
3.1 sec
1.3 sec
Click here to check amazing Liekr content for Thailand. Otherwise, check out these important facts you probably never knew about liekr.com
Visit liekr.comWe analyzed Liekr.com page load time and found that the first response time was 812 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
liekr.com performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value3.4 s
65/100
25%
Value10.4 s
8/100
10%
Value5,890 ms
0/100
30%
Value0.185
66/100
15%
Value19.0 s
3/100
10%
812 ms
96 ms
93 ms
74 ms
118 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Liekr.com, 76% (48 requests) were made to Image.liekr.com and 5% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (926 ms) relates to the external source Image.liekr.com.
Page size can be reduced by 160.6 kB (16%)
979.3 kB
818.7 kB
In fact, the total size of Liekr.com main page is 979.3 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. 60% of websites need less resources to load. Images take 776.9 kB which makes up the majority of the site volume.
Potential reduce by 52.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. This page needs HTML code to be minified as it can gain 12.2 kB, which is 20% 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 52.4 kB or 86% of the original size.
Potential reduce by 6.1 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. Liekr images are well optimized though.
Potential reduce by 32.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 32.0 kB or 60% of the original size.
Potential reduce by 70.1 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. Liekr.com needs all CSS files to be minified and compressed as it can save up to 70.1 kB or 79% of the original size.
Number of requests can be reduced by 6 (10%)
61
55
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Liekr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
liekr.com
812 ms
comA.min.css
96 ms
lk_style.css
93 ms
jquery.min.js
74 ms
comB.min.css
118 ms
com.min.js
91 ms
www.liekr.com
875 ms
liekr_logo.png
127 ms
ui_icon_third.png
108 ms
searchIcon.png
106 ms
1375691456804932.jpg
103 ms
144141456803749.jpg
100 ms
603441456802463.jpg
103 ms
703321456801900.jpg
100 ms
1617531456801378.jpg
112 ms
891961456801259.jpg
105 ms
938121456800903.jpg
108 ms
370761456800389.jpg
106 ms
1532941456800071.jpg
109 ms
859871456687470.jpg
108 ms
1057551456480514.jpg
113 ms
1348311456479330.jpg
112 ms
1368601456477896.jpg
113 ms
199391456475655.jpg
112 ms
1117241456473877.jpg
112 ms
107021456472127.jpg
112 ms
617001456469760.jpg
126 ms
820651456467974.jpg
112 ms
1586261456467011.jpg
126 ms
390071456465615.jpg
113 ms
1509671455765414.jpg
115 ms
1564281456287009.jpg
112 ms
649221455862877.jpg
113 ms
261851455874131.jpg
117 ms
1144091456294282.jpg
116 ms
593701455677916.jpg
114 ms
1875301455695975.jpg
116 ms
1749231456124554.jpg
117 ms
356001455873741.jpg
117 ms
1181301456121100.jpg
118 ms
1824691456130532.jpg
121 ms
1743601455852536.jpg
117 ms
1526791455874553.jpg
121 ms
1133071455874421.jpg
39 ms
1682031455879920.jpg
37 ms
846461456357186.jpg
35 ms
1267651456128218.jpg
879 ms
1654241455872932.jpg
921 ms
478881456283140.jpg
926 ms
1191181456138321.jpg
888 ms
scrolltop.png
31 ms
all.js
78 ms
plusone.js
113 ms
widgets.js
17 ms
analytics.js
31 ms
collect
59 ms
collect
126 ms
99 ms
cb=gapi.loaded_0
26 ms
73 ms
xd_arbiter.php
93 ms
xd_arbiter.php
166 ms
xd_arbiter.php
40 ms
liekr.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
liekr.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
Browser errors were logged to the console
Page has valid source maps
liekr.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
TH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Liekr.com can be misinterpreted by Google and other search engines. Our service has detected that Thai is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Liekr.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.
liekr.com
Open Graph description is not detected on the main page of Liekr. 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: