Tools & Wizards About Us
2018.frilly.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

2018.frilly.com

Custom Made, Made-To-Order Clothing for Women | frilly

Page Load Speed

6.7 sec in total

First Response

214 ms

Resources Loaded

4.7 sec

Page Rendered

1.7 sec

2018.frilly.com screenshot

About Website

Click here to check amazing 2018 Frilly content for United States. Otherwise, check out these important facts you probably never knew about 2018.frilly.com

frilly is taking customization to a new level. A contemporary clothing brand meant to empower you and encourage you to embrace your own style. Free US shipping and returns. Discover the latest dresses...

Visit 2018.frilly.com

Key Findings

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

Performance Metrics

2018.frilly.com performance score

0

Network Requests Diagram

2018.frilly.com

214 ms

2018.frilly.com

466 ms

plugin_all.css

63 ms

main.css

192 ms

api_dynamic.js

41 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 53% of them (46 requests) were addressed to the original 2018.frilly.com, 10% (9 requests) were made to D1vl5672ogdtak.cloudfront.net and 5% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source D1vl5672ogdtak.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (7%)

Content Size

27.2 MB

After Optimization

25.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 2018.frilly.com main page is 27.2 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. 85% 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.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 60.6 kB

  • Original 73.4 kB
  • After minification 48.2 kB
  • After compression 12.8 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 25.2 kB, which is 34% 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 60.6 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 1.8 MB

  • Original 27.0 MB
  • After minification 25.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. 2018 Frilly images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 17.3 kB

  • Original 71.3 kB
  • After minification 64.1 kB
  • After compression 54.0 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 17.3 kB or 24% of the original size.

CSS Optimization

-23%

Potential reduce by 13.7 kB

  • Original 59.5 kB
  • After minification 59.5 kB
  • After compression 45.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. 2018.frilly.com needs all CSS files to be minified and compressed as it can save up to 13.7 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (47%)

Requests Now

76

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

2018.frilly.com

2018.frilly.com

214 ms

2018.frilly.com

2018.frilly.com

466 ms

plugin_all.css

plugin_all.css

63 ms

main.css

main.css

192 ms

api_dynamic.js

api_dynamic.js

41 ms

api_static.js

api_static.js

74 ms

require.js

require.js

301 ms

require.config.js

require.config.js

300 ms

index.js

index.js

305 ms

gtm.js

gtm.js

336 ms

4432ac0f4442e6a9c60c7c233.js

4432ac0f4442e6a9c60c7c233.js

764 ms

152904898659175.jpg

152904898659175.jpg

645 ms

1548237810485364.jpg

1548237810485364.jpg

1512 ms

close.svg

close.svg

218 ms

logo_black.svg

logo_black.svg

235 ms

search_b.svg

search_b.svg

232 ms

bag_b.svg

bag_b.svg

231 ms

werecustom.gif

werecustom.gif

354 ms

dress.gif

dress.gif

1134 ms

facebook.svg

facebook.svg

537 ms

pinterest.svg

pinterest.svg

571 ms

twitter.svg

twitter.svg

572 ms

tumblr.svg

tumblr.svg

571 ms

inc_logo.png

inc_logo.png

658 ms

forbes_logo.png

forbes_logo.png

656 ms

glossy_logo.png

glossy_logo.png

657 ms

who_logo.png

who_logo.png

655 ms

fast_logo.png

fast_logo.png

659 ms

1545157641944334.jpg

1545157641944334.jpg

3346 ms

1543454590836993.jpg

1543454590836993.jpg

3276 ms

1541473163626124.jpg

1541473163626124.jpg

3364 ms

1553846506501935.png

1553846506501935.png

3332 ms

1547453145489897.png

1547453145489897.png

2902 ms

1547458216949821.jpg

1547458216949821.jpg

2679 ms

1547453179827148.png

1547453179827148.png

2916 ms

1547453196683104.png

1547453196683104.png

3197 ms

header.js

header.js

618 ms

bag.js

bag.js

660 ms

index.js

index.js

626 ms

Mostardesign%20-%20SofiaPro-Bold.woff

Mostardesign%20-%20SofiaPro-Bold.woff

921 ms

Mostardesign%20-%20SofiaProMedium.woff

Mostardesign%20-%20SofiaProMedium.woff

922 ms

Mostardesign%20-%20SofiaProRegular.woff

Mostardesign%20-%20SofiaProRegular.woff

1232 ms

Mostardesign%20-%20SofiaProSemiBold.woff

Mostardesign%20-%20SofiaProSemiBold.woff

1230 ms

asset_composer.js

asset_composer.js

515 ms

optimize.js

optimize.js

631 ms

bat.js

bat.js

625 ms

fbevents.js

fbevents.js

425 ms

core.js

core.js

609 ms

ytc.js

ytc.js

677 ms

spx

spx

1826 ms

fs.js

fs.js

795 ms

spx

spx

1844 ms

frilly.min.js

frilly.min.js

944 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

614 ms

underscore-min.js

underscore-min.js

612 ms

swiper.min.js

swiper.min.js

612 ms

adaptive.js

adaptive.js

612 ms

axios.min.js

axios.min.js

1418 ms

js.cookie.min.js

js.cookie.min.js

1418 ms

wishList.js

wishList.js

1417 ms

errorTips.js

errorTips.js

1414 ms

lazy.image.js

lazy.image.js

1412 ms

434971030188428

434971030188428

445 ms

frillyhelp.zendesk.com

frillyhelp.zendesk.com

1553 ms

main.3a217bc7.js

main.3a217bc7.js

261 ms

analytics.js

analytics.js

238 ms

10032084.json

10032084.json

944 ms

5666669.js

5666669.js

920 ms

es6-promise.js

es6-promise.js

663 ms

jquery.slimscroll.min.js

jquery.slimscroll.min.js

663 ms

layer.min.js

layer.min.js

663 ms

formcheck.js

formcheck.js

662 ms

selectordie.min.js

selectordie.min.js

662 ms

679 ms

collect

collect

144 ms

collect

collect

554 ms

5666669

5666669

552 ms

request_api

request_api

507 ms

request_api

request_api

493 ms

request_api

request_api

454 ms

web-widget-framework-8bd776911afeefa93f7a.js

web-widget-framework-8bd776911afeefa93f7a.js

64 ms

ga-audiences

ga-audiences

330 ms

clarity.js

clarity.js

166 ms

create.html

create.html

213 ms

collect

collect

26 ms

c.gif

c.gif

8 ms

SEO Factors

2018.frilly.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2018.frilly.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 2018.frilly.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

2018.frilly.com

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