7.4 sec in total
2 sec
4.9 sec
389 ms
Welcome to livat.cn homepage info - get ready to check Livat best content for China right away, or after learning these important things about livat.cn
Visit livat.cnWe analyzed Livat.cn page load time and found that the first response time was 2 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
livat.cn performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value5.3 s
21/100
25%
Value4.0 s
80/100
10%
Value170 ms
93/100
30%
Value0
100/100
15%
Value5.3 s
72/100
10%
2039 ms
795 ms
394 ms
489 ms
497 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 80% of them (32 requests) were addressed to the original Livat.cn, 5% (2 requests) were made to Staticxx.facebook.com and 3% (1 request) were made to Tjs.sjs.sinajs.cn. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Livat.cn.
Page size can be reduced by 416.8 kB (25%)
1.7 MB
1.3 MB
In fact, the total size of Livat.cn main page is 1.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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 21.6 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 4.4 kB, which is 15% 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 21.6 kB or 74% of the original size.
Potential reduce by 41.9 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. Livat images are well optimized though.
Potential reduce by 230.4 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 230.4 kB or 67% of the original size.
Potential reduce by 123.0 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. Livat.cn needs all CSS files to be minified and compressed as it can save up to 123.0 kB or 83% of the original size.
Number of requests can be reduced by 10 (26%)
39
29
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Livat. 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 JavaScripts and as a result speed up the page load time.
www.livat.cn
2039 ms
responsive_white.css
795 ms
require.js
394 ms
addtohomescreen.css
489 ms
addtohomescreen.min.js
497 ms
wb.js
7 ms
tracker.js
6 ms
topBanner_white.gif
277 ms
logo.ashx
17 ms
uparrow.png
18 ms
wk.ashx
20 ms
transparent_466x466.png
17 ms
wuxi230230.ashx
420 ms
beijin230230.ashx
418 ms
wuhan230230.ashx
434 ms
index02-4.ashx
323 ms
index03-1.ashx
368 ms
index03-2.ashx
371 ms
index03-3.ashx
371 ms
index03-4.ashx
419 ms
begin470.ashx
804 ms
index-btn02.ashx
373 ms
index-btn01.ashx
375 ms
index-btn03.ashx
378 ms
ikea-centres-logo-footer.png
379 ms
MainLayout.js
928 ms
config.js
671 ms
gtm.js
78 ms
all.js
16 ms
menu_delimiter.png
651 ms
top_title.png
646 ms
arrow_white_redback_9x9_right.gif
660 ms
bg_cookie.png
880 ms
loading1.gif
1488 ms
bundle.js
1738 ms
71 ms
xd_arbiter.php
37 ms
xd_arbiter.php
50 ms
jquery-1.11.1.min.js
375 ms
responsive.js
235 ms
livat.cn 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
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.
livat.cn best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
livat.cn 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 doesn't use legible font sizes
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Livat.cn can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Livat.cn 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.
livat.cn
Open Graph description is not detected on the main page of Livat. 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: