Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    55% of websites

ahava.no

AHAVA®: Dead Sea Mineral Skincare Products – AHAVA USA

Page Load Speed

1.5 sec in total

First Response

38 ms

Resources Loaded

979 ms

Page Rendered

530 ms

ahava.no screenshot

About Website

Click here to check amazing AHAVA content. Otherwise, check out these important facts you probably never knew about ahava.no

Buy AHAVA® Dead Sea mineral products. Recharge, hydrate and illuminate your skin with our Dead Sea skin & body care products. Vegan and paraben-free.

Visit ahava.no

Key Findings

We analyzed Ahava.no page load time and found that the first response time was 38 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

ahava.no performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value5,710 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value33.9 s

0/100

10%

Network Requests Diagram

ahava.no

38 ms

www.ahava.com

115 ms

vsly-preact.min.js

84 ms

AHAVA_NA.js

85 ms

visually.js

85 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ahava.no, 46% (30 requests) were made to Ahava.com and 11% (7 requests) were made to Cdn.shopify.com. The less responsive or slowest element that took the longest time to load (347 ms) relates to the external source Cozycountryredirectiii.addons.business.

Page Optimization Overview & Recommendations

Page size can be reduced by 310.7 kB (38%)

Content Size

825.3 kB

After Optimization

514.6 kB

In fact, the total size of Ahava.no main page is 825.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. 55% of websites need less resources to load. HTML takes 342.4 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 293.9 kB

  • Original 342.4 kB
  • After minification 300.9 kB
  • After compression 48.5 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 41.5 kB, which is 12% 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 293.9 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 14.2 kB

  • Original 223.3 kB
  • After minification 209.0 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. AHAVA images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.2 kB

  • Original 218.2 kB
  • After minification 218.2 kB
  • After compression 216.9 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

-3%

Potential reduce by 1.4 kB

  • Original 41.5 kB
  • After minification 41.0 kB
  • After compression 40.1 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. Ahava.no has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 47 (78%)

Requests Now

60

After Optimization

13

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AHAVA. 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 from 16 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

ahava.no accessibility score

96

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.

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

Links do not have a discernible name

SEO Factors

ahava.no SEO score

85

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

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

High

Tap targets are not sized appropriately

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 Ahava.no 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 Ahava.no 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 AHAVA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: