Tools & Wizards About Us
mybeautycompare.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mybeautycompare.com

Page Load Speed

2.8 sec in total

First Response

241 ms

Resources Loaded

2.3 sec

Page Rendered

226 ms

mybeautycompare.com screenshot

About Website

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

My Beauty Matches™ where beauty gets personal. Shop your favourite brands from makeup to skin care from the biggest online shop floor & discover your Beauty Matches™

Visit mybeautycompare.com

Key Findings

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

mybeautycompare.com performance score

0

Network Requests Diagram

241 ms

gtm.js

234 ms

analytics.js

268 ms

mixpanel-2-latest.min.js

273 ms

styles.css

395 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mybeautycompare.com, 6% (2 requests) were made to Google-analytics.com and 6% (2 requests) were made to Cdn.mxpnl.com. The less responsive or slowest element that took the longest time to load (802 ms) relates to the external source Content.mybeautymatches.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 79.9 kB (28%)

Content Size

290.1 kB

After Optimization

210.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Mybeautycompare.com main page is 290.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 161.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 43.7 kB

  • Original 56.6 kB
  • After minification 56.0 kB
  • After compression 12.9 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 43.7 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 4.1 kB

  • Original 161.4 kB
  • After minification 157.3 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. Mybeautycompare images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 32.0 kB

  • Original 72.0 kB
  • After minification 72.0 kB
  • After compression 40.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 32.0 kB or 44% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (39%)

Requests Now

28

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

241 ms

gtm.js

gtm.js

234 ms

analytics.js

analytics.js

268 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

273 ms

styles.css

styles.css

395 ms

js

js

431 ms

compressed_libs_01_09_2016.js

compressed_libs_01_09_2016.js

540 ms

jquery.matchHeight.js

jquery.matchHeight.js

248 ms

app.min.js

app.min.js

430 ms

main.min.js

main.min.js

429 ms

loading.gif

loading.gif

331 ms

favicon.png

favicon.png

318 ms

stylist.png

stylist.png

491 ms

vogue.png

vogue.png

493 ms

bazaar.jpg

bazaar.jpg

491 ms

tracker.min.js

tracker.min.js

225 ms

bme.min.js

bme.min.js

301 ms

3_LARGE+b%26w.jpg

3_LARGE+b%26w.jpg

802 ms

collect

collect

185 ms

badge_light.png

badge_light.png

147 ms

vector-logo-new.svg

vector-logo-new.svg

221 ms

sprite.png

sprite.png

294 ms

collect

collect

74 ms

avenirnextltpro-demi.woff

avenirnextltpro-demi.woff

85 ms

modern_no._20-webfont.woff

modern_no._20-webfont.woff

211 ms

AvenirNextLTPro-MediumCn.woff

AvenirNextLTPro-MediumCn.woff

83 ms

avenir-next-bold.woff

avenir-next-bold.woff

210 ms

icomoon.woff

icomoon.woff

145 ms

font-awesome.min.css

font-awesome.min.css

180 ms

jquery-ui.min.css

jquery-ui.min.css

290 ms

gen_204

gen_204

198 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

207 ms

sdk.js

sdk.js

88 ms

get-currencies

get-currencies

75 ms

1447146242.woff

1447146242.woff

149 ms

sdk.js

sdk.js

7 ms

SEO Factors

mybeautycompare.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 Mybeautycompare.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 Mybeautycompare.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

mybeautycompare.com

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