Tools & Wizards About Us
lativ.com.tw screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

lativ.com.tw

lativ 米格國際

Page Load Speed

5.2 sec in total

First Response

459 ms

Resources Loaded

4.2 sec

Page Rendered

586 ms

lativ.com.tw screenshot

About Website

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.tw

Key Findings

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

Performance Metrics

lativ.com.tw performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value1,100 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value1.574

0/100

15%

TTI (Time to Interactive)

Value23.8 s

1/100

10%

Network Requests Diagram

lativ.com.tw

459 ms

www.lativ.com.tw

1095 ms

bundle.css

1094 ms

LativJS.js

1273 ms

StaticPage.css

868 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 9% of them (4 requests) were addressed to the original Lativ.com.tw, 27% (12 requests) were made to S1.lativ.com.tw and 22% (10 requests) were made to S.lativ.com.tw. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source S3.lativ.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 91.3 kB (8%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lativ.com.tw main page is 1.1 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. 25% of websites need less resources to load. Images take 882.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 58.9 kB

  • Original 76.4 kB
  • After minification 73.5 kB
  • After compression 17.5 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 58.9 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 9.7 kB

  • Original 882.4 kB
  • After minification 872.7 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.

JavaScript Optimization

-13%

Potential reduce by 16.4 kB

  • Original 128.8 kB
  • After minification 128.8 kB
  • After compression 112.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 16.4 kB or 13% of the original size.

CSS Optimization

-17%

Potential reduce by 6.3 kB

  • Original 35.9 kB
  • After minification 35.9 kB
  • After compression 29.7 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 6.3 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (35%)

Requests Now

43

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 43 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.

Network Requests Diagram

lativ.com.tw

lativ.com.tw

459 ms

www.lativ.com.tw

www.lativ.com.tw

1095 ms

bundle.css

bundle.css

1094 ms

LativJS.js

LativJS.js

1273 ms

StaticPage.css

StaticPage.css

868 ms

js

js

65 ms

fbevents.js

fbevents.js

220 ms

notification_logo.png

notification_logo.png

217 ms

logo-2011.png

logo-2011.png

215 ms

64727_3P498_1180X630_240502_TW0503.jpg

64727_3P498_1180X630_240502_TW0503.jpg

1469 ms

64464_2P85DUP_1180X630_240502_TW.jpg

64464_2P85DUP_1180X630_240502_TW.jpg

1477 ms

60355_WORK_1180X630_240502_TW.jpg

60355_WORK_1180X630_240502_TW.jpg

814 ms

64503_1180X630_240425_TW_0.jpg

64503_1180X630_240425_TW_0.jpg

1399 ms

icon_close.png

icon_close.png

619 ms

65320_64257_65339_DENIM_1180X630_240219_TW.jpg

65320_64257_65339_DENIM_1180X630_240219_TW.jpg

996 ms

grey.gif

grey.gif

602 ms

icon_cs.png

icon_cs.png

617 ms

64570_SHIRTS_1180X630_240327_TW.jpg

64570_SHIRTS_1180X630_240327_TW.jpg

1479 ms

grey.gif

grey.gif

881 ms

blank.gif

blank.gif

406 ms

PC01_TW.gif

PC01_TW.gif

614 ms

PCLINE_TW.gif

PCLINE_TW.gif

614 ms

PC02_TW.gif

PC02_TW.gif

614 ms

PC03_TW.gif

PC03_TW.gif

616 ms

PC04_TW.gif

PC04_TW.gif

617 ms

PC05_TW.gif

PC05_TW.gif

619 ms

PC06_TW.gif

PC06_TW.gif

799 ms

64508_home_1180X630_240502_TW.jpg

64508_home_1180X630_240502_TW.jpg

1486 ms

btn_search.gif

btn_search.gif

592 ms

nav-menus-ilook.gif

nav-menus-ilook.gif

610 ms

ShoppingCart.gif

ShoppingCart.gif

590 ms

ytc.js

ytc.js

94 ms

firebase-app-5.7.3.js

firebase-app-5.7.3.js

758 ms

webPush.js

webPush.js

829 ms

265 ms

bx_loader.gif

bx_loader.gif

735 ms

mainpic_arrow.png

mainpic_arrow.png

752 ms

js

js

51 ms

10060142.json

10060142.json

18 ms

567690756667739

567690756667739

183 ms

212 ms

FS_mothersady_1200_240427_TW_s.jpg

FS_mothersady_1200_240427_TW_s.jpg

628 ms

64082_1200_240502_TW_s.jpg

64082_1200_240502_TW_s.jpg

885 ms

mainpic_circule.png

mainpic_circule.png

392 ms

firebase-messaging-5.7.3.js

firebase-messaging-5.7.3.js

257 ms

Accessibility Review

lativ.com.tw accessibility score

78

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lativ.com.tw best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

lativ.com.tw SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    ZH

  • Encoding

    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.

Social Sharing Optimization

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: