Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

amirose.com

Amirose | Organic Skincare Hair and Beauty Products

Page Load Speed

4.2 sec in total

First Response

401 ms

Resources Loaded

3.3 sec

Page Rendered

432 ms

amirose.com screenshot

About Website

Visit amirose.com now to see the best up-to-date Amirose content and also check out these interesting facts you probably never knew about amirose.com

At Amirose, We specialise in producing high quality skincare, hair and beauty products. We carry a number of ranges that are available in the UK.

Visit amirose.com

Key Findings

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

Performance Metrics

amirose.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value10.0 s

27/100

10%

Network Requests Diagram

www.amirose.com

401 ms

theme.scss.css

66 ms

css

75 ms

css

84 ms

ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js

58 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Amirose.com, 60% (37 requests) were made to Cdn.shopify.com and 10% (6 requests) were made to Productreviews.shopifycdn.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Cdn.shopify.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 679.8 kB (11%)

Content Size

6.2 MB

After Optimization

5.5 MB

In fact, the total size of Amirose.com main page is 6.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 5.6 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 112.4 kB

  • Original 128.3 kB
  • After minification 90.2 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 38.0 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 112.4 kB or 88% of the original size.

Image Optimization

-4%

Potential reduce by 231.8 kB

  • Original 5.6 MB
  • After minification 5.4 MB

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. Amirose images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 275.0 kB

  • Original 405.8 kB
  • After minification 389.3 kB
  • After compression 130.8 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 275.0 kB or 68% of the original size.

CSS Optimization

-75%

Potential reduce by 60.6 kB

  • Original 80.5 kB
  • After minification 80.2 kB
  • After compression 19.9 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. Amirose.com needs all CSS files to be minified and compressed as it can save up to 60.6 kB or 75% of the original size.

Requests Breakdown

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

Requests Now

57

After Optimization

35

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

Accessibility Review

amirose.com accessibility score

61

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-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

amirose.com best practices score

92

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

Page has valid source maps

SEO Factors

amirose.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Amirose.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 Amirose.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

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