Tools & Wizards About Us
beautypie.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

beautypie.com

BEAUTY PIE | Luxury Makeup & Skincare Products Direct | BEAUTY PIE

Page Load Speed

8.5 sec in total

First Response

2.4 sec

Resources Loaded

5.4 sec

Page Rendered

736 ms

beautypie.com screenshot

About Website

Welcome to beautypie.com homepage info - get ready to check BEAUTY PIE best content for United Kingdom right away, or after learning these important things about beautypie.com

An exclusive luxury buyers club. Join tens of thousands of members already enjoying more skincare, makeup, haircare, bodycare, fragrances and makeup brushes.

Visit beautypie.com

Key Findings

We analyzed Beautypie.com page load time and found that the first response time was 2.4 sec and then it took 6.2 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

beautypie.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value7,100 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value24.3 s

0/100

10%

Network Requests Diagram

www.beautypie.com

2372 ms

3258fd4cea72b1b6.css

20 ms

0ce5a600cbd2389c.css

19 ms

e2bcfcb8f633f489.css

24 ms

6e08678ab671d927.css

18 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 94% of them (76 requests) were addressed to the original Beautypie.com, 5% (4 requests) were made to Images.ctfassets.net and 1% (1 request) were made to Services.postcodeanywhere.co.uk. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Beautypie.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (49%)

Content Size

3.8 MB

After Optimization

1.9 MB

  • HTML
  • Images

In fact, the total size of Beautypie.com main page is 3.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. 65% of websites need less resources to load. HTML takes 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 1.8 MB

  • Original 2.2 MB
  • After minification 2.2 MB
  • After compression 316.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.8 MB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 84 B

  • Original 1.6 MB
  • After minification 1.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. BEAUTY PIE images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 24 (30%)

Requests Now

80

After Optimization

56

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.beautypie.com

www.beautypie.com

2372 ms

3258fd4cea72b1b6.css

3258fd4cea72b1b6.css

20 ms

0ce5a600cbd2389c.css

0ce5a600cbd2389c.css

19 ms

e2bcfcb8f633f489.css

e2bcfcb8f633f489.css

24 ms

6e08678ab671d927.css

6e08678ab671d927.css

18 ms

ae2df71a5a46a20d.css

ae2df71a5a46a20d.css

19 ms

ea86bb5e5a4a362f.css

ea86bb5e5a4a362f.css

26 ms

b1498dffbda0ab68.css

b1498dffbda0ab68.css

27 ms

eab2c69878a8fba3.css

eab2c69878a8fba3.css

27 ms

2a33bc3ee46530fb.css

2a33bc3ee46530fb.css

25 ms

5cc6c89c1ee60e09.css

5cc6c89c1ee60e09.css

23 ms

a01ecf028daaf11c.css

a01ecf028daaf11c.css

27 ms

fd9d1056-39bda791586cb287.js

fd9d1056-39bda791586cb287.js

31 ms

2117-1c9cb11985d71968.js

2117-1c9cb11985d71968.js

30 ms

main-app-fb757dbf2494d41f.js

main-app-fb757dbf2494d41f.js

28 ms

2089-bbfabe85e556ae87.js

2089-bbfabe85e556ae87.js

29 ms

layout-0626173e3dbfded9.js

layout-0626173e3dbfded9.js

29 ms

aaea2bcf-797c5169bd51afe7.js

aaea2bcf-797c5169bd51afe7.js

40 ms

5378-e6f64c0322e8aed0.js

5378-e6f64c0322e8aed0.js

50 ms

6384-b077d0a5d0cb6c28.js

6384-b077d0a5d0cb6c28.js

47 ms

4370-5e674955311f7f04.js

4370-5e674955311f7f04.js

36 ms

850-434ccd8f2164edbd.js

850-434ccd8f2164edbd.js

39 ms

page-0b2ef9a34d45f0e8.js

page-0b2ef9a34d45f0e8.js

48 ms

not-found-d9cd6425dfaa7244.js

not-found-d9cd6425dfaa7244.js

60 ms

address-3.91.css

address-3.91.css

65 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

58 ms

webpack-a6c7dd9cfa76708d.js

webpack-a6c7dd9cfa76708d.js

103 ms

middlemen-shirt-icon-strikethrough.svg

middlemen-shirt-icon-strikethrough.svg

30 ms

image

image

490 ms

image

image

193 ms

image

image

372 ms

image

image

308 ms

image

image

408 ms

image

image

703 ms

image

image

777 ms

image

image

721 ms

image

image

660 ms

image

image

811 ms

image

image

940 ms

image

image

848 ms

image

image

1190 ms

image

image

1126 ms

image

image

1063 ms

image

image

1078 ms

image

image

1258 ms

image

image

1125 ms

image

image

1192 ms

image

image

1318 ms

image

image

1261 ms

image

image

1304 ms

image

image

1555 ms

image

image

1472 ms

image

image

1434 ms

image

image

1690 ms

image

image

1603 ms

image

image

1470 ms

image

image

1628 ms

image

image

1972 ms

image

image

1897 ms

image

image

1940 ms

image

image

1996 ms

image

image

1915 ms

shop-counter-icon-strikethrough.svg

shop-counter-icon-strikethrough.svg

17 ms

markups-cash-icon-strikethrough.svg

markups-cash-icon-strikethrough.svg

20 ms

exclamation-icon-strikethrough.svg

exclamation-icon-strikethrough.svg

22 ms

image

image

1680 ms

image

image

1811 ms

image

image

2066 ms

image

image

1921 ms

image

image

1709 ms

image

image

1697 ms

image

image

1783 ms

image

image

1460 ms

image

image

1503 ms

image

image

1651 ms

image

image

1461 ms

image

image

1580 ms

image

image

1864 ms

image

image

2092 ms

image

image

1701 ms

image

image

2111 ms

Accessibility Review

beautypie.com accessibility score

83

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

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

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

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

beautypie.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

beautypie.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

beautypie.com

Open Graph data is detected on the main page of BEAUTY PIE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: