Tools & Wizards About Us
cuple.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

cuple.com

Cuplé | Online clothing and shoe store

Page Load Speed

7.2 sec in total

First Response

690 ms

Resources Loaded

6.2 sec

Page Rendered

326 ms

cuple.com screenshot

About Website

Click here to check amazing Cuple content for Spain. Otherwise, check out these important facts you probably never knew about cuple.com

Surprise yourself and discover our large catalog of clothing, footwear, bags and accessories for women. All products designed and manufactured in Spain.

Visit cuple.com

Key Findings

We analyzed Cuple.com page load time and found that the first response time was 690 ms and then it took 6.5 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

cuple.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

36/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

cuple.com

690 ms

2911 ms

bootstrap.css

232 ms

v_899_58e8ed75bc0ad12b04b7afff9433da68_all.css

315 ms

responsive.css

217 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 77% of them (46 requests) were addressed to the original Cuple.com, 5% (3 requests) were made to Google-analytics.com and 5% (3 requests) were made to Connect.nosto.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Cuple.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 651.6 kB (37%)

Content Size

1.8 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 48.3 kB

  • Original 60.7 kB
  • After minification 52.8 kB
  • After compression 12.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 7.9 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 48.3 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 10.5 kB

  • Original 917.2 kB
  • After minification 906.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. Cuple images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 424.5 kB

  • Original 590.2 kB
  • After minification 521.8 kB
  • After compression 165.6 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 424.5 kB or 72% of the original size.

CSS Optimization

-89%

Potential reduce by 168.3 kB

  • Original 188.1 kB
  • After minification 154.7 kB
  • After compression 19.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. Cuple.com needs all CSS files to be minified and compressed as it can save up to 168.3 kB or 89% of the original size.

Requests Breakdown

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

Requests Now

54

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cuple.com

cuple.com

690 ms

2911 ms

bootstrap.css

bootstrap.css

232 ms

v_899_58e8ed75bc0ad12b04b7afff9433da68_all.css

v_899_58e8ed75bc0ad12b04b7afff9433da68_all.css

315 ms

responsive.css

responsive.css

217 ms

cuple-estilo.css

cuple-estilo.css

223 ms

3.jpg

3.jpg

218 ms

1.jpg

1.jpg

244 ms

cuple-1407138574.jpg

cuple-1407138574.jpg

374 ms

menu.jpg

menu.jpg

375 ms

SPRING_SUMMER16_2.jpg

SPRING_SUMMER16_2.jpg

984 ms

Capa-35.jpg

Capa-35.jpg

453 ms

Capa-27.jpg

Capa-27.jpg

600 ms

Capa-29.jpg

Capa-29.jpg

514 ms

Capa-31.jpg

Capa-31.jpg

628 ms

CUPLE_SORTEO_BOLSO_WEBeng.png

CUPLE_SORTEO_BOLSO_WEBeng.png

1187 ms

FINAL_SALE.jpg

FINAL_SALE.jpg

794 ms

croptop-rayas.jpg

croptop-rayas.jpg

617 ms

blucher-picados-negro.jpg

blucher-picados-negro.jpg

721 ms

cartera-negra-solapa.jpg

cartera-negra-solapa.jpg

720 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

844 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

821 ms

jquery.easing.js

jquery.easing.js

840 ms

tools.js

tools.js

906 ms

global.js

global.js

924 ms

10-bootstrap.min.js

10-bootstrap.min.js

962 ms

15-jquery.total-storage.min.js

15-jquery.total-storage.min.js

947 ms

15-jquery.uniform-modified.js

15-jquery.uniform-modified.js

1020 ms

ajax-cart.js

ajax-cart.js

1027 ms

jquery.scrollTo.js

jquery.scrollTo.js

1051 ms

jquery.serialScroll.js

jquery.serialScroll.js

1082 ms

jquery.bxslider.js

jquery.bxslider.js

1091 ms

blocknewsletter.js

blocknewsletter.js

1133 ms

jquery.autocomplete.js

jquery.autocomplete.js

1130 ms

blocksearch.js

blocksearch.js

1155 ms

ajax-wishlist.js

ajax-wishlist.js

1203 ms

GoogleAnalyticActionLib.js

GoogleAnalyticActionLib.js

1200 ms

conversion.js

conversion.js

16 ms

treeManagement.js

treeManagement.js

1230 ms

nostotagging-auto-slots.js

nostotagging-auto-slots.js

1038 ms

leocustomajax.js

leocustomajax.js

1048 ms

countdown.js

countdown.js

1078 ms

cart.png

cart.png

1039 ms

footer-foot.jpg

footer-foot.jpg

1044 ms

gotham-book.woff

gotham-book.woff

1044 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1010 ms

112 ms

analytics.js

analytics.js

109 ms

prestashop-917fbd6f

prestashop-917fbd6f

81 ms

fbevents.js

fbevents.js

76 ms

hotjar-104822.js

hotjar-104822.js

139 ms

1userUp.png

1userUp.png

115 ms

97 ms

ev1

ev1

24 ms

42 ms

ec.js

ec.js

15 ms

modules-043c1e6abe660c48857202e419ff9d8a.js

modules-043c1e6abe660c48857202e419ff9d8a.js

18 ms

collect

collect

28 ms

push

push

45 ms

collect

collect

49 ms

Accessibility Review

cuple.com accessibility score

71

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-*] attributes do not match their roles

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

Links do not have a discernible name

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

cuple.com 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

Page has valid source maps

SEO Factors

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

High

Page is blocked from indexing

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cuple.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 Cuple.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

cuple.com

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