Tools & Wizards About Us
miyalashes.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

miyalashes.com

Miva Lashes

Page Load Speed

4 sec in total

First Response

71 ms

Resources Loaded

3.2 sec

Page Rendered

785 ms

miyalashes.com screenshot

About Website

Visit miyalashes.com now to see the best up-to-date Miya Lashes content and also check out these interesting facts you probably never knew about miyalashes.com

Miva Lashes

Visit miyalashes.com

Key Findings

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

Performance Metrics

miyalashes.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value8,380 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

miyalashes.com

71 ms

miyalashes.com

14 ms

www.miyalashes.com

93 ms

www.miyalashes.com

110 ms

bootstrap.min.css

52 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 24% of them (16 requests) were addressed to the original Miyalashes.com, 26% (18 requests) were made to Weboss.miyalashes.com and 15% (10 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Cdn.bootcss.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 416.7 kB (6%)

Content Size

7.4 MB

After Optimization

7.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Miyalashes.com main page is 7.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. Only a small number of websites need less resources to load. Images take 7.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 34.6 kB

  • Original 44.0 kB
  • After minification 38.0 kB
  • After compression 9.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 6.0 kB, which is 14% 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 34.6 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 372.3 kB

  • Original 7.0 MB
  • After minification 6.6 MB

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. Miya Lashes images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 8.8 kB

  • Original 256.2 kB
  • After minification 256.2 kB
  • After compression 247.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 986 B

  • Original 106.7 kB
  • After minification 106.7 kB
  • After compression 105.8 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. Miyalashes.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (48%)

Requests Now

52

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Miya Lashes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

miyalashes.com

miyalashes.com

71 ms

miyalashes.com

miyalashes.com

14 ms

www.miyalashes.com

www.miyalashes.com

93 ms

www.miyalashes.com

www.miyalashes.com

110 ms

bootstrap.min.css

bootstrap.min.css

52 ms

bootstrap-theme.min.css

bootstrap-theme.min.css

70 ms

font-awesome.min.css

font-awesome.min.css

65 ms

swiper.min.css

swiper.min.css

68 ms

uikit.min.css+slick.css+base.css+index.css+iconfont.css.pagespeed.cc.A7y2AiZIrd.css

uikit.min.css+slick.css+base.css+index.css+iconfont.css.pagespeed.cc.A7y2AiZIrd.css

11 ms

font_1383987_hfvsiu5brx6.css

font_1383987_hfvsiu5brx6.css

89 ms

swiper.min.js

swiper.min.js

61 ms

jquery.min.js

jquery.min.js

61 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

1213 ms

layer.js.pagespeed.jm.BTh-aGG_i8.js

layer.js.pagespeed.jm.BTh-aGG_i8.js

34 ms

cms.js

cms.js

43 ms

js

js

86 ms

bootstrap.min.js

bootstrap.min.js

69 ms

wow.min.js

wow.min.js

69 ms

uikit.min.js.pagespeed.ce.Db6chghuKA.js

uikit.min.js.pagespeed.ce.Db6chghuKA.js

56 ms

cart.js+base.js+zturn.js.pagespeed.jc.dxiKwTwYI9.js

cart.js+base.js+zturn.js.pagespeed.jc.dxiKwTwYI9.js

39 ms

layer.css

layer.css

18 ms

fbevents.js

fbevents.js

165 ms

46cb7b8a46.png

46cb7b8a46.png

449 ms

xqydefault.jpg.pagespeed.ic.IE3cy6JIwc.jpg

xqydefault.jpg.pagespeed.ic.IE3cy6JIwc.jpg

60 ms

d21e04c082.jpg

d21e04c082.jpg

517 ms

168e13b030.jpg

168e13b030.jpg

581 ms

15a545b340.jpg

15a545b340.jpg

520 ms

92de45ea75.jpg

92de45ea75.jpg

518 ms

42bd251eb9.jpg

42bd251eb9.jpg

516 ms

bb90f0b936.jpg

bb90f0b936.jpg

515 ms

60e4c37e71.jpg

60e4c37e71.jpg

521 ms

5b23371c50.jpg

5b23371c50.jpg

584 ms

e05f3c4047.jpg

e05f3c4047.jpg

570 ms

8c455873f9.jpg

8c455873f9.jpg

519 ms

65f08a7e58.jpg

65f08a7e58.jpg

565 ms

2d62d59eb7.jpg

2d62d59eb7.jpg

669 ms

2dcef5f789.jpg

2dcef5f789.jpg

567 ms

79e56e5745.jpg

79e56e5745.jpg

575 ms

28006628bf.jpg

28006628bf.jpg

579 ms

wMkmPDcE47Y

wMkmPDcE47Y

391 ms

uaUqxakRxiI

uaUqxakRxiI

388 ms

jiantou.png

jiantou.png

102 ms

cf82d2d03a.jpg

cf82d2d03a.jpg

525 ms

500102b35a.jpg

500102b35a.jpg

543 ms

js

js

151 ms

analytics.js

analytics.js

430 ms

font_1383987_hfvsiu5brx6.woff

font_1383987_hfvsiu5brx6.woff

1066 ms

iconfont.woff

iconfont.woff

341 ms

iconfont.woff

iconfont.woff

221 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

285 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

284 ms

xfbml.customerchat.js

xfbml.customerchat.js

251 ms

wMkmPDcE47Y

wMkmPDcE47Y

133 ms

uaUqxakRxiI

uaUqxakRxiI

228 ms

collect

collect

109 ms

www-player.css

www-player.css

30 ms

www-embed-player.js

www-embed-player.js

55 ms

base.js

base.js

102 ms

iconfont.ttf

iconfont.ttf

493 ms

ad_status.js

ad_status.js

368 ms

QIgJXlTW_ocH5BKR4VvT459F7KnrK51w4wqraUAmDYI.js

QIgJXlTW_ocH5BKR4VvT459F7KnrK51w4wqraUAmDYI.js

268 ms

embed.js

embed.js

159 ms

id

id

40 ms

iconfont.svg

iconfont.svg

229 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

54 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

56 ms

Create

Create

239 ms

Create

Create

347 ms

Accessibility Review

miyalashes.com accessibility score

54

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

miyalashes.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

miyalashes.com SEO score

85

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Miyalashes.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 Chinese language. Our system also found out that Miyalashes.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.

Social Sharing Optimization

miyalashes.com

Open Graph description is not detected on the main page of Miya Lashes. 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: