Tools & Wizards About Us
lipsy.co.uk screenshot

Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

lipsy.co.uk

Lipsy London | Women's Clothing & Accessories | Next Uk

Page Load Speed

48.2 sec in total

First Response

132 ms

Resources Loaded

28.3 sec

Page Rendered

19.7 sec

lipsy.co.uk screenshot

About Website

Click here to check amazing Lipsy content for Japan. Otherwise, check out these important facts you probably never knew about lipsy.co.uk

Women's Day-to-night dresses, Dream jumpsuits & Do-it-all tailoring. Lipsy's Women's Clothing gives style to casual wear to nightwear. Next day delivery & free returns available.

Visit lipsy.co.uk

Key Findings

We analyzed Lipsy.co.uk page load time and found that the first response time was 132 ms and then it took 48.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

lipsy.co.uk performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value34.2 s

0/100

25%

SI (Speed Index)

Value18.5 s

0/100

10%

TBT (Total Blocking Time)

Value5,300 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.775

5/100

15%

TTI (Time to Interactive)

Value35.2 s

0/100

10%

Network Requests Diagram

lipsy.co.uk

132 ms

www.lipsy.co.uk

1013 ms

entry.js

1491 ms

responsive

829 ms

Cms.min.css

1386 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 28% of them (20 requests) were addressed to the original Lipsy.co.uk, 15% (11 requests) were made to Cdn.lipsy.co.uk and 6% (4 requests) were made to Tags.rd.linksynergy.com. The less responsive or slowest element that took the longest time to load (8.9 sec) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (31%)

Content Size

4.3 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lipsy.co.uk main page is 4.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 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 103.8 kB

  • Original 119.9 kB
  • After minification 90.7 kB
  • After compression 16.1 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 29.2 kB, which is 24% 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 103.8 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 81.0 kB

  • Original 2.6 MB
  • After minification 2.5 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. Lipsy images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 802.5 kB

  • Original 1.1 MB
  • After minification 877.4 kB
  • After compression 326.8 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 802.5 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 324.6 kB

  • Original 387.6 kB
  • After minification 386.3 kB
  • After compression 63.0 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. Lipsy.co.uk needs all CSS files to be minified and compressed as it can save up to 324.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (65%)

Requests Now

62

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lipsy.co.uk

lipsy.co.uk

132 ms

www.lipsy.co.uk

www.lipsy.co.uk

1013 ms

entry.js

entry.js

1491 ms

responsive

responsive

829 ms

Cms.min.css

Cms.min.css

1386 ms

css

css

1152 ms

css

css

1387 ms

toolkit

toolkit

993 ms

css

css

1354 ms

analytics

analytics

1086 ms

WebResource.axd

WebResource.axd

2940 ms

WebResource.axd

WebResource.axd

2977 ms

modernizr

modernizr

1133 ms

jquery

jquery

2852 ms

lipsy.mobile

lipsy.mobile

2737 ms

picturefill

picturefill

2563 ms

lipsy.jquery

lipsy.jquery

2737 ms

toolkit

toolkit

2882 ms

custom.js

custom.js

1494 ms

analytics.js

analytics.js

7166 ms

1_CLICKCOLLECT.png

1_CLICKCOLLECT.png

5140 ms

3_FREEDEL.png

3_FREEDEL.png

6073 ms

2_RETURNS.png

2_RETURNS.png

6073 ms

170823_Homepage_v2_amy_logo.png

170823_Homepage_v2_amy_logo.png

6073 ms

transparent.png

transparent.png

6073 ms

close.png

close.png

5901 ms

05.gif

05.gif

5902 ms

gtm.js

gtm.js

8938 ms

170823_Homepage_v3_03.jpg

170823_Homepage_v3_03.jpg

5612 ms

lipsy_master_sprite.svg

lipsy_master_sprite.svg

4606 ms

lipsy_master_sprite.png

lipsy_master_sprite.png

4556 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

4380 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

4379 ms

linkid.js

linkid.js

182 ms

556471239-0

556471239-0

842 ms

collect

collect

404 ms

collect

collect

939 ms

conversion_async.js

conversion_async.js

2922 ms

lipsy.js

lipsy.js

2922 ms

mmbe2ca197

mmbe2ca197

3359 ms

111677.ct.js

111677.ct.js

3199 ms

iMAWebCookie.js

iMAWebCookie.js

3200 ms

Webstats

Webstats

1567 ms

ReloadBasket

ReloadBasket

2130 ms

ga-audiences

ga-audiences

3816 ms

fbevents.js

fbevents.js

3575 ms

bat.js

bat.js

3573 ms

collect

collect

983 ms

receiver.html

receiver.html

2799 ms

mentionme-tag-library-v2-6f6f719.js

mentionme-tag-library-v2-6f6f719.js

2226 ms

1521

1521

2111 ms

lqs.aspx

lqs.aspx

1881 ms

lqs.apsx

lqs.apsx

1883 ms

929869880417562

929869880417562

692 ms

832 ms

1480 ms

bundle.js

bundle.js

681 ms

1521

1521

360 ms

generic

generic

1119 ms

generic

generic

95 ms

legacy_receiver.html

legacy_receiver.html

193 ms

cs

cs

150 ms

cs

cs

198 ms

legacy_receiver_v1.js

legacy_receiver_v1.js

62 ms

config

config

2839 ms

img

img

547 ms

null

null

1968 ms

170823_Homepage_v2_06.jpg

170823_Homepage_v2_06.jpg

1966 ms

170823_Homepage_v3_08.jpg

170823_Homepage_v3_08.jpg

774 ms

170823_Homepage_v3_09.jpg

170823_Homepage_v3_09.jpg

775 ms

170823_Homepage_v2_11.jpg

170823_Homepage_v2_11.jpg

1009 ms

lipsy_aug17_002.jpg

lipsy_aug17_002.jpg

696 ms

Accessibility Review

lipsy.co.uk accessibility score

75

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.

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

lipsy.co.uk 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

lipsy.co.uk SEO score

91

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

lipsy.co.uk

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