Report Summary

  • 32

    Performance

    Renders faster than
    52% 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

  • 85

    SEO

    Google-friendlier than
    55% of websites

beautyinthepot.oddle.me

Sorry, this Shop is currently closed.

Page Load Speed

9.5 sec in total

First Response

618 ms

Resources Loaded

8.8 sec

Page Rendered

80 ms

beautyinthepot.oddle.me screenshot

About Website

Visit beautyinthepot.oddle.me now to see the best up-to-date Beautyinthepot Oddle content for Singapore and also check out these interesting facts you probably never knew about beautyinthepot.oddle.me

Visit beautyinthepot.oddle.me

Key Findings

We analyzed Beautyinthepot.oddle.me page load time and found that the first response time was 618 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

beautyinthepot.oddle.me performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,950 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

beautyinthepot.oddle.me

618 ms

beautyinthepot.oddle.me

1770 ms

en_SG

2196 ms

css

27 ms

commons.32d327b7.chunk.css

1085 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 90% of them (19 requests) were addressed to the original Beautyinthepot.oddle.me, 5% (1 request) were made to Fonts.googleapis.com and 5% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Beautyinthepot.oddle.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 156.4 kB (47%)

Content Size

332.3 kB

After Optimization

175.8 kB

In fact, the total size of Beautyinthepot.oddle.me main page is 332.3 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. 15% of websites need less resources to load. HTML takes 183.2 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 133.0 kB

  • Original 183.2 kB
  • After minification 183.2 kB
  • After compression 50.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 133.0 kB or 73% of the original size.

Image Optimization

-16%

Potential reduce by 23.5 kB

  • Original 149.1 kB
  • After minification 125.6 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. Obviously, Beautyinthepot Oddle needs image optimization as it can save up to 23.5 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 10 (67%)

Requests Now

15

After Optimization

5

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

Accessibility Review

beautyinthepot.oddle.me accessibility score

89

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

beautyinthepot.oddle.me best practices score

75

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

High

Missing source maps for large first-party JavaScript

SEO Factors

beautyinthepot.oddle.me SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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 Beautyinthepot.oddle.me 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 Beautyinthepot.oddle.me 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 Beautyinthepot Oddle. 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: