6.4 sec in total
495 ms
5.2 sec
775 ms
Welcome to lativ.com.tw homepage info - get ready to check Lativ best content for Taiwan right away, or after learning these important things about lativ.com.tw
lativ 台灣網路服飾品牌,提供平價且高品質的衣服,線上可直接購買女裝、男裝、嬰兒裝、童裝、帆布鞋等。
Visit lativ.com.twWe analyzed Lativ.com.tw page load time and found that the first response time was 495 ms 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.
lativ.com.tw performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value10.2 s
0/100
25%
Value21.7 s
0/100
10%
Value1,320 ms
17/100
30%
Value1.254
1/100
15%
Value25.8 s
0/100
10%
495 ms
908 ms
801 ms
1219 ms
1030 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 6% of them (5 requests) were addressed to the original Lativ.com.tw, 76% (62 requests) were made to S.lativ.com.tw and 2% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source S.lativ.com.tw.
Page size can be reduced by 729.6 kB (16%)
4.7 MB
3.9 MB
In fact, the total size of Lativ.com.tw main page is 4.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 3.7 MB which makes up the majority of the site volume.
Potential reduce by 44.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 44.4 kB or 83% of the original size.
Potential reduce by 67.3 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. Lativ images are well optimized though.
Potential reduce by 461.7 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 461.7 kB or 62% of the original size.
Potential reduce by 156.2 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. Lativ.com.tw needs all CSS files to be minified and compressed as it can save up to 156.2 kB or 80% of the original size.
Number of requests can be reduced by 15 (19%)
78
63
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lativ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
lativ.com.tw
495 ms
www.lativ.com.tw
908 ms
bundle.css
801 ms
LativJS.js
1219 ms
lativ_ywa.js
1030 ms
StaticPage.css
425 ms
jquery.bxslider.js
645 ms
jquery.lazyload.js
442 ms
conversion.js
16 ms
logo-2011.gif
222 ms
btn_search.gif
204 ms
nav-menus.gif
422 ms
1180X570_0225_17_0.jpg
823 ms
1180X570_0225_3_0.jpg
1071 ms
1180x570_160130_8_0.jpg
797 ms
1180x570_160130_3_0.jpg
609 ms
1180X570_0225_1_0.jpg
1319 ms
1180x570_160130_2_0.jpg
1053 ms
1180x570_160130_6_0.jpg
1013 ms
1180X570_0225_17.jpg
1195 ms
1180X570_0225_3.jpg
1232 ms
1180x570_160130_8.jpg
1418 ms
1180x570_160130_3.jpg
1474 ms
1180X570_0225_1.jpg
1498 ms
1180x570_160130_2.jpg
1395 ms
1180x570_160130_6.jpg
1438 ms
grey.gif
1539 ms
ShoppingCart.gif
1568 ms
web_icon.gif
1595 ms
analytics.js
61 ms
104 ms
86 ms
fbds.js
115 ms
yql
131 ms
yql
204 ms
ytc.js
75 ms
bat.js
66 ms
225 ms
bx_loader.gif
1556 ms
mainpic_arrowleft.png
1597 ms
mainpic_arrowright.png
1627 ms
collect
12 ms
collect
71 ms
45 ms
42 ms
25 ms
223 ms
mainpic_circule.png
221 ms
icon20160129_news2.gif
221 ms
icon_line.gif
229 ms
icon_cn151013.gif
259 ms
icon_overseas150902.gif
285 ms
20160226_01.gif
331 ms
20160226_01-1.jpg
364 ms
20160226_01-2.jpg
441 ms
20160226_01-3.jpg
425 ms
20160226_02.gif
467 ms
20160226_02-1.jpg
488 ms
20160226_02-2.jpg
541 ms
20160226_02-3.jpg
576 ms
20160226_02-4.jpg
624 ms
20160226_03.gif
660 ms
20160226_03-1.jpg
670 ms
20160226_03-2.jpg
693 ms
20160226_03-3.jpg
750 ms
20160226_03-4.jpg
790 ms
20160226_04.gif
823 ms
20160226_04-1.jpg
879 ms
20160226_04-2.jpg
871 ms
20160226_04-3.jpg
899 ms
20160226_04-4.jpg
961 ms
20160226_05.gif
1004 ms
20160226_05-1.jpg
1020 ms
20160226_05-2.jpg
1073 ms
20160226_05-3.jpg
1097 ms
20160226_05-4.jpg
1103 ms
20160226_06.gif
1170 ms
20160226_06-1.jpg
1217 ms
20160226_06-2.jpg
1218 ms
20160226_06-3.jpg
1254 ms
20160226_06-4.jpg
1269 ms
3 ms
lativ.com.tw accessibility score
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
Image elements do not have [alt] attributes
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.
lativ.com.tw 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
Missing source maps for large first-party JavaScript
lativ.com.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lativ.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Lativ.com.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.
lativ.com.tw
Open Graph description is not detected on the main page of Lativ. 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: