Tools & Wizards About Us
beautyfires.com screenshot

Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

beautyfires.com

Beauty Fires

Page Load Speed

5.5 sec in total

First Response

965 ms

Resources Loaded

4.5 sec

Page Rendered

56 ms

beautyfires.com screenshot

About Website

Welcome to beautyfires.com homepage info - get ready to check Beauty Fires best content for South Africa right away, or after learning these important things about beautyfires.com

Visit beautyfires.com

Key Findings

We analyzed Beautyfires.com page load time and found that the first response time was 965 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

beautyfires.com performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.9 s

0/100

25%

SI (Speed Index)

Value19.3 s

0/100

10%

TBT (Total Blocking Time)

Value3,110 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value1.326

0/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

beautyfires.com

965 ms

beautyfires.com

1308 ms

mqy3kow.css

145 ms

jquery-3.6.3.min.js

29 ms

main.334d44d6.js

1939 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 20% of them (4 requests) were addressed to the original Beautyfires.com, 25% (5 requests) were made to Use.typekit.net and 10% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Beautyfires.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.5 kB (2%)

Content Size

566.5 kB

After Optimization

556.0 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 9.4 kB

  • Original 12.4 kB
  • After minification 12.3 kB
  • After compression 3.0 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 9.4 kB or 76% of the original size.

JavaScript Optimization

-0%

Potential reduce by 1.0 kB

  • Original 537.6 kB
  • After minification 537.6 kB
  • After compression 536.5 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

-0%

Potential reduce by 80 B

  • Original 16.5 kB
  • After minification 16.5 kB
  • After compression 16.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. Beautyfires.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (50%)

Requests Now

14

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

beautyfires.com

beautyfires.com

965 ms

beautyfires.com

beautyfires.com

1308 ms

mqy3kow.css

mqy3kow.css

145 ms

jquery-3.6.3.min.js

jquery-3.6.3.min.js

29 ms

main.334d44d6.js

main.334d44d6.js

1939 ms

main.abc0811e.css

main.abc0811e.css

1298 ms

api.js

api.js

55 ms

p.css

p.css

32 ms

gtm.js

gtm.js

101 ms

fbevents.js

fbevents.js

26 ms

recaptcha__en.js

recaptcha__en.js

57 ms

js

js

57 ms

analytics.js

analytics.js

23 ms

collect

collect

108 ms

collect

collect

25 ms

ga-audiences

ga-audiences

63 ms

d

d

4 ms

d

d

29 ms

d

d

24 ms

d

d

6 ms

Accessibility Review

beautyfires.com accessibility score

89

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

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Best Practices

beautyfires.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

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

beautyfires.com SEO score

89

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Beautyfires.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Beautyfires.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

beautyfires.com

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