Tools & Wizards About Us
blog.ipsy.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

blog.ipsy.com

Personalized Monthly Makeup & Beauty Sample Subscription | IPSY

Page Load Speed

782 ms in total

First Response

12 ms

Resources Loaded

554 ms

Page Rendered

216 ms

blog.ipsy.com screenshot

About Website

Visit blog.ipsy.com now to see the best up-to-date Blog IPSY content for United States and also check out these interesting facts you probably never knew about blog.ipsy.com

Personalized makeup and beauty products, exclusive offers, and how-to video tutorials from our IPSY Stylists. Each month subscribers receive a gorgeous Glam Bag with 5+ products starting at $13/month....

Visit blog.ipsy.com

Key Findings

We analyzed Blog.ipsy.com page load time and found that the first response time was 12 ms and then it took 770 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

blog.ipsy.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value6,170 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value27.1 s

0/100

10%

Network Requests Diagram

blog.ipsy.com

12 ms

blog.ipsy.com

260 ms

b0a4a66d89cd7445.css

85 ms

polyfills-c67a75d1b6f99dc8.js

99 ms

at.js

79 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Blog.ipsy.com, 83% (35 requests) were made to Nextjs-assets.prod.ipsy.com and 10% (4 requests) were made to Cdn-cf.ipsy.com. The less responsive or slowest element that took the longest time to load (260 ms) belongs to the original domain Blog.ipsy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.0 kB (14%)

Content Size

1.1 MB

After Optimization

971.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.ipsy.com main page is 1.1 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. 70% of websites need less resources to load. Javascripts take 655.4 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 159.1 kB

  • Original 186.9 kB
  • After minification 186.9 kB
  • After compression 27.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. 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 159.1 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 3.7 kB

  • Original 281.2 kB
  • After minification 277.5 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. Blog IPSY images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.0 kB

  • Original 655.4 kB
  • After minification 655.4 kB
  • After compression 654.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 116 B

  • Original 11.8 kB
  • After minification 11.8 kB
  • After compression 11.7 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. Blog.ipsy.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (86%)

Requests Now

37

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.ipsy.com

blog.ipsy.com

12 ms

blog.ipsy.com

blog.ipsy.com

260 ms

b0a4a66d89cd7445.css

b0a4a66d89cd7445.css

85 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

99 ms

at.js

at.js

79 ms

webpack-d077232f94fe5927.js

webpack-d077232f94fe5927.js

98 ms

framework-e0e3abb0c4b76822.js

framework-e0e3abb0c4b76822.js

130 ms

main-f9fc9abed40b4496.js

main-f9fc9abed40b4496.js

126 ms

_app-357ff0beb2ade399.js

_app-357ff0beb2ade399.js

191 ms

3291-0395021cc271138e.js

3291-0395021cc271138e.js

188 ms

5847-1da2b0014a2c138e.js

5847-1da2b0014a2c138e.js

180 ms

9181-647bd4d8a9e17f20.js

9181-647bd4d8a9e17f20.js

180 ms

8365-7d7785fbaf29fcc9.js

8365-7d7785fbaf29fcc9.js

188 ms

5675-4383a7c97e93a937.js

5675-4383a7c97e93a937.js

188 ms

8764-86ee4dec8701906d.js

8764-86ee4dec8701906d.js

202 ms

5713-95b64b8e0a6b13e9.js

5713-95b64b8e0a6b13e9.js

189 ms

653-4092ffa0a202f4d8.js

653-4092ffa0a202f4d8.js

199 ms

2922-6301aa797552f768.js

2922-6301aa797552f768.js

199 ms

7536-df1171c5a792f5e7.js

7536-df1171c5a792f5e7.js

209 ms

2200-75c8a6127fafdc46.js

2200-75c8a6127fafdc46.js

211 ms

3890-61358b271de2e5ff.js

3890-61358b271de2e5ff.js

210 ms

7915-443635690cd6a13e.js

7915-443635690cd6a13e.js

214 ms

5592-a41cad933399cedf.js

5592-a41cad933399cedf.js

220 ms

3634-71604f8e70d95aa6.js

3634-71604f8e70d95aa6.js

223 ms

3632-eccdcb37ef5e1b8d.js

3632-eccdcb37ef5e1b8d.js

222 ms

24-6a32d51c72ddcd1b.js

24-6a32d51c72ddcd1b.js

221 ms

1153-9340f50dd7212399.js

1153-9340f50dd7212399.js

221 ms

6015-278ffde8b1525758.js

6015-278ffde8b1525758.js

220 ms

3670-467931ec3e1a617c.js

3670-467931ec3e1a617c.js

228 ms

3937-433bad0a47d8b0fb.js

3937-433bad0a47d8b0fb.js

228 ms

3468-ecef3092ea67257e.js

3468-ecef3092ea67257e.js

232 ms

2273-ece5fb65e8399007.js

2273-ece5fb65e8399007.js

229 ms

index-64bc8d75e99a003f.js

index-64bc8d75e99a003f.js

229 ms

_buildManifest.js

_buildManifest.js

230 ms

_ssgManifest.js

_ssgManifest.js

235 ms

161 ms

script.js

script.js

199 ms

fileAsset

fileAsset

106 ms

fileAsset

fileAsset

121 ms

NeueEinstellung-Bold.e6c39209.woff

NeueEinstellung-Bold.e6c39209.woff

9 ms

NeueEinstellung-Regular.0673feec.woff

NeueEinstellung-Regular.0673feec.woff

5 ms

ipsyIcons.25e7d254.woff

ipsyIcons.25e7d254.woff

6 ms

Accessibility Review

blog.ipsy.com accessibility score

98

Accessibility Issues

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

blog.ipsy.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

blog.ipsy.com SEO score

100

Search Engine Optimization Advices

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 Blog.ipsy.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 Blog.ipsy.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

blog.ipsy.com

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