Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

prettybeautiful.net

Pretty Beautiful – Malaysia Beauty Blog – Skincare, Nail Arts, Makeup and Health

Page Load Speed

2.7 sec in total

First Response

594 ms

Resources Loaded

1.8 sec

Page Rendered

289 ms

About Website

Welcome to prettybeautiful.net homepage info - get ready to check Pretty Beautiful best content for Malaysia right away, or after learning these important things about prettybeautiful.net

A beauty blog and blogger based in Malaysia, with reviews from skincare, makeup, general beauty & health to nail art tutorials

Visit prettybeautiful.net

Key Findings

We analyzed Prettybeautiful.net page load time and found that the first response time was 594 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

prettybeautiful.net performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

prettybeautiful.net

594 ms

layout.css

40 ms

custom.css

77 ms

public_widget.css

100 ms

styles.css

101 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 32% of them (33 requests) were addressed to the original Prettybeautiful.net, 8% (8 requests) were made to Googleads.g.doubleclick.net and 6% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (594 ms) belongs to the original domain Prettybeautiful.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 425.7 kB (36%)

Content Size

1.2 MB

After Optimization

768.9 kB

In fact, the total size of Prettybeautiful.net main page is 1.2 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. 60% of websites need less resources to load. Images take 563.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 57.4 kB

  • Original 72.2 kB
  • After minification 68.4 kB
  • After compression 14.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 57.4 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 18.8 kB

  • Original 563.7 kB
  • After minification 544.9 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. Pretty Beautiful images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 236.1 kB

  • Original 420.8 kB
  • After minification 406.2 kB
  • After compression 184.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 236.1 kB or 56% of the original size.

CSS Optimization

-82%

Potential reduce by 113.4 kB

  • Original 137.9 kB
  • After minification 114.8 kB
  • After compression 24.5 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. Prettybeautiful.net needs all CSS files to be minified and compressed as it can save up to 113.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (60%)

Requests Now

97

After Optimization

39

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

Accessibility Review

prettybeautiful.net accessibility score

94

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.

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

prettybeautiful.net best practices score

67

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

SEO Factors

prettybeautiful.net SEO score

79

Search Engine Optimization Advices

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 Prettybeautiful.net 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 Prettybeautiful.net 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

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