Tools & Wizards About Us
slaylashes.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

slaylashes.com

Slashes Handcrafted lashes 3D hair cruelty free

Page Load Speed

2.8 sec in total

First Response

129 ms

Resources Loaded

1.9 sec

Page Rendered

834 ms

slaylashes.com screenshot

About Website

Welcome to slaylashes.com homepage info - get ready to check Slay Lashes best content right away, or after learning these important things about slaylashes.com

Slaylashes Handcrafted lashes using 100% premium 3D hair and cruelty-free 2018

Visit slaylashes.com

Key Findings

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

Performance Metrics

slaylashes.com performance score

0

Network Requests Diagram

slaylashes.com

129 ms

slaylashes.com

131 ms

www.slaylashes.com

519 ms

css

63 ms

theme-15afdf70-70ad-013a-1437-62b8e852788b.css

75 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 11% of them (5 requests) were addressed to the original Slaylashes.com, 24% (11 requests) were made to Cdn11.bigcommerce.com and 16% (7 requests) were made to Sdk.beeketing.com. The less responsive or slowest element that took the longest time to load (808 ms) relates to the external source Cdn11.bigcommerce.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.6 MB (16%)

Content Size

28.3 MB

After Optimization

23.8 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Slaylashes.com main page is 28.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 27.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 150.5 kB

  • Original 178.7 kB
  • After minification 155.2 kB
  • After compression 28.2 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 23.5 kB, which is 13% 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 150.5 kB or 84% of the original size.

Image Optimization

-16%

Potential reduce by 4.4 MB

  • Original 27.7 MB
  • After minification 23.3 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. Obviously, Slay Lashes needs image optimization as it can save up to 4.4 MB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 589 B

  • Original 463.8 kB
  • After minification 463.8 kB
  • After compression 463.2 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.

Requests Breakdown

Number of requests can be reduced by 21 (57%)

Requests Now

37

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Slay 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 22 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

slaylashes.com

slaylashes.com

129 ms

slaylashes.com

slaylashes.com

131 ms

www.slaylashes.com

www.slaylashes.com

519 ms

css

css

63 ms

theme-15afdf70-70ad-013a-1437-62b8e852788b.css

theme-15afdf70-70ad-013a-1437-62b8e852788b.css

75 ms

loader.js

loader.js

73 ms

platform.js

platform.js

214 ms

theme-bundle.main.js

theme-bundle.main.js

144 ms

csrf-protection-header-95f3d9ac8c049e3ed132c83a168cf1d6a8ed0237.js

csrf-protection-header-95f3d9ac8c049e3ed132c83a168cf1d6a8ed0237.js

143 ms

visitor_stencil.js

visitor_stencil.js

66 ms

getgeotrustsslseal

getgeotrustsslseal

8 ms

fbevents.js

fbevents.js

214 ms

analytics.js

analytics.js

214 ms

slaylashes.png

slaylashes.png

393 ms

stunner__40344.png

stunner__40344.png

808 ms

loading.svg

loading.svg

170 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

418 ms

beeketing.js

beeketing.js

454 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

291 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

290 ms

bigcommerce.js

bigcommerce.js

653 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

238 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

304 ms

index.php

index.php

340 ms

cookie-notification

cookie-notification

344 ms

theme-bundle.chunk.18.js

theme-bundle.chunk.18.js

316 ms

495204078588976

495204078588976

280 ms

collect

collect

254 ms

icon-sprite.svg

icon-sprite.svg

141 ms

muse__45629.png

muse__45629.png

531 ms

GOALS.png

GOALS.png

445 ms

postmessageRelay

postmessageRelay

223 ms

js

js

215 ms

nobot

nobot

107 ms

1755322644719270

1755322644719270

85 ms

beeketing.0.41fa4b0af8d6bfceac2f.js

beeketing.0.41fa4b0af8d6bfceac2f.js

48 ms

beeketing.1.19d05760fa520b2970db.js

beeketing.1.19d05760fa520b2970db.js

60 ms

beeketing.3.f475d5839949f0aad803.js

beeketing.3.f475d5839949f0aad803.js

62 ms

beeketing.131.849372d45e7048adcda7.js

beeketing.131.849372d45e7048adcda7.js

66 ms

developers.google.com

developers.google.com

343 ms

MWJjYjY2MDhjZmJlN2JjYzVlMDNmNGM3NDVhNWUzYzE=.json

MWJjYjY2MDhjZmJlN2JjYzVlMDNmNGM3NDVhNWUzYzE=.json

299 ms

production.json

production.json

237 ms

3588414169-postmessagerelay.js

3588414169-postmessagerelay.js

200 ms

rpc:shindig_random.js

rpc:shindig_random.js

83 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

10 ms

SEO Factors

slaylashes.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Slaylashes.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Slaylashes.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

slaylashes.com

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